Lately, I have been having problems when I try to load certain Figures from my Libraries. The program will tell me that it is unable to open either the .obj or the .rsr file. Then, a warning will flash telling me that I am out of memory and must change the amount of memory allocated to Poser, and one of my Figures onscreen will disappear. The Geometries files are all spelled correctly with the proper case and placed in the proper folder, but Poser will tell me that it unable to read or open these files. Although this sometimes happens with new Figures that I have just tried to install, the really weird thing is that it has also started to happen when I try to load up stuff that I have used without any problems in the past. It will always happen with the same particular Figures, but it seems like more and more of the library is slowly deteriorating, with another Figure getting messed up every month or two. So, my first question is a dumb one. How DO I allocate more memory to Poser? My second question is, will that solve my problem? The third question is, if that isn't the problem, then what is going on? If anyone has any ideas or suggestions, please let me know. Thanks. -the Inmate

you can only allocate more memory to poser if you are on a mac... otherwise.... on a pc.... poser is using all of your available ram.... however the likely culprit here is corrupt rsr's.... which poser will create....the rsr's in the geometries folder... it may even be poser's main rsr....they usually need to be deleted when corrupt.. the main one replaced...and poser recreates the rest of the geometry ones on the first time it is opened again... that is sometimes the problem here

Also, when was the last time you shut down your computer? Poser has done this to me a few times when my resources get down abit. Also, how much room do you have open on your hard drive?

Good answers, but if it always happens with the same characters it is probably the .RSR problem that X-perimentalman described. As he said, delete the offending .RSR in the appropriate Geometries folder and let Poser rebuild it from the .OBJ file in the same folder. After you get the problem figure to open again, be sure to let Poser close that scene and exit properly because it only writes the new .RSR to disk as it closes the file. If you crash out, the new .RSR will be corrupt once again the next time you try to use that figure.

When you get everything back up and proper, close Poser and using your file manager, change the attributes of your main Poser rsr and character rsr(s) to be "read only" , then Poser can not corrupt them.

Thank you crazed-inmate for asking the question and the rest of you for your helpful answers. I've been having the exact same problem for a while now and just thought something was screwy with my computer and not something you guys could help with. I should have learned by now that you guys have all the answers. Thanks again. I can't wait to try this when I get home to fix my problems.

This is an old issue. Poser rsr files are a bit of Mac programing that was ported over to the PC. Everytime you open a character Poser rewrites the geometry rsr file. (unless you make it "read only") Sometimes Poser doesn't rewrite it correctly. For instance, I had a 200k rsr file that became a 4 meg rsr file after being rewritten. That's when you get the error messages. All you have to do is go to the folder indicated by the error, then delete the offending rsr. The next time you load the character, Poser will write a new rsr and everything should load correctly. Remeber, Poser only rewrites rsr's that are not "read only" so making your rsr files "read only" will alow you to avoid the problem. -SMT

Minor point of order - Smallspace mentioned "Everytime you open a character Poser rewrites the geometry rsr file" I don't believe it writes a new .RSR everytime you use the character, but it does get rewritten occasionally -- though I haven't a clue what triggers the rewrite.

You guys were right. Last night I deleted the rsr's of a few of my problem obj files and they worked!!! Thank you very much.