I've found that there is a way to crash Lightwave using Octane that is repeatable 100% (on my rig anyway) but there is a simple way to avoid.
Fire up a fresh scene, activate Octane and open IPR. Drop in the attached model and Lightwave will crash (100% of the time). However.... If you drop in the model THEN open IPR all is fine and it won't crash. As far as I see the mesh is clean, no Ngons, no 2 point polys, all points merged and polys unified. I've noticed this tends to happen more with higher resolution meshes such as cars, beds, & trees.
Is this just my rig or is this happening with anyone else?
Another Mysterious Crash (...but thankfully avoidable)
Moderator: juanjgon
I just tested it, no crash no matter how I loaded itMrFurious wrote:I've found that there is a way to crash Lightwave using Octane that is repeatable 100% (on my rig anyway) but there is a simple way to avoid.
Fire up a fresh scene, activate Octane and open IPR. Drop in the attached model and Lightwave will crash (100% of the time). However.... If you drop in the model THEN open IPR all is fine and it won't crash. As far as I see the mesh is clean, no Ngons, no 2 point polys, all points merged and polys unified. I've noticed this tends to happen more with higher resolution meshes such as cars, beds, & trees.
Is this just my rig or is this happening with anyone else?

But to be honest I don't think I have ever loaded any object while IPR active so I have nothing to say about that problem with any other objects

But that object is using ShaderMeister which I don't have, it may be the cause.
Antti
AMD Ryzen Threadripper 2990wx (32c/64t),64GB RAM,NVIDIA GTX 1080ti,Win10
Clarisse 4,Houdini 18 (+Octane 2019),Blender2.81,Fusion360,Onyx,ZBrush,SubstPnt...
Started: Houdini 2019, Clarisse 2016
No business, just fun
Clarisse 4,Houdini 18 (+Octane 2019),Blender2.81,Fusion360,Onyx,ZBrush,SubstPnt...
Started: Houdini 2019, Clarisse 2016
No business, just fun

Thanks for trying this out Antti, you forced me to go back and check a few things. Wasn't the shadermeister, but traced it back to a LW startup command which runs a script on LW Launch. (the script basically automates opening of LW panels as well as enabling the octane plugin and opening the octane node editor) Not sure why exactly this is causing this issue but it definitely IS causing it.
Cheers.
Cheers.
Dino Inglese
CG Artist
Melbourne Australia
Intel Core i7-4820K, 3x GTX 980ti
Windows 7 64bit, Modo 12.2v2 for PC
Octane build 4.04.0.145
CG Artist
Melbourne Australia
Intel Core i7-4820K, 3x GTX 980ti
Windows 7 64bit, Modo 12.2v2 for PC
Octane build 4.04.0.145
Thanks Juanjo, it's 100% the script at fault here so don't waste your time testing this one, unless of course you want to try reproducing the issue using my script...
Cheers,
Dino.
Cheers,
Dino.
Dino Inglese
CG Artist
Melbourne Australia
Intel Core i7-4820K, 3x GTX 980ti
Windows 7 64bit, Modo 12.2v2 for PC
Octane build 4.04.0.145
CG Artist
Melbourne Australia
Intel Core i7-4820K, 3x GTX 980ti
Windows 7 64bit, Modo 12.2v2 for PC
Octane build 4.04.0.145
Juanjo could i ask on you to check this script for me. It's still causing crashes on editing mesh and reloading into layout.
Cheers,
Dino.
Cheers,
Dino.
Dino Inglese
CG Artist
Melbourne Australia
Intel Core i7-4820K, 3x GTX 980ti
Windows 7 64bit, Modo 12.2v2 for PC
Octane build 4.04.0.145
CG Artist
Melbourne Australia
Intel Core i7-4820K, 3x GTX 980ti
Windows 7 64bit, Modo 12.2v2 for PC
Octane build 4.04.0.145