This is a question for radiance: are there any plans to implement a DOF control using f-stop values instead of the somewhat strange aperture slider? Currently, I have no idea how to correctly simulate for example an f2.8 @ 100mm or an f1.4 @ 35 mm
I'm used to this from my camera, and it would ensure realistic results when picking realistic f-stop values.
DOF control via f-stop
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
excerpt from the XSI thread:
Amplitude wrote:Last thing to do is to figure out the formula to convert a "classic" aperture value in f-stop used here to the logarithmic values used by Octane... any ideas?
Edit: according to this post the value used by Octane is the aperture Radius length (in mm?)So, the formula to convert the aperture should be:radiance wrote:does anyone have any information source or table relating those values to actual aperture radius lengths ?gristle wrote:I was wondering about the aperture control as well.
Maybe offer an option so you can use F16, F8 etc... in the same way it is planned to offer camera rot. in degrees.
Radiance
(fl / apt)/2 = o_apt
fl: focal length in mm
apt: camera aperture in f-stop
o_apt: octane aperture in mm
And it does seem to work there you have it, interactive dof control and on the fly convertion from f-stop to octane aperture!
Win7 Pro x64 | GTX 770 2GB + GTS250 512Mb | Intel Xeon i7 4x 3.4ghz | 16 GB ECC Mem | Intel SSD 520 | Dell 27"
SOFTIMAGE l 2011 + OCTANE V1.20
SOFTIMAGE l 2011 + OCTANE V1.20