TalonGE opened this issue on Jun 12, 2003 ยท 61 posts
layingback posted Fri, 13 June 2003 at 1:06 AM
Just for the record, I did try the nothing but OS and Poser 5 - twice. System is very clean, patches, drivers, etc. Run Video Editing hardware/software which is VERY intolerant of OS and/or harware setup errors. OS is W2K with EVERY possible performance robbing billware "effect" turned off. Net result for my efforts - nothing, neit, nil, nada. Exactly the same problmes with every software app there and with only P5 there. Dials slow/non-linear/changing after released. Memory leaks - what a surprise non-existance of other programs in system do not impact memory leaks :-O Focus jumping everywhere and/or getting lost. Lockout of OS for long, long periods of time. Limited capacity for models due to memory resource problems. Etc, etc, etc. I have tens of years of software application testing up to and including operating systems, BTW. But as I've reported before here (and in the callously deleted P5.2 "Beta" Forum) I HAVE reproduced every problem exhibited in Poser 5 in Poser 4.03!!! Yes, every single d*^# bug in features that are common between P4 and P5! It's tedious, exacting but not very dificult. Push Poser 4 to the limit of it's memory resources, and you can get it to (mis-)behave JUST like Poser 5 does... 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. The latter seem to strong a statement? Then why else did they come out with the blantant lie that Poser 5 was a re-code? It's not as if the lie would not become exposed pretty quickly. But without it being said, would enough people have bought it to satisfy whatever irrational goal was being set internally for sales numbers? The only fix for P5 would be a rewrite of the underlying memory manager, user interface handler, OS interaction API's for a current, modern, NT-based one. Chances of that happening, slim to none unless CL have been forced to do similar for Mac OSX compliance. But with 6 staff, at least 1 of which is the head honcho, 1 is Sales/Marketing, that sure doesn't leave many for coding and testing even if they have no accounting, administration or legal staff... And finally, it has to be said: CL's attitude towards Quality seems to be well, poor. Even Poser 4.03 (note this was at least the 4th release of 4.x) should never have been left as it was for even a few months let alone 4 years. And history (written by senior staff at CL in many cases!) seems to show that every release has been much the same, buggy, fixes which added bugs as well as fixing some, and finally leaving it as "good enough" even with very visible apparently trivial to fix bugs. The ONLY rationale I can assign to this is that either it's deemed "good enough", or CL never ever understood that bug-free code can be developed, and most certainly can (and should) be strived for. Let's not forget that Poser 5 was shipped in the full knowledge that there were problems. (Source of that was the then CEO himself.) Long time member of EVM, and user of Poser 4.03 :-( P.S. EricofSD, to overcome the 1600x1200 screen setup snaafu CL added to SR3 (again) reset to factory default (both options on that page). Exit Poser and then reload, reset UI the way you had it, and changing settings back from launch to factory defaults. Exit and reload again, and you should be OK. Worked for me, anyhoo.