Reshade 3.4.1MXAO BUG on gtaIV
- t-ru
 - Topic Author
 
		Less
		More
		
			
	
		
	
						7 years 2 months ago		 -  7 years 2 months ago		#1
		by t-ru
	
	Reshade 3.4.1MXAO  BUG on gtaIV was created by t-ru
	Hello everyone, congratulations to the Reshade Team, this is just a great work, fantastic shaders!
I have a problem with MXAO v.3.4.1 I didn't tried previous version.
The bug is that instead ambient occlusion there is a burned squares on the textures, no matter what settings are adjusted:
I was thinking because of the Enb series but I tried on the stock game 1.0.7.0 and it's the same!
Edit:
The windows is 8.1 64bit
and this's from the log file:
16:32:19:825 [01452] | INFO | Compiling '
\gta4\Grand Theft Auto IV\reshade-shaders-master\Shaders\MXAO.fx' ...
16:32:20:202 [01452] | WARN | > Successfully compiled with warnings:
\gta4\Grand Theft Auto IV\Shader@0x0FDA94A0(78,10-20): warning X4008: floating point division by zero
\gta4\Grand Theft Auto IV\Shader@0x0FDA94A0(78,10-20): warning X4008: floating point division by zero
\gta4\Grand Theft Auto IV\Shader@0x0FDA94A0(78,10-20): warning X4008: floating point division by zero
	I have a problem with MXAO v.3.4.1 I didn't tried previous version.
The bug is that instead ambient occlusion there is a burned squares on the textures, no matter what settings are adjusted:
I was thinking because of the Enb series but I tried on the stock game 1.0.7.0 and it's the same!
Edit:
The windows is 8.1 64bit
and this's from the log file:
16:32:19:825 [01452] | INFO | Compiling '
\gta4\Grand Theft Auto IV\reshade-shaders-master\Shaders\MXAO.fx' ...16:32:20:202 [01452] | WARN | > Successfully compiled with warnings:
\gta4\Grand Theft Auto IV\Shader@0x0FDA94A0(78,10-20): warning X4008: floating point division by zero
\gta4\Grand Theft Auto IV\Shader@0x0FDA94A0(78,10-20): warning X4008: floating point division by zero
\gta4\Grand Theft Auto IV\Shader@0x0FDA94A0(78,10-20): warning X4008: floating point division by zero
		Last edit: 7 years 2 months ago  by t-ru.			
			Please Log in or Create an account to join the conversation.
- Tojkar
 
		Less
		More
		
			
	
		
	Go to settings tab and change the preprocessor value depth inverted to either 0 or 1, depending on which one it already is.
	
		The following user(s) said Thank You: t-ru 	
			Please Log in or Create an account to join the conversation.
- t-ru
 - Topic Author
 
		Less
		More
		
			
	
		
	Thanks for the replay!
There is a 4 values:
RESHADE_DEPTH_LINEARIZATION_FAR_PLANE=1000.0,
RESHADE_DEPTH_INPUT_IS_UPSIDE_DOWN=0,
RESHADE_DEPTH_INPUT_IS_REVERSED=1,
RESHADE_DEPTH_INPUT_IS_LOGARITHMIC=0
I changed them ingame and do/help or change nothing!
Do i need to restart the game if i change them?
			There is a 4 values:
RESHADE_DEPTH_LINEARIZATION_FAR_PLANE=1000.0,
RESHADE_DEPTH_INPUT_IS_UPSIDE_DOWN=0,
RESHADE_DEPTH_INPUT_IS_REVERSED=1,
RESHADE_DEPTH_INPUT_IS_LOGARITHMIC=0
I changed them ingame and do/help or change nothing!
Do i need to restart the game if i change them?
Please Log in or Create an account to join the conversation.
- Tojkar
 
		Less
		More
		
			
	
		
	Yes, I meant that RESHADE_DEPTH_INPUT_IS_REVERSED value. After you've changed it, go back to the first tab and hit reload button in the bottom. That initialises the preprocessor values and reloads the shaders. Restarting the game would have the same effect.
	
		The following user(s) said Thank You: t-ru 	
			Please Log in or Create an account to join the conversation.
- t-ru
 - Topic Author
 
		Less
		More
		
			
	
		
	Yes, OMG, IT'S worked, Greetings man, I love you!!!wow Finaly!!!
			Please Log in or Create an account to join the conversation.