[GZDoom 4.0.0] Glitchy rendering with FXAA on
Moderator: GZDoom Developers
Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
Re: [GZDoom 4.0.0] Glitchy rendering with FXAA on
I see. What should we do with my "workaround" then?
Re: [GZDoom 4.0.0] Glitchy rendering with FXAA on
Your fix is correct - removing the discard keyword solves the problem. I do wonder in which situations the discard would work, though. Maybe the FXAA shader was originally made with the assumption the last shader would be rendering into the original frame buffer image. Probably under the assumption the game engine used a more classical setup where all postprocess ends up in the swap chain backbuffer.
Maybe also why they made it optional with that define?
Maybe also why they made it optional with that define?
Re: [GZDoom 4.0.0] Glitchy rendering with FXAA on
Here is the description for this #define in the original source code.
Probably, I got it wrong during addition of FXAA. Or maybe it worked by occasion, and I left it defined.
Probably, I got it wrong during addition of FXAA. Or maybe it worked by occasion, and I left it defined.
- Graf Zahl
- Lead GZDoom+Raze Developer
- Posts: 49073
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: [GZDoom 4.0.0] Glitchy rendering with FXAA on
I once read in a technical paper from NVidia that they do not have different image layouts and therefore transitioning is a no-op on their current hardware.dpJudas wrote:I strongly suspect most image transitions do nothing on NVidia, which means the original contents were probably just the contents from last render (like with the OpenGL backend).