> I believe there is an issue with this in that if you make a copy and the shader gets
> updated in a future release, your shader won't have those changes (and I believe it
> is possible for the copied shader to break in this regard). The configuration and
> implementation of the shaders needs to wholly be separated, like the HLSL
The shaders right now have three parts basically: compiled binary shaders, json effect files that correspond to the compiled shaders, and the shader chain file that defines the order of the effects (and other stuff) for a shader chain and also has the configuration options.
If you separated out the default options into another file then things would now be in four places. And all four would need to match for things to work. So that doesn't really solve any problems at all.
But more importantly, people need to deal with things the way they are now and not how they'd like them to be. Which means copying the shader chain file if they want to have multiple sets of options saved.