search

JakobPCoder / ReshadeTFAA

This is a work in progress Reshade shader, which acts as an addon to other, non temporal, anti aliasing methods. Only works dx10+ maybe
Other
49 stars 6 forks source link

Black screen when TFAA is enabled #5

Open justinjanitzek opened 2 years ago

justinjanitzek commented 2 years ago

Older version works fine but this new one just gives me a Black Screen

IAmLizzy commented 1 year ago

Can confirm that this is now happening. I doubt this has anything to do with the issue, but it seemed to work fine until I deleted ppfx_ssdo from my shaders folder, adding it back in however did not fix it. (I do not know how to code and this is my method of trying to fix things sorry for being dumb lol) But yeah, it was working perfectly fine before and then suddenly it wasn't. Before it showed a warning that ppfx_ssdo has already created a file/image or something like that, now it shows these. Screenshot_309

niuyanghu commented 1 year ago

Can confirm that this is now happening. I doubt this has anything to do with the issue, but it seemed to work fine until I deleted ppfx_ssdo from my shaders folder, adding it back in however did not fix it. (I do not know how to code and this is my method of trying to fix things sorry for being dumb lol) But yeah, it was working perfectly fine before and then suddenly it wasn't. Before it showed a warning that ppfx_ssdo has already created a file/image or something like that, now it shows these. Screenshot_309 I have the same problem

jabolcni commented 1 year ago

I also get just black screen.

Spacellary commented 1 year ago

Update: GShade is no longer maintained and should be avoided at all costs due to security concerns.

For GShade users this was fixed in version 4.0.4, this was the commit with the change https://github.com/Mortalitas/GShade/commit/df5871b0c992eacfb56809cf98df2af83776ddc7.

It was as reported here. texExpColorBackup pooling was disabled.

Apparently lines 44 and 45 of TFAA.fx are mutually exclusive (at least that's the behavior for me), can't have both enabled at the same time, so pick your poison... Line 45 is recommended to be disabled.

Line 44 or 45 here, only one should be true while the other set to false:

https://github.com/JakobPCoder/ReshadeTFAA/blob/1a16bdc4d1aa058fe3e2881554a5d79e5164dee8/TFAA.fx#L44 https://github.com/JakobPCoder/ReshadeTFAA/blob/1a16bdc4d1aa058fe3e2881554a5d79e5164dee8/TFAA.fx#L45 ...Only having one or the other enabled made it not a black screen for me.

But I do have quite the distracting distortions happening mostly at the corners of my screen with qUINT_motionvectors. Is that working as intended?

UPDATE: The issues I had with corner distortions were all fixed simply by using the original DRME with this fix applied.

If you are using GShade, as of versions 4.0.4 or around this time I do not recommend using the included qUINT_motionvectors, and instead using the DRME shader I mentioned just above.
- Final Fantasy XIV (DX11)
- GShade 4.0.4
- My system information.

Update: GShade is no longer maintained and should be avoided at all costs due to security concerns.

mhtvsSFrpHdE commented 1 year ago

As a temporary workaround,
You can disable performance mode, enable performance mode, disable, enable
fast click click click click click on that button

You may be lucky to find it to work. One of my game always start with black screen but other game is fine One day I try to disable performance mode, and it's no longer black and works fine,
enable performance again, it doesn't black either. But once game is restarted, it keeps black for unknown reason.

I use ReShade 5.3.0.