If you are looking up a texture parameter in a material instance by its index, then happen to update the parent material to have more texture parameters, the order of elements will change.
Say the original texture “A” has index 0. After adding the extra textures and converting them to parameters “B” and “C”, the original “A” will now be index 2.
This can be a problem if you are using Get (since it defaults to 0) to grab an element from a Texture Parameters array in blueprints, expecting the first added to be the first element always.
v4.9