Aeneas opened this issue on Apr 06, 2003 ยท 6 posts
Aeneas posted Sun, 06 April 2003 at 1:54 PM
One of the following weeks my Poser5 will arrive. Afaik, the app does not support dual processors nor hyperthreading, dual planes or OpenGL. Doh! Yet the worst is yet to come...I have a new workstation for the big apps, with 2GB of DDRam on a dual ram mainboard (2x 2x512). Now I read on a forum that Poser can't handle 2Gig of ram and gives the message that "there is not enough ram"? If this is true, then I am really stuck... Anybody knows about this? Thanks.
I have tried prudent planning long enough. From now I'll be mad. (Rumi)
fretshredder posted Sun, 06 April 2003 at 2:14 PM
not true (partially). I am running a dual P4 2.4 GHz 2GB DDR RAM and poser uses almost all of it when needed. As far as poser not supporting SMP (dual processors) that is true. but if you run an OS that does CPU tasks will be interleaved between the two as necessary. HTH
layingback posted Sun, 06 April 2003 at 3:08 PM
IIRC all individual Windows applications are limited to 2GB, although you'll need an NT-based Windows (2000, XP) to even reach that limit. If you exceed, or more likely come close to, that limit then Poser will become unstable. OTH, the "Not RAM" message comes up whenever Poser can't find a texture, asks if it should continue searching, and you anwser "No". At that point it'll throw a wobbly and tell you there isn't enough RAM on your system. This clearly has nothing to do with RAM, and is a bogus message. One could reasonably call this a bug in any other application, but as Poser has exhibit this behaviour for years spanning at least 3 releases, one is reluctantly force to conclude that the developers designed it that way, and consider it a feature! ;-) Of course, no current applciation should EVER need 2GB of memory, real or virtual at one time, that's something an OS can handle, but Poser doesn't want to let it... The only contribution that Poser5 makes to this mess is that it uses more memory than earlier versions, so you start off from a higher start point even before you load anything into the scene.
Aeneas posted Sun, 06 April 2003 at 3:40 PM
Thanks.
I have tried prudent planning long enough. From now I'll be mad. (Rumi)
bloodsong posted Sun, 06 April 2003 at 4:26 PM
heyas; poser 4 can't handle a system with 2+G of ram, but there's a patch for that. p5 should be fine.
hogwarden posted Sun, 06 April 2003 at 8:18 PM
A customer of mine has "cannot render at this resolution" errors after converting from FAT32 to NTFS (P5). I'm sure this could be linked... were there some threads about this in the ol' Poser 5 forum? H:)