Mon, Nov 25, 11:50 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 24 8:11 pm)



Subject: Memory error (PC), Help! (new user)


divague ( ) posted Sat, 03 November 2001 at 6:20 PM ยท edited Mon, 25 November 2024 at 11:39 AM

Hi people. Im new at Poser 4, and i can't use the product once. After install, i run poser and show a message "You are out of memory"... blabla. I saw some post, but in all cases some .obj is damaged. It's not my case... Any caritative soul over there??? Thanks, divague.


divague ( ) posted Sat, 03 November 2001 at 6:24 PM

Sorry. Im a PC user (Pentium III 550mhz, 256mb memory, 20gb free space on hard). Please...!!! Gracias - Thanks. divague.


ronknights ( ) posted Sat, 03 November 2001 at 7:15 PM

One thing I can think of is this is a Poser problem. I swear that Poser has a few bugs in it. The error message comes up quite a lot if you work on an image, prop, character, whatever, where the author/artists made a mistake. You load the item, and something can't be found. I think the missing geometry file is most often the culprit. Of course, I'm making a snap diagnosis without knowing more about what you're working on. And have you downloaded the Poser patch so you're up to 4.03?!


Blackhearted ( ) posted Sat, 03 November 2001 at 8:31 PM

what operating system are you running? youll notice all these memory errors will dissappear if you install win2k or winxp. but its not necessarily a memory problem - the 'out of memory' error is poser's standard 'something is f@$#ed' error. either way, try reinstalling it (it only takes a few min, god knows ive done it dozens of times) and updating to the 4.03 update you can grab from www.curiouslabs.com good luck grasshopper cheers, gabriel



ronknights ( ) posted Sat, 03 November 2001 at 8:47 PM

Well, with Windows 2000 Pro, you get messages stating there is insufficient disk space to render at this resolution. That happens even if you have 20-30GB free space on your hard drive. You can always come back later and render the same exact file as well. Weird. I have no such problems with Windows XP Home Edition. Or XP Pro for that matter.


brycetech ( ) posted Sat, 03 November 2001 at 9:57 PM

uninstall poser and re-install it if you still cant run it at all...and assuming its a legal copy, you can contact curiouslabs and they will help you fix it up. www.curiouslabs.com could be a corrupt file in the installation...or you may have to do something as simple as delete the preferences file and let poser recreate it. luck BT


leather-guy ( ) posted Sun, 04 November 2001 at 3:38 AM

Another suggestion; Try running scandisk. I recently had a problem with Poser lockup on loading. Even CL couldn't figure it. In desperation, I ran Scandisk, & it found a bad FAT entry in the textures folder. Poser was trying to load 154 million texture entries & crapping out. Took Scandisk 3-4 passes to fix completely, but all okay after. Good luck!


MaxxArcher ( ) posted Sun, 04 November 2001 at 4:26 AM

Windows is probably unable to extend its virtual memory which gets swapped to disk. If you split your HD make sure theres enough space on the disk where the swapfile resides. My own system is big enough, but sometimes I forget that my system disk is a bit small resulting in the same problem you have....


MGCJerry ( ) posted Sun, 04 November 2001 at 9:04 AM

Do you get "runtime/blah/blah/blah.obj not found" then an error that states "YOU ARE OUT OF MEMORY"? then it removes your previous used figure from the workspace. If so its probably a screwed up obj file, and poser isn't intelligent enough to figure that out... Hopefully CL wil fix it in Poser5. It happens to all of us most likely.


divague ( ) posted Sun, 04 November 2001 at 8:04 PM

Hi ladies and guys! Thanks for your answers. Finally (sorry, my english is worst every day), the problem was solved. Im running windows 2000, but this is not the problem, i think: my hard disk was... i just did this actions: - run uninstall - checkdisk (with fix option included) - reinstall - update to 4.0.3 again. Its running right now!!! Thank you all..!!!! divague.-


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.