Error on clay renders when normal render is fine

[sbstnc]

Hi,
I am having extreme troubles rendering a clay pass for scenes where previously every render wen through fine.
Literally all I am doing is opening the scene, turning off info passes, changing main pass to "grey" for clay option, and adding to the render queue. Every single scene I try errors out at some point, some after 1 or 2 frames.
3.04.05, PC Win 10, 4 x1070, R18

Are there any known issues with this? I don't understand why the renders are all failing when the only change from a couple of weeks ago is to switch to clay.

I will try with a reduced scene (to see if I can attach) but I doubt this will help, I need to be able to render these scenes, not reduced scenes.
There are messages in the log about not being able to pin an ID or something... restarted C4D and the log is gone, is there a log file somewhere I can get the actual error messages out of?

Thanks!

[aoktar]

Please! You should post some screen shots and text outputs what you see. Like this. Otherwise no sense on me! Also we're at 3.05.3 for stable and 3.06 for development builds.

[sbstnc]

Ah yes, sorry, I mean 3.05.04, sorry I got my numbers backwards!
I will post a screenshot tonight when I get back home.
But where is the log stored on the HDD in windows? I can't find it. When you close/reopen C4D (on crash even) the log as accessed by LV menu "Show Octane Log" is cleared session to session?

[aoktar]

You can activate saving to log file. Extract octane_log_flags.txt to Cinema4D directory. It will write octane_log.txt.

[sbstnc]

Thanks I will copy that file in and see what the log captures.

The C4D log (bugreport) has a lot of these, and this is happening on crash on a lot of rendering with clay mode in the PV and C4D render queue.
Critical_Log
{
[17:52:18] CRITICAL: Stop: Current take is nullptr document data could be corrupted [takemanager.cpp(504)]
[17:52:18] CRITICAL: Stop: Current take is nullptr document data could be corrupted [takemanager.cpp(504)]
}
}

There are no takes though so I don't understand why the log says this each time it crashes on render attempt.

[sbstnc]

Thanks I will copy that file in and see what the log captures.

The C4D log (bugreport) has a lot of these, and this is happening on crash on a lot of rendering with clay mode in the PV and C4D render queue.
Critical_Log
{
[17:52:18] CRITICAL: Stop: Current take is nullptr document data could be corrupted [takemanager.cpp(504)]
[17:52:18] CRITICAL: Stop: Current take is nullptr document data could be corrupted [takemanager.cpp(504)]
}
}

There are no takes though so I don't understand why the log says this each time it crashes on render attempt.

[sbstnc]

This is some of what the Octane log says.
Again, these scenes rendered fine in the PV and queue as non-clay.

Tried to access pin via an invalid ID P_MESH (111)
Tried to access null node pin
Tried to access null node
Tried to access pin via an invalid ID P_MESH (111)
Tried to access null node pin
Tried to access null node
Tried to access pin via an invalid ID P_MESH (111)
Tried to access null node pin
Tried to access null node
Tried to access pin via an invalid ID P_MESH (111)
Tried to access null node pin
Tried to access null node
Tried to access pin via an invalid ID P_MESH (111)
Tried to access null node pin
Tried to access null node
Tried to access pin via an invalid ID P_MESH (111)
Tried to access null node pin
Tried to access null node
Tried to access pin via an invalid ID P_MESH (111)
Tried to access null node pin
Tried to access null node
Tried to access pin via an invalid ID P_MESH (111)
Tried to access null node pin
Tried to access null node
Tried to access pin via an invalid ID P_MESH (111)
Tried to access null node pin


FRAME 15 fps:25 camMb:0 objMb:0
docFrame:15 edRender:0 curFrame:15 From:15 To:60 rFps:25 docFps:25
Total time:7331.239 ms. Estimated time:7171.864 ms.
Calculation completed.... frames:[15-61]
--------------------------- EXPORT LOG ---------------------------
CUDA error 719 on device 0: unspecified launch failure
-> failed to bind device to current thread
device 0: failed to initialize resources
device 0: detected an error on render device! trying to recover...
CUDA error 719 on device 0: unspecified launch failure
-> failed to bind device to current thread
device 0: failed to initialize resources
device 0: failed to recover - giving up and switching device to failed
CUDA error 719 on device 1: unspecified launch failure
-> failed to bind device to current thread
device 1: failed to initialize resources
device 1: detected an error on render device! trying to recover...
CUDA error 719 on device 1: unspecified launch failure
-> failed to bind device to current thread
device 1: failed to initialize resources
device 1: failed to recover - giving up and switching device to failed
CUDA error 719 on device 2: unspecified launch failure
-> failed to bind device to current thread
device 2: failed to initialize resources
----------------------------------------------------------------------------------------
device 2: detected an error on render device! trying to recover...
<<< Render failure detected!!! >>>
Please check render statistics to solve the problem.
CUDA error 719 on device 2: unspecified launch failure
-> failed to bind device to current thread
device 2: failed to initialize resources
CUDA error 719 on device 3: unspecified launch failure
device 2: failed to recover - giving up and switching device to failed
-> failed to bind device to current thread
device 3: failed to initialize resources
device 3: detected an error on render device! trying to recover...
CUDA error 719 on device 3: unspecified launch failure
-> failed to bind device to current thread
device 3: failed to initialize resources
device 3: failed to recover - giving up and switching device to failed
Device:0 TotMem:8Gb rtData:0Kb film:0Kb geo:0Kb node:0Kb tex:0Kb unavailable:4.001Gb temperature:32
Device:1 TotMem:8Gb rtData:0Kb film:0Kb geo:0Kb node:0Kb tex:0Kb unavailable:3.96Gb temperature:30
Device:2 TotMem:8Gb rtData:0Kb film:0Kb geo:0Kb node:0Kb tex:0Kb unavailable:3.92Gb temperature:30
Device:3 TotMem:8Gb rtData:0Kb film:0Kb geo:0Kb node:0Kb tex:0Kb unavailable:3.92Gb temperature:33
Check geometry subdivisons.
Picture viewer uses 'Render' subdivisions. But Live Viewer uses 'Editor' subdivision values.
Try to decrease 'render/editor' subdivison values.
Export materials time= 20801.13 ms
Collect objects time= 267.785 ms
Mesh creation time = 1865.635 ms.
Triangles:0 Disp.triangles:0 Hairs:0 Meshes:0
Total export Time = 23179.323 ms
movable:2 Nodes:757 camMb:0 objMb:0
Device:0 TotMem:8Gb rtData:0Kb film:0Kb geo:0Kb node:0Kb tex:0Kb unavailable:4.001Gb temperature:32
Device:1 TotMem:8Gb rtData:0Kb film:0Kb geo:0Kb node:0Kb tex:0Kb unavailable:3.96Gb temperature:31
Device:2 TotMem:8Gb rtData:0Kb film:0Kb geo:0Kb node:0Kb tex:0Kb unavailable:3.92Gb temperature:30
Device:3 TotMem:8Gb rtData:0Kb film:0Kb geo:0Kb node:0Kb tex:0Kb unavailable:3.92Gb temperature:33
Break rendering...

[aoktar]

These first errors comes from C4D not Octane. Second part is octane. This is not what i want to see. Pls read my previous post again. We need octane_log.txt under C4D folder.
What's R18 version? Did you removed unnecessary octane files after extract?

PM sent.