I will probably try to, the issue I have right now with the GDV NTSC is that the GDV shaders (crt-guest-advanced.slang & linearize.slang) are different than the GDV NTSC shaders (crt-guest-advanced-ntsc.slang & linearize-ntsc.slang), rather than one shader with some parameter adjustments. So it is possible for me to maintain 2 versions of my adjusted GDV shader, but the bigger problem is that they require different shader chains. I would really like to be able to add NTSC to the chain so that it’s something that can be completely turned on or off, otherwise it means more base presets and less flexibility.
@guest.r could you chime in on what they think about the adjustments in crt-guest-advanced-ntsc.slang and if they could be folded into crt-guest-advanced.slang, or what the reasoning is behind keeping them separate.
I do have NTSC Adaptive passes set up to swap out with GTU, I’m not sure if NTSC Adaptive is doing enough for what GDV-NTSC is currently able to do, I’ll probably make an experimental preset with NTSC-Adaptive in the next release. The other question is would people be happier with NTSC-Adaptive or would this lose what they like about GTU.
The setting on GTU is just the default, so we could perhaps change the default to be something better, do you think something like you would use for Dreamcast would be a good default? What do you use for this?
But if what you really want is different values for 240p and 480p content then we could definitely add a multiplier which would come on when we reach the trigger res