System Information
Operating system: win 10
Graphics card: RX 6800
Blender Version
Broken: 2.93
Worked: 2.92
Caused by rB000a340afa67: EEVEE: Depth of field: New implementation
Short description of error
screen space reflections dont mix properly in the final composite, especially when mixing with ambient occlusion
Exact steps for others to reproduce the error
open in 2.92 and then 2.93 see the difference file i attached
Oh, forgot to mention. It has to do with screen space refraction for sure and possibly with irradiance as well.
Hello! Can you isolate this issue to a simple test blend file you can upload with replicatable settings to help developers a bit more? It's a little difficult to just work on an image alone. Also no disrespect against your artwork but perhaps you can make the demo file more SFW? I'm not too bothered by it but I can imagine other developers who would work on this regression might have issues with their comfort level. Thank you!
Hello I assure my art-work is very safe for work I have put blur where its not safe to look. I have tried to replicate the issue with simple geometry but alas it is not very obvious. So here I have isolated the area of the mesh from my screenshot where the issue is most obvious and uploadet that files.
We appreciate blurring it before posting it and while that does make it pass late daytime tv news standards that doesn't necessarily make it safe for work or not a comfort issue for other developers. If you are having trouble replicating it: try isolating the pieces of the mesh that appear to recieve an issue and deleting unnecessary geometry and simplifying materials. Usually developers work on small pieces of production files like this.
Yes I have done that already, I have uplodat the file is called untilted.blend you can download it now.
We appreciate blurring it before posting it and while that does make it pass late daytime tv news standards that doesn't necessarily make it safe for work or not a comfort issue for other developers. If you are having trouble replicating it: try isolating the pieces of the mesh that appear to recieve an issue and deleting unnecessary geometry and simplifying materials. Usually developers work on small pieces of production files like this.
YEs while its safe for the news it is safe for here like you said. Some people watch news if they work late shift and like you said this fits there. All is good.
YEs while its safe for the news it is safe for here like you said. Some people watch news if they work late shift and like you said this fits there. All is good.
Unfortunately that's not really how it works, you can't just send complete strangers nudity and blur it out and call it suitable for all audiences. You have to be more mindful of your audience and how they will respond. Others in the art community tend to follow this as well. Please don't argue on this point of common courtesy. I would like to see your problem addressed but you are making it less and less likely to be addressed by developers.
The glossy direct pass has incredibly high values in 2.93, in comparison to 2.92.
Some of the values are 500+. I’ll post comparisons in the morning. My first guess is that this change occurred with the EEVEE closure refactoring.
Can confirm, the behavior changed with rB000a340afa67: EEVEE: Depth of field: New implementation
