OTOY Forums

I've been getting quite a few hangups with Octane, seemingly pointing to Cuda 702 errors. I have searched the Octane forums, and the TDR Delay has been referenced. As noted, the standalone install sets this value to 10. I checked, and since I have installed the standalone, my value is also set to 10. I have a 150 frame 1080p animation that seems to have on the same series of frames (roughly half way through, frame 75, 76, etc.) Even when I start that animation rendering to start from that frame forward, the first frame will render, but the subsequent frames with cause Cinema to hang. I cannot exit gracefully, therefore I cannot see the Octane log that was generated (and I see no option to write the log as a text file until after one views the log, which you cannot do when Cinema is hung up -- logic error there, I think.)

I'm really stuck. I bet this project on Octane, but now that it has come down to actual production rendering, well, the situation is concerning me greatly...

Hi,
This is not a bug and posting to wrong section. Cuda error shows you reached to some limitations. Vram or polygon counts. You can have more polygon due difference subdivision for render output. Advice to investigate more your scenes about this limitations and watching the tutorials.

Hi Aoktar, here is the error report that I just had. Hopefully you can offer a good solution for me

Started logging on 31.08.15 12:49:56

OctaneRender 2.24 (2240000)

Scene created in plugin version 2232006
Tried to access null item
Could not load 'C:\Users\<me>\Dropbox\Cinema 4D Files\<Project>\tex\263742_4d47604d5ca7c830d1fe368209719e62.png:rgba'.

...
Can't write float to static pin 'unknown' (P_UNKNOWN, type PT_UNKNOWN) of node 'chromed steel 1' (NT_UNKNOWN, 000000456B3E2CC0)
Tried to access pin via an invalid ID P_BRIGHTNESS_SCALE (17)
Tried to access null node pin
Can't write float to static pin 'unknown' (P_UNKNOWN, type PT_UNKNOWN) of node 'chromed steel 1' (NT_UNKNOWN, 000000456B3E2CC0)
Tried to access pin via an invalid ID P_BRIGHTNESS_SCALE (17)
Tried to access null node pin
Can't write float to static pin 'unknown' (P_UNKNOWN, type PT_UNKNOWN) of node 'chromed steel 1' (NT_UNKNOWN, 000000456B3E2CC0)
Tried to access pin via an invalid ID P_BRIGHTNESS_SCALE (17)
Tried to access null node pin
Can't write float to static pin 'unknown' (P_UNKNOWN, type PT_UNKNOWN) of node 'chromed steel 1' (NT_UNKNOWN, 000000456B3E2CC0)
Could not load 'C:\Users\<me>\Dropbox\Cinema 4D Files\<Project>\tex\263742_4d47604d5ca7c830d1fe368209719e62.png:rgba'.
CUDA error 1 on device 2: One or more of the parameters passed were not within an acceptable range of values.
CUDA error 1 on device 1: One or more of the parameters passed were not within an acceptable range of values.
-> failed to bind texture to device memory (data3)
-> failed to bind texture to device memory (data3)
device 2: failed to bind data texture 2 of context 0
device 1: failed to bind data texture 2 of context 0
<<< Render Failure >>>
CUDA error 1 on device 0: One or more of the parameters passed were not within an acceptable range of values.
-> failed to bind texture to device memory (data3)
device 0: failed to bind data texture 2 of context 0

I wrote that what you should do. it's most likely triangle count problem. second option that's out of vram. try to hide some geo until find. texture error comes from a material from livedb.

The issue was the character's hair. My initial render tests of this scene had no animation on the character. The issue revealed itself with movement of the character as the camera moved through the shot. I have made some changes to the character (as well as culling every single unnecessary polygon I could find throughout the scene) and that appears to have solved it, for the most part. Octane still complains about those two particular frames, but manages to render them anyway. I used an asset from Cinema's content browser, and that has some sort of weird map, the reference of which persists even though I have removed the object from my scene. Odd, but no noticeable impact outside of the notations in the log file.

FYI.