Hello all!
This isn't strictly a Vray issue that I'm having but since you guys are always so helpful I thought you might be able to help me eliminate Vray as the source of the problem
I've recently switched to an full 32bit workflow mostly due to the information and reccomendations from this forum and I must say it is very helpful, But i've run into a snag and I'm not exactly sure where the problem lies.
I'm rendering to 32bit unclamped RPF's with vray frame buffer and bring them into combustion.
In post i'm applying lighting changes ,DOF and RPF blur. Something weird is happening. In combustion I can make lighting changes with the 32 bit data so I know its working and everything seems fine but when I use the DOF and RPF motion blur or glow it doesn't seem to be using the 32bit data( lights aren't blurring and blowing out like they should in 32 bit they're just smudging like crappy max vector blur. It seems to be clamping the data and THEN applying the opperator. has anyone run into this problem before?
This isn't strictly a Vray issue that I'm having but since you guys are always so helpful I thought you might be able to help me eliminate Vray as the source of the problem
I've recently switched to an full 32bit workflow mostly due to the information and reccomendations from this forum and I must say it is very helpful, But i've run into a snag and I'm not exactly sure where the problem lies.
I'm rendering to 32bit unclamped RPF's with vray frame buffer and bring them into combustion.
In post i'm applying lighting changes ,DOF and RPF blur. Something weird is happening. In combustion I can make lighting changes with the 32 bit data so I know its working and everything seems fine but when I use the DOF and RPF motion blur or glow it doesn't seem to be using the 32bit data( lights aren't blurring and blowing out like they should in 32 bit they're just smudging like crappy max vector blur. It seems to be clamping the data and THEN applying the opperator. has anyone run into this problem before?
Comment