Hello,
I would like to suggest linking the DAZ DoF control to octane. Currently it is very easy handling DoF with DAZ (especially with the F/Stop plane). These changes in Daz however do not translate to Octane. I understand that the same controls exist in Octane. However when making changes in Octane, these do not show on the DAZ Viewport.
So the current workaround is to make all changes with DAZ DoF and then copy the settings over to the Octane parameters.
So my request is simple: Can the DAZ DoF Settings be directly linked/copied/applied to the Octane DoF settings?
Feature Request: Link Daz DoF to Octane DoF Parameters
Moderator: BK
Forum rules
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.
they were once linked, but it didn't work that well; the common sense back then was that the results are barely comparable, so the oc cam aperture should not be linked to the daz fstop.3dmania wrote:Hello,
I would like to suggest linking the DAZ DoF control to octane. Currently it is very easy handling DoF with DAZ (especially with the F/Stop plane). These changes in Daz however do not translate to Octane. I understand that the same controls exist in Octane. However when making changes in Octane, these do not show on the DAZ Viewport.
So the current workaround is to make all changes with DAZ DoF and then copy the settings over to the Octane parameters.
So my request is simple: Can the DAZ DoF Settings be directly linked/copied/applied to the Octane DoF settings?
apart from that in studio changing the fstop does also move the focal point, where octane will always focus to the exact point given by the distance, so this also translates not very well.
is from your experience using a fstop value from daz in octane giving similar/expected results in octane?
„The obvious is that which is never seen until someone expresses it simply ‟
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
- linvanchene
- Posts: 783
- Joined: Mon Mar 25, 2013 10:58 pm
- Location: Switzerland
edited and removed by user
Last edited by linvanchene on Fri Sep 05, 2014 3:07 am, edited 2 times in total.
thanks for the great explanations!

- an additional focus mode that combines node selection and the surfaces focus distance which i get from the viewport click (in other words a "see through" focus)
- additional abilities to set a focus area instead of only a focus point, or even multiple focus points, and to also freely move the focus point/area within the view (just like real cam autofocus controls)...
that would be indeed great. from my pov it is also a logical step at some point. of course there is a lot of other homework to do until such features literally leap into viewlinvanchene wrote:What I am hoping to see in the next years is that render engines actually start to integrate data from real live camera manufactors like Canon, Nikon, Sony, Zeiss, Tamron.
Instead of just selecting 50mm F 1.4 the users will be able to select a specific lens from a preset menu (like SAL85F14Z ) that will then include all the information even with option to correct Chromatic aberration or keep it as produced by the actual lens.

i was always keen to know if the f/stop translation works in mimicking real world f/stop values; the oc "thinlens" cam is based on a pinhole model, with only a variable aperture, so the f/stop value i implemented for the daz plugin is just an approximation (i am used to think in f/stop numbers, so the -reverse- aperture value was always a tad to synthetic for my taste).linvanchene wrote:I find the current approach of OctaneRender great because instead of making a compromise they offer both realistic camera values and also simple controls.
Those users who are familiar with photography will find that focal lenght, F stop, aperture will more or less behave as expected.
what is on my rather long list of "nice to have" islinvanchene wrote:One issue with that system is that sometimes scene objects interfere with the viewport selection.
A quick workaround is to quickly switch those object invisible in the DAZ scene tab, adjust focus and done.
- an additional focus mode that combines node selection and the surfaces focus distance which i get from the viewport click (in other words a "see through" focus)
- additional abilities to set a focus area instead of only a focus point, or even multiple focus points, and to also freely move the focus point/area within the view (just like real cam autofocus controls)...
„The obvious is that which is never seen until someone expresses it simply ‟
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400