Rhino: Critical usage of the viewport (ratio change cause output change)

Hi,

it’s a problem I know from Octane and that I never have seen at Vray, but Enscape show it too. The render output strongly depends on the viewport ratio.

Today morning I have setup 30 views of a complex interiors and later this day I wonder, why some views show to much or not enough from the scene anymore. I found now, that a change of the viewport ratio cause a change of the output view. This is very critical since Rhino viewports are quite dynamic, the sizes can be changing often over the day.

Please go the way of Vray, there the Vray cam is defined by camera source/target/lenslength only. So, it doesn’t matter how the viewport is looking, the output is always the same. The current behavoir cause a lot of trouble and is a pitfall for user who not careful check the viewport ratio.

-Micha

I do not understand. The viewport ratio must change the resulting image, else it would be distorted. Thats why we set the vertical field of view fixed and scale the horizontal field of view accordingly.

Can you give an example on what you mean / what you desire?

Here an example, best to understand if we look at the Rhino render output and the Rhino camera options. The solution would be if Enscape would determinate the view by camera position, target, lens length and output size only. The goal should be that a change of the viewport size/ratio doesn’t cause any zoom effect at the Enscape window.

Vray do it like the Rhino render and so, the user can press the render button after weeks and he get the same result like before, no matter how big the viewport is or on which computer/screen the file is opened

It might have to do with horizontal vs. vertical field of view. The lens length stored in the Rhino View defines the vertical FOV, and it looks like this stays the same when the viewport size changes. Enscape internally uses the horizontal FOV and we convert the vertical to horizontal based upon the viewport size.

We’ll think about a solution.

@Simon_Weinberger For me a good benchmark is Vray for Rhino. It’s developed since more than 10 years and proved under real project conditions. And Vray complete ignores the viewport ratio/size. The camera is defined by position-target-lenslength.

Why is it so important to keep the output independent from the viewport? Often renderings are post worked at Photoshop. I or my clients create dozen of layers for adding or adjusting things. And if later a detail needs to be rerendered and exchanged, than the new rendering must 100% match. If not, all the previous postwork needs to be redone.

Please, try to keep it simple and save - ignore the viewport FOV.