linvanchene wrote:Can anyone give more information which settings in the DS render settings are used by the Octane Render Settings?
Is there a way to have DS cameras display the proper aspect ratio in the DS viewport by just using the Octane Render Settings?
Or do I always have to use the DS render settings to get the proper aspect ratio showing?
sorry that you need to fiddle around...
the bottom line(s) first:
- since not everyone seems to feel the need for using the aspect frame to control the output crop, this is an optional setting (defaults to on aynway).
- the octane render size can only be controlled by the respective setting in the plugins render settings.
- changing aspect ratios either by resizing the octane viewport (while scale-to-viewport is on), or changing the x/y render settings will overrule the ds render settings.
why does this happen?
- the render dimensions in ds control the camera aspect ratio (as well as the aspect frame of course)
- plus this affects the field of view
- since the fov is vertical in daz and horizontal in octane, there is no way to make fov and ar settings independent
- in order to synchronize daz and octane cameras - which is a must - both render size settings need to stay somehow connected.
- while the rendering is sized to the viewport, the master needs to be the plugin, otherwise it won't be possible to show the correct aspect frame in the ds viewport, and even the camera fov won't match.
- this means the master controlling the dimensions in general needs to be the plugin, otherwise you will have 2 places which affect the render size in a different ways, making things very complicated.
- if this would not be connected all together, octane cameras won't ever be in sync to the daz viewport
so why is not at least the render size in ds also updated to the settings in the plugin?
the input method in the ds render size/ar fields won't allow it, as much i like to do it.
in detail: the connection of this fields between x/y size and x/y ar effectively overwrite each other whenever something changes; put x size in change y ar, enter x ar, changes y size, and so on.
as far as i remember (this was done way in the past) there is something strange happening, actually avoiding setting all four values to the correct numbers, plus the actual camera ar/fov is _only_ derived from the ar fields, but not the size fields (what you won't notice, since you can't break their connection by manually putting in values). all together i needed to make sure that at least the ar values fit, otherwise, the cameras fov and crop would be different in ds viewport and octane.
reading these values back from ds is not really possible because of some reasons:
- while sizing to viewport is on, octane of course needs to control these settings, to have fov/ar and crop in sync.
- because of th x-size y-ar connection in the ds parameters, you will get input loops, since sadly the cameras use the exact other axis to determine the fov
- and i don't think it is a good idea to have the render size the only parameter controlled somewhere in a ds dialog.
putting it short:
- if you render in 3delight, you need to setup its values accordingly, don't care about octane
- if you render in octane, you need to set octanes parameters to your preferences, not caring about ds/3delight
...