Re: OctaneRender for Modo Beta 1.52 [TEST]
Posted: Sat Apr 12, 2014 7:31 am
Strange. If I make 2 cubes and try to export one as .obj with "Export Selected Layers" Modo do not crash.
Community Forums for OTOY Customers
https://render.otoy.com/forum/
I can confirm the crash with octane installed. The bug DOES NOT occur when octane is not installed though (I rename my AppData\Roaming\Luxology_old and make a new one with my modo.lic file in it).face_off wrote:Modo is crashing for me even with the plugin disabled. I am on SP5, deleted my Config.CFG, and it still crashes - so it look like a Modo bug to me. Is anyone else able to reproduce this crash pls?Strange, I get this behavior every time if I have Octane for Modo installed!
If I make 2 cubes and try to export one as .obj with "Export Selected Layers" Modo crash!
If I copy one cube to a new scene and export that scene as .obj with "File - Export as..." everything works!
2 Cubes scene(.LXO)
Video(youtube) about this problem
/Niklas
Paul
Hey Paul,face_off wrote:Modo is crashing for me even with the plugin disabled. I am on SP5, deleted my Config.CFG, and it still crashes - so it look like a Modo bug to me. Is anyone else able to reproduce this crash pls?Strange, I get this behavior every time if I have Octane for Modo installed!
If I make 2 cubes and try to export one as .obj with "Export Selected Layers" Modo crash!
If I copy one cube to a new scene and export that scene as .obj with "File - Export as..." everything works!
2 Cubes scene(.LXO)
Video(youtube) about this problem
/Niklas
Paul
René, the Modo devs have been able to reproduce the crash without the plugin loaded - so it's definitely a Modo issue. The fact that the crash doesn't happen with the plugin disabled is "luck"I can reproduce the crash with the Octane for Modo plugin installed. If I deinstall it (delete the Octane for Modo Plugin folder in the Lux Configs and delete my MODO cfg) the crash is gone...so it seems it has something to do with the plugin...unfortunately. I am on SP5 too...
No - not supposed to happen, and I couldn't reproduce the problem. Do you have other Modo item selected when changing the bloom and glare?I have noticed that the Render resets every time a post process change is done (bloom & glare). Is this supposed to happen?
Looks like I can't reproduce it either. Restarted and the problem is gone.No - not supposed to happen, and I couldn't reproduce the problem. Do you have other Modo item selected when changing the bloom and glare?
Sometimes Modo sends the plugin a "Mesh Change" event when you change an unrelated property (like the Postproc channels), which triggers a refresh. I don't know why this happens - and I see it rarely - but it happens.Looks like I can't reproduce it either. Restarted and the problem is gone.
I've seen similar behavior in MODOs own preview render for the entirety of 701s existence. Random things seem to cause a reset of the render, including just sitting there watching it.face_off wrote:Sometimes Modo sends the plugin a "Mesh Change" event when you change an unrelated property (like the Postproc channels), which triggers a refresh. I don't know why this happens - and I see it rarely - but it happens.
Paul