Hi Ahmet,
lately my cinema is crashing constantly with scenes that worked before quite fine.
i read that this could be something with the vram but in this case its only few polys and only few bitmap texturs.
what i have is a ton of cinema noises in a very complex mixed materiel with lots of nested materials and a xpresso setup which is animating the noises and doing some userinterface stuff.
however it worked perfectly last week.
i build the scene with 2.24.0 and it started crashing, so i decided to update to 24.1 but its still crashing.
the error messages comes very irregular after switching the frame on the timeline or hitting the render button. usually after about 5 clicks it crashes.
when i open the log while letting it crash the last lines is always a different, so no specific one.
same thing happens when trying to open on another machine or when i copy everything into a new scene.
i'm working on a 5,1 macpro, gtx970 with up to date drivers.
do you have any experiences or suggestions what after a certain point might cause the problem?
thanks for you time,
jonas
Application and Plugin Error
Moderators: ChrisHekman, aoktar
You should post bugreport.zip. Also check Console and Octane Log windows.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
thanks for your reply.aoktar wrote:You should post bugreport.zip. Also check Console and Octane Log windows.
i attached the bugreport and a screenshot of the log and the console.
jonas
- Attachments
-
- _BugReport.zip
- (45.94 KiB) Downloaded 115 times
MacPro5,1 OS X 10.10.3 | GTX TITAN Black, GTX 970, 3x GTX 780Ti, GTX 780
What's yours?skoeth wrote:it says "1" as well.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
But i see the crashes are occuring in "RenderShader". It's about the baking C4D shaders. Please check again.skoeth wrote:its set to "1" too
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
it is definitly set to "1". even when i try to change it it automatically switches back to "1".aoktar wrote:But i see the crashes are occuring in "RenderShader". It's about the baking C4D shaders. Please check again.
one thing i just noticed it that its working fine when im rendering the scene in the picturemanager.
so is there any setting regarding the liveviewer that could cause the problem?
- Attachments
-
- Bildschirmfoto 2015-10-06 um 15.38.51.png (19.9 KiB) Viewed 2275 times
MacPro5,1 OS X 10.10.3 | GTX TITAN Black, GTX 970, 3x GTX 780Ti, GTX 780
No. It's a global parameter. I'm not sure why it happens in just LV. But it's exactly related with RenderShader. You can test it by removing C4D shaders. Also maybe good to share some scene with me.skoeth wrote:it is definitly set to "1". even when i try to change it it automatically switches back to "1".aoktar wrote:But i see the crashes are occuring in "RenderShader". It's about the baking C4D shaders. Please check again.
one thing i just noticed it that its working fine when im rendering the scene in the picturemanager.
so is there any setting regarding the liveviewer that could cause the problem?
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw