Version 3.04.5-R2 (05.12.2016)-Previous stable

Fri Nov 18, 2016 8:13 pm

mrom wrote:renders fine here, but without the acer campestre texture. nice work btw
R16, latest octane

Yeah still not getting it. Took all Laubwerk textures out and used my own bark texture. Still crashes as soon as I try to render to the picture viewer. Can someone please take a look and tell me what's going on? Thank you!

Fri Nov 18, 2016 9:35 pm

aggiechase37 wrote:tell me what's going on?!

https://docs.otoy.com/#cinema-4d-v3-plu ... ume-object

Sat Nov 19, 2016 2:17 am

I use windows version.
want test build.

It's very helpful fo me.

Sat Nov 19, 2016 6:58 am

Ok, so what options do I have? This is as large as I could make the voxels.

Mon Nov 21, 2016 8:57 pm

HI. I´m having a weird issue with this latest version (3.04.3-R1) on C4D 18.028 on windows. Whenever I try to render an image sequence of my current project, it renders the first frame fine but then stops right as it starts rendering the second frame. This happens on the picture viewer. If I try the render queue it does the first frame and the it sends an out of memory error and stops, but the scene is quite light, it´s actually using about 300MB of the 6GB I have on both cards.
Yesterday I tried downgrading to 3.03.3-R1 and everything works fine.
I read through this topic but didn´t read of anything similar from anyone. Any ideas what could be causing it?
Thanks

Mon Nov 21, 2016 10:20 pm

do you have any c4d shaders in your project?

Mon Nov 21, 2016 10:34 pm

mrom wrote:do you have any c4d shaders in your project?

I think I do... is that the reason? Because, it actually started happening on the previous version as well

Mon Nov 21, 2016 11:23 pm

rafaelvamp wrote:
mrom wrote:do you have any c4d shaders in your project?
I think I do... is that the reason? Because, it actually started happening on the previous version as well

Yes. It mostly happens with Layer texture. Try to don't use c4d shader as much as possible. It can makes the material creation and previews much slower.

Tue Nov 22, 2016 7:46 am

Have a serious bug in a particular scene when using render regions. The sequence causing the crash:

Render the full scene to PV. Stop.
Render to LV, draw a region.
Save and enable the region in Octane Render Settings
Render to PV. Stop.
Refresh render in LV - even with the region still active the whole view is rendering, not the region.
Toggle region on/off to get it to work again.
Create a new region
Save and enable new region in Octane Render Settings
Render to PV. Crash.

It only crashes when certain objects were added back into a test scene, which I can send to you...

Tue Nov 22, 2016 3:29 pm

aoktar wrote:
rafaelvamp wrote:
mrom wrote:do you have any c4d shaders in your project?
I think I do... is that the reason? Because, it actually started happening on the previous version as well
Yes. It mostly happens with Layer texture. Try to don't use c4d shader as much as possible. It can makes the material creation and previews much slower.

Yes, that seems to fix my problem. Many thanks!