When I select my render plugin as the current renderer, the Document->Render Properties options change.
However then flipping back to the Rhino Renderer, this panel becomes…
I take it this is a bug? Shouldn’t these screens be consistent? If the user selects the Rhino Renderer and sets a resolution, and then changes renderer, the resolution does not get copied across. I think this is creating a lot of confusion for some users.
Now - with the “Lock Viewport Ratio” UNTICKED in the Rhino Render properties, the Rhino Render panel renders to a resolution set in the NON-Rhino Render properties (ie. in the above case, selecting the Rhino Renderer and rendering, Rhino sets the resolution to 400 x 200 - but of course the panel to set this resolution is not available to the user when the Rhino Renderer is selected!
In summary - the Rhino Renderer is rendering to a resolution set in a panel which cannot be accessed whilst the Rhino Renderer is enabled.
Further to this, you can see in the render above the Rhino Render FOV seems to be arbitrarily set (it’s not using the HFOV, or the VFOV - so what is it using?). Also, how can a rendering plugin get the FOV that the Rhino Renderer is using? Without being able to access the FOV, there is no way for a rendering plugin to match the FOV used by the Rhino Renderer. I’m currently using doc.Views.ActiveView, but of course the FOV obtained from the ActiveView is that of the Preview window, not the FOV used by the Rhino Renderer.
Hope this all makes sense - and that there are some solutions.