Problems with MXAO in GTA SA

Hello everyone.
I have a problem with the incorrect work of MXAO.fx in GTA San Andreas (see the picture).

MXAO is not correctly displayed only in gta sa, with the rest of the games there are no problems.
Help to solve the problem pls.
Sorry for my bad English.

Huh, that's odd. Even more odd, considering that I develop my shaders on GTASA. What config do you use?

I hope I understood you correctly.

Reshade 3.0.8
[MXAO.fx]
bMXAODebugViewEnable=0.000000
bMXAOSmoothNormalsEnable=0.000000
fMXAOAmbientOcclusionAmount=3.000000
fMXAONormalBias=0.000000
iMXAOBayerDitherLevel=3.000000
fMXAOIndirectLightingAmount=0.000000
iMXAOSampleCount=24.000000
fMXAOIndirectLightingSaturation=0.000000
fMXAOSampleRadius=2.000000
fMXAOBlurSharpness=2.000000
fMXAOBlurSteps=2.000000
fMXAOFadeoutStart=0.200000
fMXAOFadeoutEnd=0.400000

Weird. Your AO Amount is a bit high but that should not cause this problem. How does the AO look with debug mode enabled?

With debug mode


This problem has appeared only now. Earlier, when I installed gta sa, MXAO worked correctly. I assume that it may be due to the update of Windows 10 Creators Update, since after the update I had to rename the .exe file in order for the game to start (e.g. gta-sa.exe, rather then gta_sa.exe).

UPD: It seems that I just solved the problem.
Here's what I did: In the properties of exe I set compatibility with Windows 7 and then renamed the exe one more time. The game started and the MXAO began to work quite correctly.
Marty, thx for your responding.

That's very strange. Shaders should execute same on all platforms. This looks like a ReShade bug, @crosire?

Eh, that's really strange indeed. Sounds like something in D3D behavior has changed in Win10. Forcing compatibility mode will load a shim with the old behavior. I wonder what though.