viewport aspect ratio >< rendered aspect ratio

[v-cube]

Hello Paul,

before I get to the usual "make a wish" stuff I would like to tell you that we just finished a series of projects using octane 4
rhino and are more than happy with the way the software runs and the pace at it is developing. It is really a pleasure to use!

Thanks for that!

But of course it is alway possible to increase some things

Ok - here we go:

One of our main sources of errors is the issue that the rendered picture is not fully determined by the position, FOV and
viewing vector of the rhino camera and the resolution you key in the octane render options dialogue but also by the aspect ratio
of the viewport.

E.g. when rendering a picture with a 2:1 aspect ratio , 4000px x 2000px you get a different result, when you have a viewport
aspect ratio of 2:1 ( which is the correct way) compared to a viewport aspect ratio of let's say 1:3.
So the correct workflow right now is to always make sure that your viewport aspect ratio fits 100% your render resolutions AR.

The Problem is that often you alter the viewport size without noticing it, e.g. when you open the file on another computer with
another toolbar layout...

I would suggest to alter the behaviour in a way that the rendered result is only determined by the octane render resolution and

the position of the camera, its target and FOV, wich would define it 100% in my understanding.

In this aspect, it would also be great thing to have the option to "bind" the octane render window to a certain viewport /
camera, independant of it being active at the point of time you hit the render buttom.

If both aspects could be implemented, i could just hit "render" and could be sure that the right perspektive (not accidently "top" or "right) is rendered and it is rendered the same each time, independent of the actual viewport aspect ratio.

Another suggestion: could there be an option to use the safe frame rhino feature to show the octane render aspect ratio rather than the rhino render aspect ratio?

I hope this makes sense...

best regards

Andreas

[face_off]

Hi Andreas - I'm not totally clear on what you are asking for here - are you rendering in the OctaneRender Viewport, or via Octane in the Rhino Render panel?

E.g. when rendering a picture with a 2:1 aspect ratio , 4000px x 2000px you get a different result, when you have a viewport
aspect ratio of 2:1 ( which is the correct way) compared to a viewport aspect ratio of let's say 1:3.
So the correct workflow right now is to always make sure that your viewport aspect ratio fits 100% your render resolutions AR.
would suggest to alter the behaviour in a way that the rendered result is only determined by the octane render resolution and

the position of the camera, its target and FOV, wich would define it 100% in my understanding.

If you click the Resolution Lock button - Octane will render to the resolution set in the Rendertarget->Resolution setting (when rendering to the OctaneRender Viewport). If you render to the Rhino Render panel, the resolution used will be as per the Rhino Render Properties.

In this aspect, it would also be great thing to have the option to "bind" the octane render window to a certain viewport /
camera, independant of it being active at the point of time you hit the render buttom.

If both aspects could be implemented, i could just hit "render" and could be sure that the right perspektive (not accidently "top" or "right) is rendered and it is rendered the same each time, independent of the actual viewport aspect ratio.

I understand where you are coming from with this suggestion. However Rhino itself allows you to do a Rhino Render from the currently selected View - so to me to tie the Octane Render to a specific view is somewhat un-Rhino behavior. Also - I'm not quite sure where the tied View would be specified. At the moment you can tie a rendertarget to a View, so then to tie a View to a rendertarget could be problematic. Perhaps this requirement is better served with scripting in Rhino. For example, couldn't you use something this the following script to achieve this requirement? http://wiki.mcneel.com/developer/script ... namedviews.

Another suggestion: could there be an option to use the safe frame rhino feature to show the octane render aspect ratio rather than the rhino render aspect ratio?

To do this, can you not simply set the Rhino render resolution to the Octane render resolution. Again, this might be doable via Rhinoscript.

Sorry I haven't been much help with the above suggestions...

Paul

[v-cube]

Hello Paul,

are you rendering in the OctaneRender Viewport, or via Octane in the Rhino Render panel?

I am rendering to the Octane render Viewport.

I created two screenshots which should illustrate what I mean... the issue is that unless you specify exactly the rhino viewport size (and therefore aspect size), you will not archive the same render results e.g. on another computer with different toolbar layout or screen resolution.

the only thing which was changed is the rhino viewport size... camera position, camera target, lens length and render resolution are the same.
I will look into your scripting suggestion, thanks...


best

Andreas

[face_off]

I created two screenshots which should illustrate what I mean... the issue is that unless you specify exactly the rhino viewport size (and therefore aspect size), you will not archive the same render results e.g. on another computer with different toolbar layout or screen resolution.

OK, I see issue. Can you tick the Viewport Navigation button? That should lock all aspect of the camera position for that view.

Paul

[splittmatt]

Hi Paul.

Using the viewport navigation only works if the viewports are set up before each render. If the scene is opened again on a different computer and the viewports aren't the same you can't guarantee the correct render.
What we really need is for the render output to dictate the safe frame within the viewport. MAX does this very well as you can see here. No matter what the viewport size the rendered area stays the same.
Maybe this is more a Rhino problem than Octane?

[face_off]

The following workflow seems to achieve what you need:

- Select Perspective View
- Open Named Views panel, create new named view
- View the new named view in the perspective view
- Rightclick plugin Settings tree->Save Rendertarget to View
- Enable Resolution Lock
- Open Viewport, tick Viewport Navigation toggle button

Now that named view should be always render in the same camera position, fov and resolution regardless of the PC is it loaded on.

Does this resolve your issue?

[Edit: this workflow was popping an error message, which I have fixed in the latest release - 2.23.2.42]

Paul

[Micha]

I used Vray fro Rhino several years and there the rendering is independent from the viewport ratio, like at the example of 3dsmax. I never took care about the Rhino viewport ratio. So, I suppose so it should work at Octane for Rhino too. Please try to fix it, because it cause trouble during projects, if renderings doesn't match anymore.

[face_off]

I used Vray fro Rhino several years and there the rendering is independent from the viewport ratio, like at the example of 3dsmax. I never took care about the Rhino viewport ratio. So, I suppose so it should work at Octane for Rhino too. Please try to fix it, because it cause trouble during projects, if renderings doesn't match anymore.

I'm sorry - I don't understand the problem you are having here. Did you try the workflow I posted above?

Paul

[Micha]

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.

[face_off]

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.

I'm sorry - I don't understand what you are saying.

Paul