My computer hard drive had a major melt down which cause me to have to install another "C" drive. I always have a back up of my scene collection so that when I reinstalled everything, including moving the scene collections back to the new "C" drive., Poser will not seem to recognize the folders. I have to set here for hours telling it where every little obj is, every material, even when they are all in the same folder as the pz3 is in and the back up that are created by poser. Each time it searches the main poser runtime, not the correct folder. So what can I do so that for a large scene such as My tea houseMy Dream House I do not have to direct it back to the same folder time and time again? Also poser now will not collect the whole scene and I literally have to copy almost every obj and material to the collection folder.

From my experience poser remembers the location of the resources used when the scene was created/saved and does not rescan the runtimes. Is it possible the folder names of the runtimes on the new drive differ in name from from the original ones? For textures its possible to check the folders being scanned as they are display when attempting to load a texture (there should be a drop down box next to the file select option).

what is the location of your runtime? please see this thread - it may help.

file names is the same, hard drive name is the same, computer name is the same. poser had to be reinstalled with hd failure. but yea the infor should have been in the pz 3 file

it may be that you need to move your runtime depending on it's location.

the main runtime library is c :/ fiend/poser/poser 11. Though all of my other runtimes is on G drive which is a runtime for every type of runtime. Models, architecture, midfield, furniture, etc. My scenes that I create are in two locations. One is fiend, silo, tea house collection, etc for different collections. also my old collections are on N drive scene collections, which can be copied to any location and checked with win merge. I build obj's constantly to create scenes which is always in silo. Once all the objects and material is moved to one location, I carry it into poser to create the scene. Then to try and sell the objs in the scene, I use posers scene collector to ensure everything is correct. That is now going haywire.

I will pass this to the devs to take a look at.

thanks

I have edited the script - this SHOULD work.

you say this should help, is that in creating new collections, or recovering old collections? Either way thank you

It should make the script work properly - so in creating new collections.