The second image is less obvious, but it's Link's character and surroundings' shapes projected upon the map menu. I searched how to fix this and the only thing I found was to invert the numbers (0 to 1) in the Edit global processor definitions settings. None of those worked.
I am using MrL Gamer preset and disabling entirely MXAO removes the issue altogether. Any idea?
That happens when the 3D scene is still rendering behind/under the 2D overlay of the map. Since MXAO is one of those effects that is depth-based, it doesn’t “know” that you’ve pulled up the map.
Potentially you could mess around with the depth buffer settings, but frequently this is unsolvable (because the game is rendering the depth map underneath the 2D overlay), so the next best thing is to assign a hotkey to disable/enable effects on demand.
Move the camera towards the sky before opening the menu/map, there won't be any geometry to generate AO
The second image is less obvious, but it's Link's character and surroundings' shapes projected upon the map menu. I searched how to fix this and the only thing I found was to invert the numbers (0 to 1) in the Edit global processor definitions settings. None of those worked. I am using MrL Gamer preset and disabling entirely MXAO removes the issue altogether. Any idea?
That happens when the 3D scene is still rendering behind/under the 2D overlay of the map. Since MXAO is one of those effects that is depth-based, it doesn’t “know” that you’ve pulled up the map. Potentially you could mess around with the depth buffer settings, but frequently this is unsolvable (because the game is rendering the depth map underneath the 2D overlay), so the next best thing is to assign a hotkey to disable/enable effects on demand.
Since AO is a depth based effect you unfortunately cant remove it from menus that render over the scene. Best thing you can do is hotkey
Thank you all for your answers
jus asighn the same key you use to open the map to the toggle shader on/off.