Static Bool Parameters in Material Parameter Collection

[user37337]

@pvz2015;412614

Don’t feel bad user37337, usually nobody replies to me either

I don’t understand why you can’t use the current static bool parameters in material instances. I’m thinking: make two material instances, one each way, controlled via the static bool. Then on the object you can set whichever version you want via something like UMeshComponent::SetMaterial.

This is possible but it isn’t very useful when updating e.g. thousands of foliage instances.

@Allar;413103

A Material parameter collection is meant to be able to be manipulated at runtime.

Static bools are meant to be manipulated at shader compile time.

These two concepts don’t really play well together. You would have to recompile shaders at runtime for all the materials with a static bool change, which is a bit… much.

That being said, I’d still like the ability to do this, but it might be a bit impractical.

The Permutation System for this feature already exists. All variants have to be compiled in editor or when cooking. Its the same like the “Quality Switch Node” that works great. So they “only” have to implement custom static switches equally to the quality switch.