LW update? Tweet

[PaGz]

Thanks Lewis, i will try that.

Does this will impact negatively the performance and loading time for the GPU?

Best

https://martinpatoine.myportfolio.com/work

[Lewis]

Yes loading time is slower but render speed is same, but if stability is issue it's worth try.

[PaGz]

Thanks Lewis!

I did some new renders since turning off multithreaded scene extraction and no more crash for the moment.
I will do more testing next week after my actual 1200 frames to renders.....

Best

[PaGz]

Hi Lewis!

Now i can confirm that turning off multithreaded scene extraction has solved my crashing issues!

Thanks Lewis!!!

[Lewis]

Goid to hear

[PaGz]

Hi again Lewis,

I am really confused my situation is special i think.
I had many issues with Lightwave and Octane Render.
Today i think i have resolved almost all my problems.
The source of my problems was Comodo Antivirus!!!
Now i did uninstalled Comodo and Lightwave, Modeler, and Octane all works perfectly!
First day since many weeks without hangs or crash on Lw, modeler or Octane even running Octane with Multithreaded Extraction all the day with no crash!!!

So my conclusion is something wrong with Comodo...

But now i did uninstalled Comodo i need another firewall so i did installed Tiny Firewall and seems good till now..

But a new thing happen.
I have 3 gpu on another computer that now have rendering error:

OptiX error for device 2: [ERROR] "sbt->raygenRecord" is null
OptiX API error for device 2: Invalid value
device 2: path tracing kernel failed
detected that all GPUs of the render node have failed -> restarting render node

Any idea?
In the project many new textures edit, some model edits, no plugins used except Octane.
The only new addition to the project is for the fist time in this project i have created a Compound node for a surface!


I have reduced my project size significantly since last few days but this problem now...

[Lewis]

Hi,

I use regular Windows firewall/Defender so not really needed any 3rd party ones so far.

As for optic crashes it could be your GPU clock/overheating so check with MSI Afterburner what are clocks and try to underclock GPU to see.