Dreaded 999 error is back

[Rafael-Vallaperde]

Hello everyone.

Hi Paul.

Mate i'm bumping into this error all the time now and can't get it to work anyhow.

Error 999:

After 999 happens, i need to reboot my machine otherwise my titans won't load anything again.

It starts rendering then screen flashes and NVIDIA message pops saying that the driver crashed and recovered. 3D applications don't crash due to this error. However octane stops rendering.

It seems to stick to the scene, after the error happens it will remain with the scene, somehow.

Can't track what is going on, first i had UV errors, thought they could be trigering it, but not really, i deleated the UVs from the meshes and errros still happens.

Link to the scene: https://www.dropbox.com/s/jlikh742bkn3u ... 9.rar?dl=0

Thank you for reading.
heeeeeelllp!

All the best.
Raf

[face_off]

Hi Raf - I'll download and try your scene. However, in the vast majority of cases error 999 is a hardware problem. Try underclocking your card(s), or just rendering to a single card to determine which one is at fault.

Paul

[face_off]

Hi Raf - I couldn't render this scene on my PC - Windows 10 reported it was running out of memory. Are you using Modo801 or 901? What OS are you using and how much RAM do you have? Have you tried the latest TEST release of the Octane plugin (for Octane 2.24)?

Paul

[rafaelcoppola]

Hello Paul
I and Rafael Vallaperde worked at the same company and I was also participating in this work,we try to decoupage the problem and in our tests whats caused the problem was the material called "cortina atras" "cortina azul" "cortina amarela", when we exchange these materials all went well
big hug
Rafael Coppola

[Rafael-Vallaperde]

Hi Poul.

Yeah, scene is a bit heavy, a lot of raw geometry.
I'm rendering from 801, and i have 32 Gigs of memory.

999 doesn't seem to be hardware related here, as Coppola said i investigated a lot and found out that materials were creating the error. First a though a .tif texture was causing the issue, erased the material and it started to work.

Another point that makes me believe that it isn't related is that the error happens in 3 different machines. the same way.

Later on, i noticed that that problem wasn't related to the .tif, it was related to leaving unplugged nodes in the sschematic(many).

Sometimes in my workflow if i want to tchange the material i'll simply unplug the nodes that create one material and create another branch. This seems to be causing the error.
Weird!!

Havent tried the new build yet, will do so.

Thanks man.

[face_off]

When you next get an error 999, can you pls try exporting the scene to ORBX and sending to me?

Thanks

Paul