kayjay.. Here is what I have found concerning .cr2 and .pz? files. If I have a .obj or texture file referenced with the path as such :runtime:geometries: ........ I am prompted to search for the needed file. If I put in the actual path of the object in the .cr2 file such as below ... h:poser4runtimegeometries ...... then the file is automatically found and loaded without any intervention from me. If you will notice that when you are prompted for a file location the path will look something like this /runtime/geometries/ I consider that to be poor programming ( the " /" ) on the part of DAZ, sorry about that folks, I am a hugh fan of DAZ, but I also program in C and when I see something like that and I am experiencing file and directory parsing problems, I consider it poor programming. Parsing a path is basic to any file operation and there should never be a coding error in that respect. I suspect as I have stated in another thread, that when DAZ corrects what I believe to be file and directory parsing errors, then they will probably clean up a number of 'odd' bugs. BabaLouie