Version 2.05.0 - Updated on (14.08.14)

[aoktar]

well, most important thing is, that rendering works!
Even if I have to restart after each render session.

Trying now with renderthreads set to "1"
But this will be fixed in near future?

thanks
Mike

threads are new on development, i wished to see how is working. There is some problems which are related c4d's sdk and our workflow.
As you can read in section, has a note about that. Also default is 1 core. I hope to get some support and fix it.
Also you should think to do a stress test on your gpus. Maybe a HW problem.

[miohn]

Hi Ahmet,

what stress test should I do?
Any recommendations?

regards
Mike

[aoktar]

Hi Ahmet,

what stress test should I do?
Any recommendations?

regards
Mike

hi mike,
First, can you do some checks on registy for TdrLevel and TdrDelay values. Also try this values to enter to registy. Later check again rendering to see what's happening.

WriteRegDWORD HKLM “SYSTEM\CurrentControlSet\Control\GraphicsDrivers” TdrLevel 3
WriteRegDWORD HKLM “SYSTEM\CurrentControlSet\Control\GraphicsDrivers” TdrDelay 10

[momade]

hey aoktar.

as i am a veeery 'fast klicker' (always thining two steps ahead of what im doing and therefore klicking at the moment) i encounter chrashes of octane 2.03 almost on a minute base. it crachesrandom. sometimes just by opening a meaterial in the material manager, very often, just by chaging the renderer from 'DL' to 'PT'. sometimes when aboarding a rendering in pictureviewer, making a quick change to light or material and hitting the renderbutton again...

i had to go back to 2.02, because it crashes by faaaat more soldom!.

how do i send you crash-reports?


br.
mo

[aoktar]

hey aoktar.

as i am a veeery 'fast klicker' (always thining two steps ahead of what im doing and therefore klicking at the moment) i encounter chrashes of octane 2.03 almost on a minute base. it crachesrandom. sometimes just by opening a meaterial in the material manager, very often, just by chaging the renderer from 'DL' to 'PT'. sometimes when aboarding a rendering in pictureviewer, making a quick change to light or material and hitting the renderbutton again...

i had to go back to 2.02, because it crashes by faaaat more soldom!.

how do i send you crash-reports?


br.
mo

please attach a few bugreport.zip here.
"Fast clicking" does not causes any crash. I'm suspecting on new improvement for C4D shaders.
Are you using c4d's shaders in Octane materials with multicores?

[momade]

where can i find these bug-reports?

br.
mo

[aoktar]

where can i find these bug-reports?

br.
mo

c:\Users\ahmet\AppData\Roaming\MAXON\Cinema4Dr15_ABCEFGH\..

Can you response the question about your C4D shader usage?

[momade]

i have an unused original c4d material in the material-manager. but it is not in use on any rendered object. its just in use un a nullobject, that i keep my materials on to keep them from loss when selecting delete unused materials. all the octane materials used have no c4d-shaders applied.

the bug-report-zip is attached.
br.
mo

[aoktar]

i have an unused original c4d material in the material-manager. but it is not in use on any rendered object. its just in use un a nullobject, that i keep my materials on to keep them from loss when selecting delete unused materials. all the octane materials used have no c4d-shaders applied.

the bug-report-zip is attached.
br.
mo

ok, doesn't make any different to use or not. It triggers some preview calls. I can see the problem on part of multicore, as i expected. Set cpucores=1 to avoid crashes. I'll try to implement more reliable method.

If anyone has crashes on 2.03 please try first set cpu cores=1

[Augustronic]

"Perspective Correction" doesn't work with "Motion Blur" on.