There are a lot more problems in P6 than just the memory bug. The dial response problem referenced above, some remaining focus issues, the memory structure design error found by a partner at release time, features in the manual not enabled in the code, etc., etc. So if they are taking the time to try to address everything in one go, more power to them. Historically P4 took a couple of SR's, PP 3, P5 4 of (really 9 as there were 5 attempts at SR2 ;-) so it would be good if CL demonstrated that they could substantially fix a release in one pass. But the effort at the Content Update suggests otherwise of course. (By the time my P6-in-a-box arrived the CU was available, so I hate to imagine how bad it looked before the CU, 'cos it's still pretty bad.) And P6 still has all the bugs and slowness of P5, plus all the bugs and slow downs of PP and the bugs of P4 and ... As to 1 month being too long for the memory bug fix, that might be true if and only if the bug was a P6 development bug. There's a real possibility IMHO that it's no more than finally "hitting the wall" with the memory management bug that has affected all Poser versions with increasing seriousness. (Adding more resident code to an app which is already saddled with an out-dated memory structure.) Fixing that would be very tricky, especially - as indicated above - because CL has clearly little practice in fixing bugs in prior release :-O And did anyone else note a reference in that post about the memory structure design error by a development partner to CL, which said that CL should be able to fix easily because it is in "live code"? Which implies parts of Poser are "dead" code? Each development shop has its own coloquisms, but that sounds awfully like they do not have access to every piece of source code...