Hi there,
It would be really helpful in blueprints (or even c++ for that matter) to mark a certain collection (set or group) of materials as of being of the same type (some kind of tag that you can add, just like asset tags, I know that an interface is just overkill, maybe). This can be really helpful for blueprints that get/set material parameters on a material instance. The problem is that if a parameter is part of the material, it fails silently to update values or returns a default value in the case of a “getMaterialScalar/TextureParameter()”.
A case where this could be applicable is having a blueprint that manipulates a material instance dynamic reference behave differently based on the base material type, getParent() would create a huge if and else chain that is just not practical in modern programming paradigms/techniques.
Does anyone share the same sentiment?