Hi,
We also encounter similar problems during a project with a friends.
In 8 years of using Houdini we never had a scene corruption problem with houdini. Those kind of problems were a things of the past while using maya and nParticles.
But recently my friend has done an approved shot for a project and was just unable to open his scene, so i couldn't believe that , and i also try. i also fail to open it, and it also fail on a linux machine.
So it was just impossible to get our work back.
Basically when opening the scene the houdini console was opening and display an infinite looping message log contening the O_PUI ? O_UI ? OPUI ? OUI ? word ( i dont remember exactly ).
He finally was able to open his scene and get his work while using a voodoo tricks from symek on odforce.
https://forums.odforce.net/topic/27410- ... -hip-file/This post save our ass as we were able to open the cpio archive and edit it manually.
Then 5 days later still suspecting my fellow friend of being a lazy / unprofessional human being, i get the exact same problem, console was opening with infinite loop, and it was impossible to open it. fortunately i am a huge paranoid and save my scenes around 100000 times per day so there was no issue to get our work back.
But from there, while we have no proof it is an octane for houdini problem we switch all our render on standalone and delete all octane nodes in our scenes.
From there we didn't encounter any scene corruption problems.
We have now switch all our renders on standalone and stop using octane for houdini for the moments just as a precaution.
Again we have no evidence that octane corrupt the scene.
But Octane for houdini is the only variable we have added in the equation in 8 years without any problem of this kind, so i highly suspect it from being at the core of the log message.
Cheers
E