PM me a Dropbox (or other cloud storage) link here is the easiest.
Paul
Rhino / Octane aspect matching
Moderator: face_off
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
I think this is to do with the interpretation of viewport sizes. For example, a display viewport that is 400x400, but set to render (in Octane, RhinoRender) at 1920x1080 is getting interpreted/cropped differently.
I have not seen this as a major issue, as I just ensure that the display viewport has the same aspect ratio (manually set, rather than dragged/stretched). So I would just set the rhino viewport to 960x540 to render at 1920x1080.
Cam
I have not seen this as a major issue, as I just ensure that the display viewport has the same aspect ratio (manually set, rather than dragged/stretched). So I would just set the rhino viewport to 960x540 to render at 1920x1080.
Cam
Octane for Rhino | Windows 8.1 x64 | i7-3820 OC | GTX970 4GB OC & GTX 560 Ti 1GB OC | 32GB DDR3
We still have the same problem.
I think if you check show safe frame in rhino option and adjust your rhino viewport so that it shows the complete view it should match.
But if the aspect ratio of the viewport is vertical you experince this problem.
This has to be fixed please.
I think if you check show safe frame in rhino option and adjust your rhino viewport so that it shows the complete view it should match.
But if the aspect ratio of the viewport is vertical you experince this problem.
This has to be fixed please.
What version of the plugin are you running pls? Can you send me a scene which demonstrates this problem pls?I think if you check show safe frame in rhino option and adjust your rhino viewport so that it shows the complete view it should match.
But if the aspect ratio of the viewport is vertical you experince this problem.
This has to be fixed please.
Thanks
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
Hi Paul,
I have to check the version in the office next week.
I know that I installed the latest version available on August 26th (if that helps). But I need to find out the exact version number...
I have to check the version in the office next week.
I know that I installed the latest version available on August 26th (if that helps). But I need to find out the exact version number...
Hi Paul,
we are still using 3.03 at the office, so I couldn't test yet.
But I will describe it briefly.
In Rhino options you can tick on rendering/save frame on (save title, save action,...).
So then you see a gray frame if you decrease the viewport (horizontally).
If you increase the width of the Rhino viewport you will see two gray arrows left and right indicating that not everything is displayed.
Usually this shouldn't matter at all for a rendering. If you do a viewport capture via command or a VRay rendering or any other renderer it should always render what is within the gray frame.
But Octane changes the render view (octane window) if you see the gray arrows. So there is often a mismatch between old and new renderers and to find this out after a long rendersession is depressing.
It is easy to reproduce.
Was this fixed in the last release?
Cheers
Nando
we are still using 3.03 at the office, so I couldn't test yet.
But I will describe it briefly.
In Rhino options you can tick on rendering/save frame on (save title, save action,...).
So then you see a gray frame if you decrease the viewport (horizontally).
If you increase the width of the Rhino viewport you will see two gray arrows left and right indicating that not everything is displayed.
Usually this shouldn't matter at all for a rendering. If you do a viewport capture via command or a VRay rendering or any other renderer it should always render what is within the gray frame.
But Octane changes the render view (octane window) if you see the gray arrows. So there is often a mismatch between old and new renderers and to find this out after a long rendersession is depressing.
It is easy to reproduce.
Was this fixed in the last release?
Cheers
Nando
I'm sorry Nando, but I cannot help you unless you tell me the full version number of the plugin you are running.we are still using 3.03 at the office, so I couldn't test yet.
But I will describe it briefly.
In Rhino options you can tick on rendering/save frame on (save title, save action,...).
So then you see a gray frame if you decrease the viewport (horizontally).
If you increase the width of the Rhino viewport you will see two gray arrows left and right indicating that not everything is displayed.
Usually this shouldn't matter at all for a rendering. If you do a viewport capture via command or a VRay rendering or any other renderer it should always render what is within the gray frame.
But Octane changes the render view (octane window) if you see the gray arrows. So there is often a mismatch between old and new renderers and to find this out after a long rendersession is depressing.
It is easy to reproduce.
Was this fixed in the last release?
Thanks
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
Hi Paul,
the version is 3.3.3.70
Cheers
Nando
the version is 3.3.3.70
Cheers
Nando
Can you pls try with the latest release. If the problem is still occurring - send me a sample scene demonstrating the problem, and provide the exact steps I need to take to see the issue.
Thanks
Paul
Thanks
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
Hi Paul,
at the moment we can not update to the latest release on all machines including standalone because we are in a tight deadline.
It would really help me if you could repeat the following steps since there is no change concerning this in the update log.
1. create any kind of simple scene putting the objects on the viewport extents (to check if parts are cropped).
2. use -viewCaptureTo file command to create a screenshot
3. open Octane Render view and make the render view window really narrow (so that the two arrows [left] and [right]) appear]
4. Save the image from the render view
4. So you will see that they don't match if you overlay them
at the moment we can not update to the latest release on all machines including standalone because we are in a tight deadline.
It would really help me if you could repeat the following steps since there is no change concerning this in the update log.
1. create any kind of simple scene putting the objects on the viewport extents (to check if parts are cropped).
2. use -viewCaptureTo file command to create a screenshot
3. open Octane Render view and make the render view window really narrow (so that the two arrows [left] and [right]) appear]
4. Save the image from the render view
4. So you will see that they don't match if you overlay them