When creating custom resolutions. The safe frame needs to have the aspect ratio specified by the user (like cropping the camera sensor) and the longest dimension of the safe frame needs to stay within the narrowest dimension of the viewport.
So, If the user specifies a ridiculously narrow aspect ratio the Safe frame should look like this:
The way it is now the safe frame goes outside the viewport and we no longer see what will be rendered unless we detach the viewport and start resizing it.
Example: The user specifies a custom resolution of 500x8000. The safe frame should look like this
The way Rhino works currently is that the custom render size changes the camera sensor size. Doing this changes the cone angle and therefore it’s a sneaky way to change the 35mm equivalent focal length. Example: an 85mm camera whose sensor size is changed to 48x48 will have a field of view of 43.5 degrees and therefore becomes a 54mm standard lens.
Rhino is doing it this way because the rendered image is not affected by viewport window resizing (but at the expense of changing the FOV and equivalent focal length)
If we were to keep the aspect ratio within the Rhino viewport (as suggested above) then it is still possible to choose an appropriate camera sensor size to do so, but it will likely have to be a different method than the current Rhino lensing (of keeping the smallest dim at 24mm)
Here is an example by adjusting directly the focal length (but the same can be achieved if rhino internally changed the sensor size). Here the red rectangle is the desired aspect ratio to fit on screen.
Dear Santa,
we have been nice, so will you grant us this wish? It’s nothing big, so it might still fit into your bag, and make us very happy!
Thank you so much!
