Quote - > Quote - For distributed Poser content, things like:

F:MyPoserProductsProduct1RuntimeTexturesMyTexturesmytexturemap.jpg

aren't going to work on anyone else's system since it is an absolute and unique path.

Is this quite correct though Robert? For example, a prop on my system has the following path in the .pp2 file:

textureMap "C:Documents and SettingsDAVIDMy DocumentsPoserTempfolderzeusweproundshield.jpg"

But when Poser loads the prop, it finds the correct texture in the directory where it really is located. It seems as if Poser searches in the specified directory, and if it fails to find it, searches the current Runtime until it does. So it's certainly advantageous to use relative paths, because the amount of searching Poser has to do is reduced, but absolute paths won't necessarily stop the object working correctly.

Oh, you can use absolute paths for your own stuff and, if you're lucky, the files are in the same absolute path on your system as specified on the creators, it will work.  But other than that, the likelyhood of failure is highly probable.  Note that I used the example as, say, a product work folder and not one attached to Poser.  Yes, Poser will search through the available Runtimes - only if they are available to it.  Any old Runtime anywhere on the system will not work. I'm guilty of almost forgetting this myself on occasion when setting up distributed Poser content. ;)

Not certain if Poser 5/6 create absolute paths when using alternative Runtimes (those added to Poser), so this could also be a reason for the problem.  Then, as you note, the search feature will kick in and cause an interminable wait.

Robert

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone