Ok been using poser 6 and 7 on the mac for a while now and one problem that keeps cropping up is when you load an item into poser, or new textures, or prop. Certain ones keep asking for you to find textures as poser says it can't find them.  Thing is if you check the paths in the poser files they are correct.  Now we've got quite a few external runtimes but it doesn't seem to be across the board. Most things load in fine. Its just some items seem to lose the path to the textures even though the path in the file is correct.  It drives me nuts when you have to keep finding texture files when you either load an item or render it.

 Has anybody got the same problem. We've got too much stuff to just put in all in the main poser runtime.  Is there anything we can do to sort this or is it just poser and the way it handles paths?

 Help!

I'm going crazy here

This is a common problem among users. The way Poser locates textures (and objects) is a bit obscure and it is very easy to make (very small) mistakes.
There are two ways to correct the problems.
Firstly it possible to simply save back any failing prop after you have loaded it and helped Poser to find the missing elements (this will generally fix the problem) but this is a lot of work as you will have to take care to maintain the link between the icon and the file and you must make sure the whole prop. Keep in mind that in most cases files contain relative references, you can always replace them with absolute references (Poser does understand these although it would never use one itself). Another thing to remember is that Poser is very sensitive to exact file names, far more sensitive than the OS tools (even on a Mac).
The second way would be to use one of the tools to correct the references (i did notice you're working on a Mac and most tools are only available for the PC).

If you find a tool for the Mac I do advise you to get it and use it. It remains surprising how many incorrect references exist (even in the core Poser content).

Also, if you're installing to external runtimes, make sure the appropriate runtime is loaded when you call up the prop (figure, hair, etc.).

About the only time P7 asks me for a texture is if I'm opening a scene and don't have the appropriate runtimes open in P7.  Even the deep scan sometimes fails to find the textures if they're in an obscure folder.

I use a PC but, from personal experience, that a utility text editor is a must have.  I use EditPad Pro because it will read any pz2 file out there and give me a chance to check the paths if I have a hard time finding a texture.

Also make sure that you added the correct folder as external runtime - the folder containing the folder called "runtime", not the rolder called "runtime" itself.

I wrote a script in python that does verify relative paths . I could make that available if you think you need it .   Poser is a bit nasty because its hard to actually test that path names are correct , poser searches for them , and if the developer isnt careful they can work with errors in the path name.

Correct referance does this check but an easier way is to use Daz Studio. It didnt search, if the path is wrong you get an error .

Poser seems to take the relative path , and test each runtime with that path , then do a general search .

After I move files I run CRPro from Hogsoft.com and it fixes all the paths (plus cleans up the files).  I don't know if it works on Mac.

I have used CR and PFO and checked the absolute paths to find they are in fact correct and still Poser 7 will not find textures even in the primary runtime fairly frequently! I have to use 2xExlorer to search up the texture for Poser. 

Urgh. It's annoying. I have external Runtimes. P6 worked fine until I updated to SR3, now it can't any texture that's not in the default Runtime. grrrrrr

Is there a way to fix this on the Mac?

Does the New Poser Pro for Mac still have this problem?

Have you got DEEP selected in Poser 7  for the search ?  It became a selectable option in Poser 7 and if you try less than deep you can get odd errors occuring .