ok I am near panicy! I was working on a piece.....everything was going great...hit render and it went through till it started to actually render the scene. then I got a wierld message popup telling me I was out of memory and needed to allocate more memory to poser??? I stoped the render and went to close poser..the dialog box to save or not to save the changes came up..I hit save...it closed. but when I went to reopen it...nothing there is nothing in the pz3! no lights no figures nothing at all! ok so I was going to take it as a loss...I went to a previously made pz3{ I am a fanatic about saving them} and.........NOTHING CAME UP it opened..it had the title..but no lights no figures nothing!!!!!!!!!!!! how do I fix this how to I make sure it doesnt happen again ....is poser possessed? how can I get my pz3s to work again??????

https://www.darkelegance.co.uk/

Commission Closed till 2025

Do either the corrupt PZ3 or the backup PZ3 open correctly after Poser has been restarted and/or the system has been rebooted? If you are using P4 or ProPack, this may be an instance in which deleting the .rsr files might help. Sometimes the .rsr files in Geometries may become corrupted. You might try deleting the .rsr files associated with any geometries used by your problem file. Try opening up the .PZ3 in a text editor to see if any information was saved. That will tell you whether the problem is the .PZ3 or Poser itself.... I have had the sort of problem you relate happen periodically with both P4 and P5. The only remedy I know is to save regularly as you work. It might help something to make the Poser.rsr read only, although I'm not really sure how that is supposed to help. Hopefully someone else can elaborate....

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.

On second thought, I can't remember whether ProPack used Geometries .rsr files or not. If not, my apologies for the error.

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.

O.o ok it is apparently all my old pz3s..I mean GIGS worth of them they just open and seem empty??? it happened after that really odd message about the memory thing poped up {I am really begining to hate the upgrade to win2k} I reopened one pz3 and in the hierarchy editor..it showed the body parts but as part of the universe not a figure. that made no sence to me at all. and there was..a scene prop...dress...figure..hair and one prop..in the whole pz3 how do I check to see it they are all in there? and yes p4 does have rsr >.< ohh the puter turning into a planter is looking better and better!

https://www.darkelegance.co.uk/

Commission Closed till 2025

Um ok silly question... Have you rebooted? Mind you, something similar happened to me after Poser got stuck on lights, but it was only the pz3 I had open at the time. Are all your pz3's in the same place? If yes, try moving them. Empty your windows temp folder (always a good idea anyway, lots of rubbish accumulates there) Empty recycle bin. Rename some pz3's that you haven't opened yet to something else and try. (Before that I would pull a lot onto CD first, in case it wipes them clean) I'm just blindly stabbing at stuff here, I don't really know what's causing it. :( But I figured every little helps.

Silke

if it's happening to all the pz3's it the system rsr thats broken- poser uses 2 types of rsr- the libary one that can be deleted and the system one that is part of the program itself. Do this- it's real simple- copy you runtime out to a safe place delete and reinstall poser then just copy you old runtime back in :) poser tends to accumilate errors during crashes and just plain over time. this is the simpelest and most direct fix for most problems- also makes poser run a touch faster to do this sometimes :) it's a good idea to reinstall this way every now and then just for maintaince :)

ok ran window washer {to clean out caches and temps} booted like five times now....and still no luck on at least three pz3s still trying to go through somemore {gggggigggggggg worthhhhhhhhhh} will try that reinstall...why does poser get pissy like this?? and how can I prevent it from happening again????

https://www.darkelegance.co.uk/

Commission Closed till 2025

If it is the Poser.rsr, as I think Geogress is suggesting, you can supposedly offset this sort of problem by making the Poser.rsr write-protected. Do the PZ3's that continue to be a problem have anything in common? If they all use the same files and the PZ3's that are okay use different props and characters, that might indicate that the Geometries .rsr's are corrupt. Dang, I hate a re-installation. Sorry to hear about that. :(

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.

It might be a good idea to make a backup copy of the poser rsr if you just copy and paste it to the same place then the next time there is a problem delete the rsr and rename the copy to poser.rsr