>> You never ever used a file monitor to see what Poser does... It only searches the whole runtime if the references in the files are completely wrong (and search depth is set to deep).

Whether it's searching or it's replacing the placeholders in the preview image, it still has to follow the paths to find the necessary materials -- which means reading the runtime to do so. Poser doesnt magically transport texture files -- it goes and finds them.

And yes, this is what Poser does. It doesnt retain information; it points to information and then goes and gets it. This is what a lot of 3D programs do, because it keeps the size of the master file down to a manageable size. Otherwise, you'd be looking at file sizes comparable to those in Bryce, which holds everything in one place and creates monster files in the process.

docandraider.com -- the collected cartoons of Doc and Raider