I’m just working on a multipass shader and I’m wondering if it’s possible to use the same parameters in different passes wihout having multiple GUI entries (feature request? =D). right now you have to change the corresponding parameter for every pass if you wanna change the value. which is kinda annoying especially with small step sizes.
The implementation currently doesn’t try to pair up settings which have the same identifier across shaders. The question is if it should merge settings. I guess the implementation should just ignore or throw a warning if the type/min/max/defaults don’t match up exactly in that case. Another alternative is creating a different identifier for matches to ensure there is no conflict, but then you risk having two settings with exactly same description in the UI.
Sp00kyFox, what kind of shader are you making that wants to use same setting across multiple shaders?
it’s a restricted blur filter where the kernel is seperated into three steps to speed it up significantly. the thing is that the shader just works fine with changing values over these steps, but it just doesn’t make much sense to do this.
Ah, so, a separable blur kernel with configurable kernel parameters? Ye, I guess it makes sense to merge the parameters in that case.