It seems that any opacity applied to the correction layers in the VFB are ignored when rendering on the cloud. We typically save out as RAW EXR with "save VFB corrections to RGB channel" ticked. Prior to uploading to the cloud we sometimes set the denoiser or lens effect opacity to 0.5. Since there is no current way to control it in post-production correctly when mixing with CC adjustments as well, as per this thread https://forums.chaosgroup.com/forum/...render-element.
But the resulting RAW file from the cloud which has the effectsResult.RGB ignores the opacity value and instead just puts it back to 1.0.
We can of course choose to not have "save VFB corrections to RGB channel" ticked and instead apply the VFB adjustments post downloading as suggested here: https://www.youtube.com/watch?v=2DGPR7ocXos
However manually doing this hundreds of times is an unnecessary pain. Especially when dealing with Cryptomatte as you cannot re-save from the VFB and keep the masks intact. Simple answer which seems favoured by many is to go back to the old way and have:
- tonemapped RGB without lens effects.
- tonemapped denoised RGB without lens effects.
- lens effects glare element separate.
- optional RGB without tone mapping just for reference.
Thanks,
But the resulting RAW file from the cloud which has the effectsResult.RGB ignores the opacity value and instead just puts it back to 1.0.
We can of course choose to not have "save VFB corrections to RGB channel" ticked and instead apply the VFB adjustments post downloading as suggested here: https://www.youtube.com/watch?v=2DGPR7ocXos
However manually doing this hundreds of times is an unnecessary pain. Especially when dealing with Cryptomatte as you cannot re-save from the VFB and keep the masks intact. Simple answer which seems favoured by many is to go back to the old way and have:
- tonemapped RGB without lens effects.
- tonemapped denoised RGB without lens effects.
- lens effects glare element separate.
- optional RGB without tone mapping just for reference.
Thanks,
Comment