If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Exciting News: Chaos acquires EvolveLAB = AI-Powered Design.
To learn more, please visit this page!
New! You can now log in to the forums with your chaos.com account as well as your forum account.
Do you have a denoiser on as well? If so, is its multiplier less than 1? I've had issues in the past where enabling the lens effects forced the denoiser to full multiplier regardless of its actual value. I thought this was fixed though as I haven't had this problem for a while.
www.dpict3d.com - "That's a very nice rendering, Dave. I think you've improved a great deal." - HAL9000... At least I have one fan.
Do you have a denoiser on as well? If so, is its multiplier less than 1? I've had issues in the past where enabling the lens effects forced the denoiser to full multiplier regardless of its actual value. I thought this was fixed though as I haven't had this problem for a while.
I do, but only at .2. When Lens Effects hits, it is like having the Desoiser at 100%—the denoiser can be on or off; it doesn't matter, but I have a Denoiser in the stack. I am using the NVIDIA solution, so I'll try changing that.
Yeah., that's the problem I encountered as well. I THINK I may have worked around it by checking/unchecking some options on the lens effect settings: interactive, create lens effect channel, or something (I can't really remember). I'm using Intel denoiser btw.
www.dpict3d.com - "That's a very nice rendering, Dave. I think you've improved a great deal." - HAL9000... At least I have one fan.
I managed to reproduce the issue. It seems Lens Effects' "create effectsResult channel" overrides the Denoiser layer's opacity. Logged as internal tracker id: VFB-158.
Well that explains why I never use Denoiser, I always get the shitty result and create effectsResults channel is always on. I just though the denoiser was horribly bad but turns out it's a bug :facepalm:.
Well that explains why I never use Denoiser, I always get the shitty result and create effectsResults channel is always on. I just though the denoiser was horribly bad but turns out it's a bug :facepalm:.
I don't think there's a point to checking the "Create effectsResult channel" if you have the denoiser enabled anyways. Once the denoiser is enabled, an effectsResult channel is automatically generated and is always at 100% (as far as I can tell), only the RGB Color channel reflects the Denoiser opacity. Once "Enable Lens Effect" is checked, the lens effect is added onto the effectsResult channel, regardless of whether the "Create effectsResult channel" option is checked or not. All that seems to be affected by it is the influence on the RGB Color channel (which is where the error shows up). Maybe this would affect something if it's saved to a multichannel exr?
I don't think there's a point to checking the "Create effectsResult channel" if you have the denoiser enabled anyways. Once the denoiser is enabled, an effectsResult channel is automatically generated and is always at 100% (as far as I can tell), only the RGB Color channel reflects the Denoiser opacity. Once "Enable Lens Effect" is checked, the lens effect is added onto the effectsResult channel, regardless of whether the "Create effectsResult channel" option is checked or not. All that seems to be affected by it is the influence on the RGB Color channel (which is where the error shows up). Maybe this would affect something if it's saved to a multichannel exr?
This proves that it's way more complicated than it needs to be...
Comment