Hi Jaberwocky,
I agree with you that the settings in the 'camera' and 'mesh preview imager' need to be more 'linked'.
But I don't see any logical reason to link the apperture with focal depth. These are indipendent values that need no linking in photography.
What definately needs a linking is the apperture, shutter speed and exposure value. So when you change one value, at least one other value (of the other two) has to change accordingly. The exposure value is a logarithmic product of the shutter speed and apperture/fstop so this is linked anyway. You might ask where is the shutter speed, and it seems that this important thing does not exist in octane! On the other side the apperture exists twice, because apperture (Mesh Preview Imager) and fstop (camera) is the same! That is indeed very strange.
Also some of the values are wrong like you have addressed correctly. The apperture / fstop should start with below 1 (not 1.2 in my view) because you can get a very expensive Leica lenses which start with an fstop below one. I wouldn't constrain the iso to specific value steps. But I would at least allowing an iso of 6400 or higher (25.000).
I would not like to have more graininess with a high iso. A good camera shows little visible grain in high iso (like Nikon 3Ds). So this is something for the post. But a grain slider could be a nice feature like we have vignetting. (Also vignetting is linked with the apperture / fstop in reality but I would not go so far and keep it flexible.)
But there is one important linking and I think this is what you have meant. The linking of the depth of field effect with the apperture/f stop. Yes that is definately important. They have already named it apperture but the fstop attribute in the "mesh preview imager node" makes no sense then.
This is CG so I really think that a software can be way more flexible in terms of what values can be put in but some relations of values should be represented in the behaviour.
Another important thing what I have said in an earlier post is that I don't think it is a good idea to put the iso, fstop, exposure into a node outside the camera. These are camera specific values and should stay in the camera node. Especially when you deal with multiple cams with different values it makes work easier.
Any other suggestion appreciated.
Cheers
Refracty
Jaberwocky wrote:Another query.This time more of a logical one than a bug.
In a real camera analogy a depth of field is created by the lens aperture.
F1.4 is very fast letting in lots of light but with a very shallow depth of field.
when you get down to around F22 you have almost infinite depth of field but requiring a longer exposure to get lots of light to get an image.
Surely these two controls I have highlighted in the attachment should really be set as one slider only, if the Camera lens analogy is going to work.This slider should really be labelled as a series of F stops from say F1.2 to F22.
You already have the autofocus point eye dropper tool on the tool bar to focus the lens on the relevant point in the scene , as an autofocus lens would in real life.Couple that with the aperture slider described above. That should duplicate a Camera lens correctly.The remainder of the camera controls you already have.The ISO Slider should be re label'd to ISO settings 64 / 100 / 200/ 400 / 800 / 1600 / 3200 / 6400 as they are currently on most Digital SLR's.The scene image would get progressively grainier as the slider approach's the higher ISO values. This way anyone who uses octane and who also does photography should instantly be able to replicate a photographic situation.
The current interface sort of smacks of over complication.
Any other views on this suggestion ?
) and also pan and zoom in big res. ideally of course you set up everything in a small res and then change up to render the final, never the less...
...although I just did something now where the view is now all white no matter what resolution...hmmm... what was that I did...something to do with recenter and reset to original view... 
