DOF & camera export problem with BETA 2.48

[vipvip]

At first, congrats to this new version: execpt some heavy bugs like alpha channel missing, the renderind speed is excellent on multiGPU (2 x gtx470) and i dont have the animation stopping bug during animation calculation after 3-4 frames calculated ( this bug was present on 2.46b cuda32 but not on 2.44 cuda30, (win7 64b) ).

But i have a big problem with 2.48:
when i adjust the point of depth of field and save the ocs, it doesn't keep it when re-rendering the picture ( the picture is very blurry with high aperture values ).
To correct this, i'have to uncheck 'export camera' and it works but the big problem is: no more camera animation possible...

So that it's actually impossible to render animation anymore ( with blurry DOF effects) i've tried to check the focal distance, and even the autofocus option is not memorised...This procedure was working before.

I export with maya and lightwave 10.1: same problem... i think it's an ocs problem...

just another suggestion ( i know it's not the good topic ) for the DOF chapter, is it possible to add a control for the sharpness depth plane ( control the lenght of sharpenning ) ?
-> sorry for my english

[face]

At first, congrats to this new version: execpt some heavy bugs like alpha channel missing, the renderind speed is excellent on multiGPU (2 x gtx470) and i dont have the animation stopping bug during animation calculation after 3-4 frames calculated ( this bug was present on 2.46b cuda32 but not on 2.44 cuda30, (win7 64b) ).

But i have a big problem with 2.48:
when i adjust the point of depth of field and save the ocs, it doesn't keep it when re-rendering the picture ( the picture is very blurry with high aperture values ).
To correct this, i'have to uncheck 'export camera' and it works but the big problem is: no more camera animation possible...

So that it's actually impossible to render animation anymore ( with blurry DOF effects) i've tried to check the focal distance, and even the autofocus option is not memorised...This procedure was working before.

I export with maya and lightwave 10.1: same problem... i think it's an ocs problem...

just another suggestion ( i know it's not the good topic ) for the DOF chapter, is it possible to add a control for the sharpness depth plane ( control the lenght of sharpenning ) ?
-> sorry for my english

It should be correct, the values from the export script overwrites the values which are written in the ocs-file.
That give you the way to animate the values with you 3d-app.
You must only enter the values from Octane in the export scripts and it should solve your problem.

Another way is, that the script-developers can insert an option to disable the lens-export.

face

[vipvip]

thanx for your answer
i agree with you abd it was the case with previous versions.
The trouble seems to be with this 2.48 beta...
in fact it seems to be bad interpretation between exporters and octane....
otherwise, this version seems to be excellent for anim: much much speed ( rendering, voxelising and export ), animated grain with PT rendering ( before the grain was fix, less photographic...)
Just this portal attribute is a bit mysterious... hope a tutorial soon ( i tried the roeland explanation but no real results....)

[face]

Haven´t test the focal depth option, but the aperture works correct.
Maybe it is the new port in the camera node.

- added focusDepth to camera node which defines the depth of the plane in focus, if "autofocus" is enabled the focus depth gets overridden by the autofocus

face

[abstrax]

Please see my reply in the beta 2.48 thread:
http://www.refractivesoftware.com/forum ... 701#p57701

Cheers,
Marcus

[SamCameron]

I have the same problem here, I'm using Blender, previously it was working fine, now I cannot setup a DOF target, simply goes crazy.

[pixelrush]

any likelihood of test 'B' today?

[abstrax]

any likelihood of test 'B' today?

Yes, still working on it, but it looks good.

Cheers,
Marcus