Thanks mjc, I ran out of breath (energy really ;p ) before I got to that part. Usually DS will complain if it doesn’t find the texture and you can just point it to the texture which will update the path in the file. Same goes for the obj if loading a poser or daz file and it doesn’t see the base obj. That’s why it is frustrating to me when artists use unintuitive naming conventions for their obj/texture folders and worse, use multiple since they can’t seem to remember how to spell their own (shortcut for their own) name sometimes. It makes it a royal pain to fix broken files.
One of my absolute hates… ! name, !! name, !!! name and so on.
If I plan on using a texture/image on more than one item, I’ll place it in the textures/mjc folder. If it’s going to be used on just one item it will most likely be textures/mjc/item_name/textname.(format extension), all in lowercase letters…yeah, hey, it’s not ‘artistic’...but any OS/99% of the apps in the world can find it. And who really cares if my name is the top of the heap of thirty bazillion texture folders.]
Another tip…naming materials and their associated textures the same is a GOOD IDEA. Naming a shirt collar material collar is pretty straightforward. But naming the texture used by that material BN950XJ32.jpg is absolutely nuts, especially when the button texture is CR853.jpg…of course the sleeve in this example would be FT693 B54.jpg. We aren’t trying to keep the secrets of McDonald’s ‘special sauce’ out of the hands of the North Koreans or anything…
Spaces in file names are a BAD IDEA. Not every OS/version OS/file system or program can deal with them. Just because the version you are currently using can, doesn’t mean the next update will. The same thing for letter case. If you must pick one, pick LOWERCASE letters and make sure it is used consistently. Don’t in one place load Collar_txt.jpg and save the texture as collar_txt.JPG. Some OS/file systems will most definitely throw a wobbly over that…and for me, running on one of the pickiest, that simple thing resulted in lots of ‘broken’ files.
The naming ideas should be rules…not like ‘law of gravity’, more like ‘don’t run with scissors’, type rules. With file names we aren’t looking for ‘artistic’, we want functionality on the widest range of systems/conditions…so that means stick to the most simple, straightforward, basic means of doing so as possible. Save the ‘fancy’, artistic stuff for the actual content/texture files, not their names.