The last item on the list: ************************************* When an .obj file which is referenced by a .pz3 is moved, the user has to locate the missing geometry file. The new path the user specified is now saved to the .pz3, removing the need for loacting the file on every subsequuent loading of the .pz3. ************************************* Please DO NOT implement this, it's bad practice for an application to change the contents of files during the loading process, as any problem or interruption to the application or system may end up corrupting previously good data. Loading actions should always be carried out in "read-only" mode. If the user wants to avoid the problems of reloading a moved object file (or for that matter texture files), then the simple option of resaving the pz3 should suffice without needing the introduction of a potentially corrupting mechanism. Bill

IIRC the pointers weren't updated to the "found file" location in the past when the PZ3's were saved, and people (rightly IMHO) complained about this. My interpretation of Katherine's statement, which I think should be implimented, is that the pointers to re-located files WILL now be saved within the .pz3 rather than the old out-of-date-and-incorrect pointers remaing and causing the users to have to locate stuff again and again.

And for this change alone, I will be truly grateful!

I was aware that this have been what is intended, just that the actual statement (with continual reference to 'the pz3') seems to indicate otherwise. Bill