Attached Link: http://www.renderosity.com/messages.ez?ForumID=12440

Much of Loser5's problems are due to memory. They are actually inherited problems from Poser4, I've reproduced all the Loser5 problems in features shared with Poser4, in Poser4 - they are harder to make occur, you really have to load up the scene, but they are there. But the new features in Loser5 are huge and they are also *always* memory resident along with all the Poser4 stuff, and so further starve the earlier Poser4 ones of memory resulting in yet greater instability. This has been a continuing hypothesis since 5.2's release, but check out the Poser 5.2 Forum (yes it still exists) for williamsheil's very enlightening explanation of Poser's Memory Management - or lack thereof in his response to "P5 Memory,... Oh I forgot." 3/27 - 29. It's worth reading if only for Bill's priceless term 'bedroom programming' ;-) Fingers crossed for SR3 fixing underlying problems not just the newly-created-in-Loser5 problems... (Violence warning flag turned on for benefit of those who would hear nothing ill said of CL or Poser5 :-)