A Moogle  🏳️‍🌈 💻 🎮 🎶 🇸🇪

I know I follow some people who are all about shader tech, so I'm posing this question: If you had to limit the potential for photosensitivity triggers entirely in post-processing, on an engine using TAA, without the option to keep RT history, what would you do?

Do you by chance have a concise, accurate description of what specifically causes problems? I know strobing/flashing but that isn't good enough to act on :)

generally it is a frequency thing. the pokemon issue was the scenes in question alternated solid red and blue background shots every frame

and btw this is a little FIR playground if useful: http://demofox.org/DSPFIR/FIR.html 

Depending on the TAA, you may be able to do IIRs instead, or be stuck with them though, actually... IIRs: https://blog.demofox.org/2020/01/24/iir-audio-data-filters-featuring-biquads/ … Playground: http://demofox.org/DSPIIR/IIR.html 

Yeah TAA's reconstruction is generally IIR. Common weights for history: current is 9:1. That would do suppression on its own except taa also has to classify when it applies that filter, and a big change in intensity indicates to not apply the filter, otherwise everything smears

Honestly, any periodic animation on alternating frames is bad news (it also wouldn't aa properly) almost feel like it is more of an authoring issue. But I'd you wanted to reshade a game that's already been produced...I'm not sure