Hey there, I'm getting a fatal render error whenever I try to render a 1920x1080 EXR sequence of 75 frames. My guess so far is that a high poly count will crash the scene, but I'm not sure.
Windows 10 Pro 64 Bit
Intel Core i7-6800K CPU @ 3.40GHz
NVIDIA GeForce GTX 980 Ti (Gigabyte)
NVIDIA GeForce GTX 980 Ti (Gigabyte)
ForceWare version: 372.54
SLI Disabled
64 GB DDR4 RAM
Octane Plugin Version 3.03-3-R1
Octane Engine Version 3.03-3
Cinema 4D R17.053
I've attatched my scene and bugreport zip. Any help is much appreciated, as I have zero clue why it is crashing and on a tight deadline.
Thank you very much!
Scene Render Crash
Moderators: ChrisHekman, aoktar
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
- Attachments
-
- bugReportAndSceneFile_jamesvde_01.rar
- Bug Report Folder & Scene File called waveRoof
- (440.32 KiB) Downloaded 182 times
I'm not sure about exact reason. Maybe a bug in plugin with meshno=3 and these objects. It's a long topic.
Use layer manager to make visible all objects in object manager. then select tags and change values to 1-2.
Btw, please don't use "send all data" without any real reason. I'm gonna deprecate that soon.
A tip when crashes/errors happened: Try to delete some parts and render it until find crash reason.
Use layer manager to make visible all objects in object manager. then select tags and change values to 1-2.
Btw, please don't use "send all data" without any real reason. I'm gonna deprecate that soon.
A tip when crashes/errors happened: Try to delete some parts and render it until find crash reason.
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
True, seems a bit above what I need to know. Thank you for the tip with the layer manager.
I had to use 'send all data' as my deformer wouldn't update correctly when rendering. Unless there is another way around that.
I'll try that next time when I encounter a crash or error.
Thanks again!
I had to use 'send all data' as my deformer wouldn't update correctly when rendering. Unless there is another way around that.
I'll try that next time when I encounter a crash or error.
Thanks again!

Ok i see. When some meshes are not updating try this option. I'm gonna check this issue after come back from a vacation.
Or this options
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
- fatfreemedia
- Posts: 65
- Joined: Thu Jul 31, 2014 10:15 am
- Contact:
Those softboxes are, I'm sad to say, very very bad news for Octane at the moment. I would recommend against using them if possible.
Win10 64bit | 3 * GTX970 | i7 5930k | 32GB
Win10 64bit | 2 * GTX970 | i7 4790k | 16GB
Win10 64bit | 3 * GTX980 | i7 5930k | 32GB
Win10 64bit | 3 * GTX980 | i7 5930k | 48GB
Win10 64bit | 3 * GTX1070 | i7 6850k | 64GB
Win10 64bit | 2 * GTX970 | i7 4790k | 16GB
Win10 64bit | 3 * GTX980 | i7 5930k | 32GB
Win10 64bit | 3 * GTX980 | i7 5930k | 48GB
Win10 64bit | 3 * GTX1070 | i7 6850k | 64GB