Thanks, millighost. My first reaction to your post was, "That cannot possibly be right!" but apparently it is. This is from the Poser Manual:

• File Search: When an object is loaded from the Library, Poser searches for all the associated files included with that object. The File Search options allow you to configure the extent of that search. These options are:

• None..: Selecting None disables file searching; this option is useful for testing the accuracy of newly developed content.

• Shallow.: Selecting Shallow will reduce the amount of time spent searching for missing or mislabeled files, but will increase the instances of files not found.

• Deep.: This is the default File Search setting. We recommend that you select Deep file searching, as this option initiates the most extensive searches for content file components, hence increasing the likelihood that missing or mislabeled files will be found.

That doesn't really tell you much, but my tests pretty well confirm what you said, and I have to say - What a terrible, terrible idea. What were the developers thinking? Good lord, no wonder Poser is so slow. You have to wonder how many other bone-headed, inefficient, useless "features" are built into the code. Forgive me for ranting but ~!@#$%^&*()+!!!!

Even when I set "File Search" to "None" it still seems to go looking for the file outside of what is stated in the referring object.

Also, I'm not sure what you are saying with, "Most commercial objects for poser contain texture references like this.", e.g., "C:BRuntimeTexturesB.png". All the references I've seen are in the form of:

":Runtime:Textures:::"

None have the device name , e.g., "C:" appended.

 **
**

---

OS: Windows 10 64-bit, Poser: 10