Cinema 4D version 2019.1.5-R3 (Obsolete stable) 12.02.2020

[aoktar]

if i open old scenes or render scenes the octane plugin crashes. i dont understand why?

i attached a Bug Report.

System is :

Octane 4.05 | Cinema 4D Studio R21.115
Win10 Prof. 64 bit
AMD Ryzen Threadripper 1950X 16-Core 4.00GHZ
Drivers: tried different from NVidia: studio 26.21.14.4166
3x 1080ti GTX Geforce

Bugreport doesn't give a detailed information. It show that's crashing at the renderer. Must attach a scene or send by Pm. Or activate log outputs and put c4doctanelog.txt

It just takes time and money!

Which version do you suppose to use? You're on 4.05 and this thread is for 2019.1.5

[rclassenphoto]

Thats not right im on 2019.1.5 why you think im on 4.05 ?

Look at the image an the error an the octane version

[rclassenphoto]

An i made this scene file with 2019.1.4 and i had no problems and i dont had problems with old files from other versions of octane. This shit comes with 2019.1.5. And this is not good for my workflow.

[aoktar]

An i made this scene file with 2019.1.4 and i had no problems and i dont had problems with old files from other versions of octane. This shit comes with 2019.1.5. And this is not good for my workflow.

Disable multi-threading for materials and try again. What do you have in your old scenes? Which version you used to do these?

[rclassenphoto]

An i made this scene file with 2019.1.4 and i had no problems and i dont had problems with old files from other versions of octane. This shit comes with 2019.1.5. And this is not good for my workflow.

Disable multi-threading for materials and try again. What do you have in your old scenes? Which version you used to do these?

thanks i think this helps me out! I disable "multi-threading" and now it doent crashes. At the start of a scene. Can you explane why this happens?

[aoktar]

thanks i think this helps me out! I disable "multi-threading" and now it doent crashes. At the start of a scene. Can you explane why this happens?

Maybe about your cpu and setups. Explaining is hard without testing on your side. What do you have in your scenes? Can I get some scenes for testing?

[rclassenphoto]

yes i can send you the scene files, but i allway happen in scenes were are not much stuff in it. How can i send you the scene files?

And CPU? i mean i have a AMD Ryzen Threadripper 1950X 16-Cores 4.00GHZ. And i have the same pc as slave pc with 16-Cores and i happens on this pc the same.

[aoktar]

yes i can send you the scene files, but i allway happen in scenes were are not much stuff in it. How can i send you the scene files?

And CPU? i mean i have a AMD Ryzen Threadripper 1950X 16-Cores 4.00GHZ. And i have the same pc as slave pc with 16-Cores and i happens on this pc the same.

I've tested many big scenes with this feature, even on 3900x. No problems. But it doesn't mean it's very stable yet. There may some settings can cause a conflict. Please send some scenes with dropbox/wetransfer/etc.. send me PM.

[rclassenphoto]

i test it out and again the plugin crashed. And there is no "mix" smybol in the "LiveDB" manager. I think there is a problem with materials in this octane version. I will upload this and send you the scene file.

[desire]

Hello aoktar
Check the video, pls, by the link https://yadi.sk/i/c11XDsb-Qv3aNg
It's not a critical bug, but since 2019 version, there like a glitch in a Live Viewer (jumping background) while changing some types of parameters, like camera position, tex projection and tex transform (not related to background), changing projection views in a native cinema4d 3d view, and so on

Thank you