I realize that this is probably a very pre mature question, however, I was wondering if the Rhino development team has shared anything with you regarding the development of the Change Que for rendering plugins that is in the works for the upcoming Rhino V6 ?
The reason I ask, is because it sounds like this Change Que development, being done to integrate Cycles, will benefit All render engines. I was wondering if you were aware of this and if you knew if maybe this would also benefit the Octane plugin? My hope would of course be for Octane to be able to do two main things:
1) Render in the Rhino viewport
2) Not have to load the scene for every frame when doing animations. I know this can be alleviated by exporting to the stand alone, but it would be a nice step to skip.
The comment from Nathan over at McNeel, on the Rhino forum regarding the Change Que is:
Again, I realize this is probably a question too early in the development of this . . . but in case not, I thought I'd ask.Part of my work to integrate Cycles into Rhino was to help create a framework that makes it easy to integrate a render engine using the RhinoCommon SDK. The Raytraced viewport mode is building on that framework. For viewport interactive realtime rendering we created the ChangeQueue. Utilizing this integration plug-ins can much more easily access the Rhino data in a unified way. It shouldn't be a big step to ensure that Bongo and the ChangeQueue play well together for the benefit of render engines.
Thanks,
Ryan
