About the blend of effect

  • Posts: 153
1 year 1 month ago #1 by seri14
Why is different the effect whether displaying or not of ReShade GUI?
#include "ReShade.fxh"

float4 TestPass(
	float4 pos : SV_Position,
	float2 texcoord : TEXCOORD
) : SV_Target
{
	return float4(
		0.0,
		step(pos.x % 64,32),
		step((BUFFER_HEIGHT - pos.y) % 64,32),
		0.0);
}

technique Test
{
	pass
	{
		VertexShader = PostProcessVS;
		PixelShader = TestPass;
		
		ClearRenderTargets = false;
		BlendEnable = true;

		DestBlend = ONE;
	}
}

Please Log in or Create an account to join the conversation.

  • Posts: 3632
1 year 1 month ago #2 by crosire
There isn't?

Please Log in or Create an account to join the conversation.

  • Posts: 153
1 year 1 month ago - 1 year 1 month ago #3 by seri14
I tried again now, I noticed this problem is causing only by d3d11.
And do not put enabled technique after the Test.

Please Log in or Create an account to join the conversation.

  • Posts: 3632
1 year 1 month ago #4 by crosire
Still cannot reproduce this =/

Please Log in or Create an account to join the conversation.

  • Posts: 153
1 year 1 month ago #5 by seri14
Recorded.

Please Log in or Create an account to join the conversation.

  • Posts: 176
1 year 1 month ago - 1 year 1 month ago #6 by Daodan
Just tested it and I also see a difference whether the ReShade overlay is shown or not.
I used the Release App and the Snipping Tool to take the screenshots.
(The 'DrawOverlay' technique is just a shader to draw an image onto the screen)





One thing to note: when a screenshot is taken from within ReShade the result looks like in the first image - it doesn't matter if the overlay is enabled or not.
The following user(s) said Thank You: seri14

Please Log in or Create an account to join the conversation.

  • Posts: 3632
1 year 1 month ago - 1 year 1 month ago #7 by crosire
Are you both on Windows 10? I have never been able to reproduce any of the "things look different with UI on/off" bugs (e.g. the MagicBloom one) and am starting to suspect it's because Windows 7 DX11 is very different than Windows 10 DX11 (WDDM vs WDDM2 and all that fun stuff) and I just got lucky that it works on the former.

Please Log in or Create an account to join the conversation.

  • Posts: 176
1 year 1 month ago #8 by Daodan
Yeah, I'm on Windows 10.

Please Log in or Create an account to join the conversation.

  • Posts: 153
1 year 1 month ago #9 by seri14
I tried to reproduce this problem by installed Windows 7 on the same PC as when recording.

Please Log in or Create an account to join the conversation.

  • Posts: 3632
1 year 1 month ago #10 by crosire
Look at that. Will try and organize me a Win10 system for reproducing.
The following user(s) said Thank You: Wicked Sick

Please Log in or Create an account to join the conversation.

  • Posts: 3632
1 year 1 month ago #11 by crosire
Got me a Win10 system and well ... this was super easy to fix: github.com/crosire/reshade/commit/af860f...66af612b9b88a738deb5 . I just never saw that because that code path is explicitly disabled on Windows 7: github.com/crosire/reshade/blob/af860f3b...ntime_d3d11.cpp#L196 . Don't even know why anymore, but there must be a good reason ...
The following user(s) said Thank You: Daodan, seri14

Please Log in or Create an account to join the conversation.

  • Posts: 153
1 year 1 month ago - 1 year 1 month ago #12 by seri14
I'm verified.

Would you reproduce and fix for MagicBloom's problem on Windows 10?

EDIT:
found commit v0.18.5

Please Log in or Create an account to join the conversation.