Windows 10 (15063.674)
3x GTX 1070 (FE)
32gb RAM
Nvidia driver version 388.00
Standalone version 3.05
Octane C4D plugin version 3.06.2
Cinema 4D R17 build .055
I've been working on an arch vis school project for the last week. The other night the whole file became corrupted and so I had to start over. I spent yesterday and today rebuilding the room and other assets that I hadn't saved to disk. I also, at the time of the file corruption, didn't have Cinema's autosave feature engaged. I do now. My issue is this: now that I'm at a point where I'm trying to add the final touches, ie, materials/textures, I'm having a persistent render failure. Luckily, I have previous builds where the render was going fine. However, I encounter a lot of issues with Octane on a regular basis. I almost always get a render failure, no matter the project. I can't determine if this is due to Cinema 4d, Octane, graphics cards, or something else.
I'm desperate to understand if anyone can shed light onto what's making Octane fail with this project. This time around I even made sure to optimize all the assets wherever possible through polygon decimation. But still... the render fails. I really love using Octane but the constant failures I encounter really bums me out to no end.
Pasted below is the LOG report and a Dropbox link to the project file:
Dropbox: https://www.dropbox.com/s/sjxlq295d8de1 ... s.c4d?dl=0
**In this project I also used TurbulenceFD to create the pyro + smoke sim for the fireplace.**
-------------------------------------------------------------------------------------
Log:
Started logging on 05.11.17 16:13:15
OctaneRender 3.06.2 (3060200)
--------------------------- EXPORT LOG ---------------------------
Tried to access pin via an invalid ID P_DIFFUSE (30)
Tried to access null node pin
Node type 33 is either unknown, a linker or incompatible to static pin 'unknown' (P_UNKNOWN, type PT_UNKNOWN) of node '' (NT_UNKNOWN, 0000019A3FAA7590)
Tried to access pin via an invalid ID P_DIFFUSE (30)
Tried to access null node pin
Node type 33 is either unknown, a linker or incompatible to static pin 'unknown' (P_UNKNOWN, type PT_UNKNOWN) of node '' (NT_UNKNOWN, 0000019A3FAA7590)
Tried to access pin via an invalid ID P_INDEX (80)
Tried to access null node pin
Can't write float to static pin 'unknown' (P_UNKNOWN, type PT_UNKNOWN) of node '' (NT_UNKNOWN, 0000019A3FAA7590)
Tried to access pin via an invalid ID P_INDEX (80)
Tried to access null node pin
Can't write float to static pin 'unknown' (P_UNKNOWN, type PT_UNKNOWN) of node '' (NT_UNKNOWN, 0000019A3FAA7590)
Tried to access pin via an invalid ID P_INDEX (80)
Tried to access null node pin
Can't write float to static pin 'unknown' (P_UNKNOWN, type PT_UNKNOWN) of node '' (NT_UNKNOWN, 0000019A3FAA7590)
Tried to access pin via an invalid ID P_INDEX (80)
Tried to access null node pin
Can't write float to static pin 'unknown' (P_UNKNOWN, type PT_UNKNOWN) of node '' (NT_UNKNOWN, 0000019A3FAA7590)
Export materials time= 2293.768 ms
Collect objects time= 27.821 ms
Mesh creation time = 5174.921 ms.
MB:0/0 ST/MOV:0/595 Nodes:1276 Tris:0 DispTris:0 Hairs:0 Meshes:0
VRAM used/free/max:265Mb/5.866Gb/8Gb Out-of-core used:0Kb total used RAM:8.587Gb
Total export Time = 8313.491 ms
CUDA error 700 on device 1: an illegal memory access was encountered
-> kernel execution failed(report)
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to copy memory from device.
device 1: direct light kernel failed
----------------------------------------------------------------------------------------
<<< Render failure detected!!! >>>
Please check render statistics to solve the problem.
MB:0/0 ST/MOV:0/595 Nodes:1276 Tris:2.16m DispTris:2k Hairs:720k Meshes:596
Device:0 TotMem:8Gb rtData:284Mb film:10Mb geo:588Mb node:61Kb tex:1.589Gb unavailable:1.389Gb temperature:57
Device:1 TotMem:8Gb rtData:284Mb film:11Mb geo:588Mb node:61Kb tex:1.589Gb unavailable:1.379Gb temperature:64
Device:2 TotMem:8Gb rtData:284Mb film:11Mb geo:588Mb node:61Kb tex:1.589Gb unavailable:1.881Gb temperature:61
CUDA error 700 on device 2: an illegal memory access was encountered
-> failed to launch kernel(init4)
device 2: direct light kernel failed
CUDA error 700 on device 0: an illegal memory access was encountered
-> kernel execution failed(report)
CUDA error 700 on device 0: an illegal memory access was encountered
-> failed to launch kernel(ptBrdf2)
device 0: direct light kernel failed
Persistent Crash, Very Demoralized
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.
-
helloimneil
- Posts: 33
- Joined: Sat Apr 01, 2017 9:44 pm
I've conducted some more troubleshooting and believe I may have found the issue. Within the TFD container, under the rendering tab, I had the smoke and fire shader to be displayed using the values stored in the temperature parameter. By selecting 'none' for each of these the render now goes to completion. I think the Octane object tag and the TFD rendering tab were miscommunicating, or something, which was causing the error. If this fix proves to be incorrect I will report those findings to this forum post.