Forum Moderators: Staff
Poser Technical F.A.Q (Last Updated: 2024 Dec 04 2:47 am)
Welcome to the Poser Technical Forum.
Where computer nerds can Pull out their slide rules and not get laughed at. Pocket protectors are not required. ;-)
This is the place you come to ask questions and share new ideas about using the internal file structure of Poser to push the program past it's normal limits.
New users are encouraged to read the FAQ sections here and on the Poser forum before asking questions.
Firefly probably doesn't, but, as its a component of a 32 bit application, it is limited, like all 32 bit applications to 2GB. This is because, a 32 bit word used to store a memory address can only really represent 2 to the power of 32 distinct numbers (adresses). This is actually 4GB, but the operating system also need to reserve some of the application's memory space for their own interfaces, and most operating systems (Windows, Mac, Linux) just split the 4GB range down the middle, allowing 2GB for the program to play with. Many of the crash type problems I've seen seem to occur when people top the 1.7 GB mark in Poser. It's possible that temporary allocations are nudging the memory use over the 2GB mark, without it ever being registered by the Windows task manager. Bill
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.
Just curious. I have some scenes that render with Fire fly just fine and some that crash. The crash scenes usually have like 5 vickiy characters in them. Just curious if FF has some upper memory limit.