viewport aspect ratio >< rendered aspect ratio
Moderator: face_off
Simple test - set render output at 800x600 and open the Octane viewport. Now change the viewport ratio by moving the left Rhino viewport side - the Octane rendering is zooming in/out. This is not good and shouldn't happen. The Rhino viewport ratio is changing as side effect of the Rhino usage often. So, please make that the rendering output zoom stay constant. Rhino is not changing the camera (place and target and camera properties stay constant), so why changing the render output?
http://www.simulacrum.de - Visualization for Designer and Architects
Win7 64 | Dual Xeon E5-2687W | 32GB RAM | 2 GTX 780 6GB | Rhino3D
Win7 64 | Dual Xeon E5-2687W | 32GB RAM | 2 GTX 780 6GB | Rhino3D
I tried the workflow you described. When you change the Rhino viewport width, the Rhino camera position does not change, and neither does the Octane camera position. The Rhino FOV is changing, and the Octane thin lens camera FOV is changing to match. So the plugin is working as it should based on this test.Simple test - set render output at 800x600 and open the Octane viewport. Now change the viewport ratio by moving the left Rhino viewport side - the Octane rendering is zooming in/out. This is not good and shouldn't happen. The Rhino viewport ratio is changing as side effect of the Rhino usage often. So, please make that the rendering output zoom stay constant. Rhino is not changing the camera (place and target and camera properties stay constant), so why changing the render output?
Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Rhino is grown over the years, rendering wasn't the power side of Rhino at the beginning, maybe some old behaviors are not fixed But many render engines are implemented and try to match the need of the user. I used the following engines: Rhino render, BMRT, AIR, Maxwell, Penguin, Vray, Neon and Octane now. Octane is the only one with this unneeded behavior. Please fix it.
http://www.simulacrum.de - Visualization for Designer and Architects
Win7 64 | Dual Xeon E5-2687W | 32GB RAM | 2 GTX 780 6GB | Rhino3D
Win7 64 | Dual Xeon E5-2687W | 32GB RAM | 2 GTX 780 6GB | Rhino3D
I do not understand what behavior you are referring to. I am unaware of any bugs in the area of camera matching.Octane is the only one with this unneeded behavior.
Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
- splittmatt
- Posts: 42
- Joined: Tue Dec 10, 2013 4:51 pm
- Location: Gold Coast, QLD Australia.
Hi Paul.
Hopefully this explains it better, see grabs below.
The render output changes if the rhino viewport is changed even if the FOV isn't changed. So for example if I don't have Rhino maximised to my screen and the viewport aspect ratio changes the render output changes.
You can see that the position of the box in the viewport in each of the screen grabs is in the same position to the safe frame but the render output is fastly different.
Does this make sense?
Matt
Hopefully this explains it better, see grabs below.
The render output changes if the rhino viewport is changed even if the FOV isn't changed. So for example if I don't have Rhino maximised to my screen and the viewport aspect ratio changes the render output changes.
You can see that the position of the box in the viewport in each of the screen grabs is in the same position to the safe frame but the render output is fastly different.
Does this make sense?
Matt
Win 11. Intel I-9 14900K. 64Gb. RTX 4080 Super.
- prehabitat
- Posts: 495
- Joined: Fri Aug 16, 2013 10:30 am
- Location: Victoria, Australia
Hi Paul,face_off wrote:I'm sorry - I don't understand what you are saying.I read this thread here and thought, no, not a new workaround keep in mind. Please try that a simple direct workflow can be used - a render is defined by the Rhino named view and the output size only.
Paul
I'm pretty sure Micha is saying that rather than a new workaround can we have a simple direct workflow; requiring only the Rhino named view & output size.
It doesn't affect/both me size I always oversize & crop/mash in Photoshop/in design anyway... But pretty sure that's the jist of it.
Win10/3770/16gb/K600(display)/GTX780(Octane)/GTX590/372.70
Octane 3.x: GH Lands VARQ Rhino5 -Rhino.io- C4D R16 / Revit17
Octane 3.x: GH Lands VARQ Rhino5 -Rhino.io- C4D R16 / Revit17
I'm really sorry - but the issue is not clear at all. If anyone can provide a sample scene and a workflow which illustrates the issue - I will take a look.
Paul
Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Did you: set render output at 800x600 and open the Octane viewport. Now change the viewport ratio by moving the left Rhino viewport side (not single viewport setup) - the Octane rendering is zooming in/out.?
http://www.simulacrum.de - Visualization for Designer and Architects
Win7 64 | Dual Xeon E5-2687W | 32GB RAM | 2 GTX 780 6GB | Rhino3D
Win7 64 | Dual Xeon E5-2687W | 32GB RAM | 2 GTX 780 6GB | Rhino3D
Yes, I tried this. It is working fine for me.Did you: set render output at 800x600 and open the Octane viewport. Now change the viewport ratio by moving the left Rhino viewport side (not single viewport setup) - the Octane rendering is zooming in/out.?
If you set the Octane Resolution to 800 x 600, then if the Rhino resolution is NOT the same aspect ratio as the Octane resolution, the FOV will not match correctly - since Rhino is rendering a different spare viewport to Octane.
Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Paul, please make that Octane works like the Rhino renderer and all the other render engines at Rhino. The current behavior cause trouble and some times it's useful to match renderings from different engines. Please use the Rhino render as reference - no zooming if the Rhino viewport ratio is changed.
For the test - it works fine? So you don't see a zooming effect? If you see an Octan zooming during changing the Rhino viewport ratio than you see the users problem. Please fix it, it's important.
For the test - it works fine? So you don't see a zooming effect? If you see an Octan zooming during changing the Rhino viewport ratio than you see the users problem. Please fix it, it's important.
http://www.simulacrum.de - Visualization for Designer and Architects
Win7 64 | Dual Xeon E5-2687W | 32GB RAM | 2 GTX 780 6GB | Rhino3D
Win7 64 | Dual Xeon E5-2687W | 32GB RAM | 2 GTX 780 6GB | Rhino3D