There is about 500 - 1000 texture listings in every map file; so that could take a while if I had to do that every time a map is patched or edited. I could do a regular expression job, but that would have to get done every time I export a map for testing as well.
No worries; I am using MapScape for test work; it will not be long until I get X-Producer's 3D exporter functional.
Quote: "I don't trust to "automatic" loading."
I find it handy; any discrepancies can be handled using the Limb Texture Name command.
To be honest, the real reason I wanted it to work is because the textures have attributes, shaders and behaviors attached to them in the engine; 9 times out of 10, a texture simply points to a shader application and is extended or replaced by other textures.