CL never ever understood that bug-free code can be developed, and most certainly can (and should) be strived for? What are you? Retarded? (thats a question not a statement) Have you picked apart the P5 code? Then how do you know it isn't a recode? They said it was, just becuase there are similarities between p4 and p5 issues the same code it doth not make. waves arms But of course they must BE lying! You cannot compare p4 tp p5, if you do then you are already beyond rational thought. To do so would only undermine what p5 is doing (not trying, IS doing) and all the hard work that cl has done (then, now and in the future) So I put it to you that the problems exhibited by Poser 5 are thus a) latent (i.e. present in prior releases), b) triggered by poor/bad/non-existant memory management, and c) known and ignored by CL when producing Poser 5 DUH!? Why not type go retype some tutorials, they need to be rehashed too. I can't have Layingbacks post be the last word.