OTOY Forums

C4D is crashing almost every time I do a render session in Octane.
I'm running 3 980 ti hybrids on an asus x99 motherboard.
I have no idea how to read these bug report files, but could really use some help, I'm on a pretty tight deadline.

Thanks.
Jamie

This is the way to invistigate the crashes.

Sorry about that.

Running version 2.24.2 R2 (this is one I've rolled back to)
Using Windows 10 pro 64 bit
Intel 17-5960x CPU @3.00GHZ (corsair h100i gtx liquid cooling)
ASUS X99-DELUXE/U3.1 LGA 2011-v3 Intel X99 SATA 6Gb/s USB 3.1 ATX Intel Motherboard
32 gigs of ram DDR4
980 TI hybrid x3
500 GB SSD
The crashes happen while rendering this scene. It's just a simple camera move. The total video is a product piece and consists of multiple camera moves around this one object.
Occasionally when the crashes happen, the render will get stuck on an image and re-render that frame over and over again.

Most the time just c4d crashes, but occasionally I will also get a BSOD from windows.

Let me know if I need to supply additional information.

Is It this scene? Which frame? I run it but no any crashes. Though that you have complex animations, scene and materials. This is very simple.
What happens when run with low maxsamples, can it reach to end? Do you make renders overnight? What about system sleep?

Yes this scene, no I mentioned that it's very simple animations. There is no set frame that it crashes on, it's very random. (There are other scenes that I have saved, but it's the exact same geometry with a different camera animation. I've saved them as individual files just to keep track of them)
It still crashes with low max samples (but seems to be less often),
occasionally the scene will make it to the end.
I usually do render over night but these crashes have been during the day.
I've set the system to never sleep, but the monitor does power off after a while.


Here is one of the emails that Maxon sent me this morning after receiving the crash report.


"Hello,

You forwarded a bugreport to us at 2016/04/18.

The crash has been caused by Octanes renderplugin.

To avoid further crashes remove the plugin from your installation of Cinema 4D
or try to install the latest version of this plugin.

You should inform and describe this problem to the developer of the plugin to assure he can
reconstruct the issue and fix the problem.

Kind regards,

Technical Support

=========== MAXON Computer GmbH ===========
Max-Planck-Str. 20 - 61381 Friedrichsdorf - Germany
Phone: +49-(0)6172-5906-0 Fax: +49-(0)6172-5906-30
============= www.maxon.net ==============

Sitz der Gesellschaft: Friedrichsdorf (Ts.) / USt-IdNr. DE 113864088
Amtsgericht Bad Homburg v.d.H. / HRB-Nr. 6049
Geschäftsführer: Uwe Bärtels, Harald Egel, Harald Schneider

Diese Mail ist nur für ihren Empfänger bestimmt und darf ohne
ausdrückliche schriftliche Genehmigung weder weitergeleitet noch
in irgendeiner Form (auch nicht auszugsweise) veröffentlicht werden.
---------------------------------------------------------------------
This message is intended for the addressee or its representative
only. Any form of unauthorized use, publication, reproduction,
copying or disclosure of the content of this e-mail is not permitted."

I just notified somethings weird: It ignores the updates after frame 2, if i set out range to 0-200 and leave timeline as 140-200. This is about plugin+c4d sdk.

It's really weird that it crashes because there is no any changes on objects, materials. Can you try with different options? I believe there is a problem on deep not plugin.
1-Manual or "all object movable" options.
2-Send all data