Hi
When someone moves a texture and doesent repath it correctly Max has a list of search paths that it looks in such as the current working directory to see if it can find a file of the same name, if it does it uses that one and in the asset Tracker it is listed as “Found” even though it could be a completely different texture.
This is causing some issues for me because the asset in max looks correct because the Max has “Found” the texture, it will even give you a path back if you run
selection[1].material.diffusemap.filename
but it WRONG! its the file path that it was originally set to and the file does not exist
This is making it very difficult to export textures because i cant guarantee that the texture that is reference exists or is even the correct texture.
On top of this if i strip the file path with the asset tracker (ATSOps) the texture is still visible!
Is there a way if stopping this behaviur so that if a texture is not correctly mapped it will not display in the viewport? Or flushing cached (?) textures.
I have a possible way of doing this but its going to be very aggressive on the scene open callback so im wondering if anyone else has a better way handling this
thanks
Dave
hmm… the max shouldn’t search a texture in alternative places if this texture is defined with an absolute path.
(i don’t remember the mxs function but i remember it was there… it gets a texture path and returns the path which the max will use if it’s found)
ill have a look for that function Dennis but if you have a look at the ATSOps help page it references “search paths” quite alot and describes the exact problem im having, Max is trying to be helpful but is actually causing more issues (for me anyway) because its hiding whats its doing from the user
In Asset Tracking.
- Select All Maps
- Strip Path
- Make Path Absolute
Then max will resolve path and put the resolved path.