As my answer, here is the beta-test-report i sent to CL; not that i'am an official beta-tester, but i feel like being one, whenever i get a .0 version of Poser :-( ********* I'm a Poser-user since Poser 1, so you can see that i'm as well a fan of this software as i am a rather experienced user of it. I was very disappointed from the first release of P5 like almost each other of us paying beta-testers, but i was naive enough to hope, that you have learnt your P5-lesson and that you wouldn't repeat the mistakes with it in P6. Well, i was a fool - it is almost the same piece of quite useless software as the .0 version of P5. Oh yes, i like the new things, really love that you finally have pointlights, i like the IBL-lights, the wacros, the improvements of the Dyn-hair, Open-GL support and other new things. BUT...again you haven't changed this historical Mac-based core-code at all. All the annoying P5-bugs are still there, as well as some new, really deadly bugs. Your memory-management is still nothing but a crap, and i wonder if your beta-testers did not find it, or if you are not able to correct it. Bad enough, that in times when pcs have 2Gigs ram and swapspace of several Gigs, a software reports me 'you are low in memory' when working with a file of about 100meg. But that this software suggests me then to save the file, and if i follow this friendly hint, it just writes an empty file, destroying all the work done before, this is not a good joke at all. How can such a bug be in a final version? And please don't tell me anything about 'it is your configuration, it happens only on your pc'! First, me pc is a very well-configured high-end machine with uptodate-drivers, 2 Gig Ram, 50 Gig swapspace running with XPpro. I can work with P5 meanwhile quite well with this machine, and all the bugs i mention here, happened with poser-scenes, that were working fine in P5. Second, one look into the numerous forums shows me, that i'm not alone at all. The only ones who didn't run in this bug are obviously your beta-testers and developers; maybe they 'tested' everything with a scene with one P4-figure, 3 lights and nothing else? Hmm, maybe in such a scene you will never run into a memory bug. But hey - users sometimes do a little bit more with poser! I have heard, that there are people who are using this Vicky 3, sometimes even with clothes, with hairs and with more figures and some background. Oh, and they also are using big textures, not only 512512 images! Is it possible, that you never had heard of this? Or that you say, people who are trying to use figures from our competitor Daz like V3 shall suffer as worse as possible? Let me give you a short list of things you should correct with your sp1 - at least i'm a beta -tester who pays good money for this honour to make your software run. 1. the memory bug - no need to say much, you're certainly drowning meanwhile in bug-reports to this topic. 2. the animation pallette: it is incredible slow. Try to select the keyframes from frame #1 and copy it to frame #120- you have to wait some minutes until Poser has completed this easy task! And this with a not very complicated scene - one V3, 3 clothed p4 male, some background stuff and ten lights. All characters collapsed on the left, so that there are about 12050 rectangular cells to draw into the table. And the same work done with the same scene in P5 doesn't need more time than i need to light my cigarette! In P6 it needs longer than smoking the cigarette to end! 3. an old bug still untouched since P5.0, not dangerous, but annoying enough to mention it: Whenever you leave the material-window, the library is resetted to the Pose-section. It would only cost your programmers two lines: oldLibrary=currentLibrary ....doMaterialRoomStuff... currentLibrary=oldLibrary Easy to do,right? But it spares your paying customers thousands of unnecessary mouse-clicks. 4. Also a very annoying bug imported from P5: WHenever you load a file, Poser adds keyframes for each spotlight in the last touched frame of your animation. And to make this really funny: all spotlights are resetted in this new keyframe to AngleEnd=70, DistantEnd=0.0. In P5 it was annoying: always after loading i have to remember this bug, go to the animation-window and remove those unwanted keyframes of the lights before i try to render again. In P6 in combination with the slow animation-window this bug is a true torture, because it needs some minutes until Poser has deleted those wrong keyframes! 5. An old bug, that is part of your software since P4: take any human figure like P4 female for example. Add any other character and parent it to a forearm of this figure. Then enable IK! Maybe you know what is happening then, if not - try it, and then remove this bug finally! 6. Collision Detection: well, it looks nice, if you have this in your feature-list. And it works quite well, if you collide a primitive cube with a primitive sphere. But again: Poser users usually are more interested in collision detection between two human characters! So if the system locks for one minute if you have ColDet enabled for a V3 head and only try to bend this head, the collision detection is absolutely useless for the users of your software! And one last hint, once you have corrected the most deadly bugs: the wacros in the material room are a very good idea. Why not giving us some wacros for the clothes room? It would be great to have some prefix settings for silk, wool, cotten, leather, steel, maybe even wet cloth or similar more sophisticated stuff. Same for the hair room: some meaningful prefix-settings would make it much easier for your customers to become handy with the controls. You have a really wonderful base for a great software, so use it finally and don't spoil it with releases of bug-diseased beta-versions that enrage even your most honest fans!