SimonJM wrote:First off, great product! Resolves a fair few issues I had using the standalone Octane engine ... well, standalone ...
A couple of minor 'gripes':
The installation of the plug-in seems to impact the definition of each and every camera, giving them, by default, DoF set to on, a focal length of 65 and an f-stop pf 5.0. Admittedly that is probably more realistic, but it does kind of assume that each and every render you'll be doing is going to be via Octane
it's because this is actually the octane focal distance slider, and the one of the daz camera gets hidden. now i also know why i did this. it is just one of a myriad of tiny problems doing this integration: daz studio alters the focal distance all the time under specific circumstances if you move the camera. and it doesn't do it in a senseful way, since it seems to always use a non-user-controllable camera target to calculate the focal distance. from my experiance, especially if watching the outcome live in the octane viewport (what you will never see rendering stills in 3delight), it looks plain erratic. in the end i decided to completely grab control of this parameter, add focus to and focus follow modes, to make best out of what is there.SimonJM wrote:LOL, I was just going to pretty much suggest the same thing!
I think I got a little turned round over the focal length as the camera settings get a little altered by Octane with the actual parameter I was thinking of (Focal distance) being hived off to sit under the OctaneRender sub-parameters.
yes, that was what bugged me too - having a parameter twice always makes users unsure about what to use and why; hamlet - you know? seems it always turns out to end in a dramaSimonJM wrote:So far as I know the f-stop parameter native to DS cameras bears no resemblance to real life, so I suspect as you mention leaving that alone and only affecting DS would be a good idea. Mind you, that then means a similar-named, un-linked, parameter specific to Octane ... hmmm, thorny issue! Could you 'take a stab' at conversion as/when DoF is set on, or having a 'Convert f-stop' button? How you'd convert'd be a bit of a stab in the dark, but I presume it'd be possible to do with ranges, setting the 'real' f-stop to Octane minimum when DS < 1, to Octane max when > 100 and suitable dealing with the in-bewteen bits?
Users browsing this forum: No registered users and 3 guests