OTOY Forums

Hey

So 6 months ago I got corrupted materials from time to time, when you do varied changes back and forward in the materials (non-node editor), (like changing reflectance, ctrl-z, textures in and out etc)
sometimes they can break and corrupt, and are no longer usable and break the file.

this then looks like this:


I didnt need these files for the last months and now I am opening them again and seemingly all my files are unusable

Even If I delete the corrupted materials or all octane objects the scene no longer renders. And before only one material was corrupted which then could be avoided by not saving the scene and going back to last saved,
but it has literally spread to all other materials now in all my octane files, while I was pretty sure before that I did not save any corrupted files or one at the best.


I get this error in the log now and cant render at all anymore:
OctaneRender 3.08.4 (3080400)

CUDA error 999 on device 0: unknown error
-> failed to link to cubin
device 0: failed to compile OSL code:
error : Undefined reference to 'cuGeo' in '('
error : Undefined reference to 'cuParams' in '('
error : Undefined reference to 'TRANSFER_XYZ' in '('
error : Undefined reference to 'cuXyzToRgbMatrix' in '('
error : Undefined reference to 'CYAN' in '('
error : Undefined reference to 'BLUE' in '('
error : Undefined reference to 'GREEN' in '('
error : Undefined reference to 'MAGENTA' in '('
error : Undefined reference to 'RED' in '('
error : Undefined reference to 'YELLOW' in '('
error : Undefined reference to 'cu_cam' in '('
error : Undefined reference to 'cuQueues' in '&'
device 0: failed to compile module 0


I just downloaded the latest 3 version but nothing changed.
I cant even open a new scene, make a new material and render that, same error. Can I delete some cache or something somehow? Or how can this be fixed?

Materials or scene is not corrupted. There's a problem with GPU or DRIVER.

I had the issue 6months ago and just updated to the latest driver (980 Ti) yesterday

And I have seen how the material corrupted in real time when I changed material settings back then, and that was just in one material. I did not save that change and reopening it worked again.
But it seems like nothing works now even without material. The GPU shows no sign of error on any other application or game.

Can you read something out of the error log I posted?

Turns out that using a newer driver causes the error and corruption, I will try to roll back a couple months but this should be looked at

Yes the newest driver that works is 417 from 2019.1.15,
419 does not work and the latest 430 something also does not

FlowFireGames wrote:Yes the newest driver that works is 417 from 2019.1.15,
419 does not work and the latest 430 something also does not

There should be an explanation, but not sure. Also it's a core and hardware issue not plugin. Latest drivers may not be well for your gpu type.

It happens on my Titan X Pascal and on my 980 TI

Different thing:
Often when the octane render is about to finish and you try to move the picture viewer preview inside the picture viewer window (when a hand appears for dragging)
Octane freezes and freezes cinema 4D, requiring a task manager quit, happened multiple times to me already on latest 3 version, surely also still exists on v4, should not be hard to reproduce
(maybe only in path tracing not 100% sure)

Record a video to show it. As I said that's not happening on my side also not a plugin issue. Why don't you stay with the stable driver for you?

FlowFireGames wrote:It happens on my Titan X Pascal and on my 980 TI

Different thing:
Often when the octane render is about to finish and you try to move the picture viewer preview inside the picture viewer window (when a hand appears for dragging)
Octane freezes and freezes cinema 4D, requiring a task manager quit, happened multiple times to me already on latest 3 version, surely also still exists on v4, should not be hard to reproduce
(maybe only in path tracing not 100% sure)

We see a similar problem with re-sizing the LV window while rendering, and we're still on V4/ Mac OS/ various 10xx cards. I suspect it's a driver issue, but honestly, it's been easier to modify our behavior, (Don't mess with the LV window, other than moving it, while it's rendering!), than to spend hours or days chasing down the right driver for each machine's hardware/OS version.

That obviously doesn't solve your problem, but at least you know you are not alone.