viewport aspect ratio >< rendered aspect ratio
Moderator: face_off
Installed the latest version and did a quick test - Octane doesn't match the Rhino 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
It looks like Rhino's render output is not matching it's own preview window. I suspect this is because it is using the Vertical or Diagonal FOV of the preview window whereas Octane uses the Horitonal FOV (which you can see is matching between the Rhino preview window and the Viewport). Did you try enabling the safe frame feature of the plugin?Installed the latest version and did a quick test - Octane doesn't match the Rhino 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
Paul, that's like all render engines work at Rhino. Please, no workaround, no plugin use (I don't used the safe frame feature), only simple support of the typical Rhino render output. The Rhino viewport is changing the size all over the day, every time the user switch on/off toolbars, ... . So, nobody is using the viewport ratio or wide as reference.
Also don't forget, if you would go the typical Rhino way, than you wouldn't get a different output of the Octane viewport and Octane-at-the-Rhino frame buffer anymore.
Also don't forget, if you would go the typical Rhino way, than you wouldn't get a different output of the Octane viewport and Octane-at-the-Rhino frame buffer anymore.
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
Micha - I think you are getting derailed by some odd functionality in Rhino. I have described the issue in the McNeel forum - hopefully a dev can provide some answers. http://discourse.mcneel.com/t/how-to-ge ... ugin/24942
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
Hello Paul,
thank you for the new option to unsync the octane FOV from the Rhino FOV, I have tested it , it works and in principle does what we asked for...
I have to observations:
1. when manual editing the FOV in the octane panel and then opening the octane viewport, the initial picture is not showing the correct FOV ( in my tests it seems that it is zoomed in -> FOV seems to be smaller ) when I then change the FOV e.g. by one degree back and forth the picture "jumps" to the correct + expected appearance. Maybe this hiccup can be cured...
2. In practice I would be great when we could also use the octane focal length node to adjust the FOV, the reason is that I can adjust the FOV in Rhino only through the focal length parameter of the 35mm rhino camera and not view or adjust the FOV directly.
To my understanding FOV and focal length should determine each other... Ideally the focal length used in the rhino camera would mimic the octane focal length (right now this does not seem to be the case e.g. a horizontal FOV of 77,32 / Rhino length length of 30 mm translates to a octane lens length of 22,49985 - please see attached screenshot). When we have created a rhino viewport with a certain aspect ratio and a certain focal length that we want to use, we could simply take these three values (width, height, focal length ) and dial them in the octane camera settings.
This way we could recreate the initial rhino viewport in octane and be sure that it would not change through any unintentional rhino viewport modification.
I hope I was able to make myself clear – I am not a native speaker...
I think we are almost there
best
Andreas
thank you for the new option to unsync the octane FOV from the Rhino FOV, I have tested it , it works and in principle does what we asked for...
I have to observations:
1. when manual editing the FOV in the octane panel and then opening the octane viewport, the initial picture is not showing the correct FOV ( in my tests it seems that it is zoomed in -> FOV seems to be smaller ) when I then change the FOV e.g. by one degree back and forth the picture "jumps" to the correct + expected appearance. Maybe this hiccup can be cured...
2. In practice I would be great when we could also use the octane focal length node to adjust the FOV, the reason is that I can adjust the FOV in Rhino only through the focal length parameter of the 35mm rhino camera and not view or adjust the FOV directly.
To my understanding FOV and focal length should determine each other... Ideally the focal length used in the rhino camera would mimic the octane focal length (right now this does not seem to be the case e.g. a horizontal FOV of 77,32 / Rhino length length of 30 mm translates to a octane lens length of 22,49985 - please see attached screenshot). When we have created a rhino viewport with a certain aspect ratio and a certain focal length that we want to use, we could simply take these three values (width, height, focal length ) and dial them in the octane camera settings.
This way we could recreate the initial rhino viewport in octane and be sure that it would not change through any unintentional rhino viewport modification.
I hope I was able to make myself clear – I am not a native speaker...
I think we are almost there

best
Andreas
Architectural Rendering Services
1 x 4090 GTX, 1 x 3090 GTX
http://www.v-cube.de
1 x 4090 GTX, 1 x 3090 GTX
http://www.v-cube.de
Ah yes - I think the Scale pin is being applied after the FOV. I will fix that.1. when manual editing the FOV in the octane panel and then opening the octane viewport, the initial picture is not showing the correct FOV ( in my tests it seems that it is zoomed in -> FOV seems to be smaller ) when I then change the FOV e.g. by one degree back and forth the picture "jumps" to the correct + expected appearance. Maybe this hiccup can be cured...
This should be possible.2. In practice I would be great when we could also use the octane focal length node to adjust the FOV, the reason is that I can adjust the FOV in Rhino only through the focal length parameter of the 35mm rhino camera and not view or adjust the FOV directly.
I will make these changes in the next release (next week).
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
thanks! -> very cool!This should be possible.
I will make these changes in the next release (next week).
Architectural Rendering Services
1 x 4090 GTX, 1 x 3090 GTX
http://www.v-cube.de
1 x 4090 GTX, 1 x 3090 GTX
http://www.v-cube.de
What version of the plugin are you running pls?I'm sorry, but this is still not working. Why is it that I change nothing but the layout of Rhino and still my renders turn out slightly differently. This makes basically Octane Render a useless product.. right?
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