Currently the Rhino render window locks up the whole interface.
Is there any plan for this to change in the future ?
I suppose the user should be able to spawn multiple render processes if they wanted to.
Hi Thomas - @nathanletwory would have an idea about this I guess…
-Pascal
Perhaps this could be accomplished by spawning a dedicated robot instance of Rhino along with a snapshot of the scene.
Oh, wait: that would be called “save a copy of your document under another name (say: “mydoc_render.3dm”) and open it with a new instance of Rhino and start the render. Then go back to the first instance of Rhino and carry on.”
And hope you don’t run your computer out of memory.
Maybe it could be macro’d or scripted. Maybe someone already has.
If you are one of those who has a spare computer with a another Rhino license on your network maybe you could even devise a way to run the render on the 2nd machine.
Ok, was hoping if Rhino did it natively would be a lightweight solution and not duplicating the entire rhino session.
I guess, it’s not urgent … but was curious if there was a rationale to keep the old Rhino way instead of implementing an asynchronous window for Cycles.
For instance other engines have the option to send the render meshes to outside Rhino for rendering.
There was long ago in a WIP for 6 a brief moment it was possible. But I was told to disallow that.
Maybe the powers that be can be swayed in the future.
Yup, thanks! It was a curiosity. With Cycles being fast enough (and CyclesX even faster) … it’s probably a non issue at this point.