How technical can we get here???? cause I'd like to pose some questions that may help others solve the problems with lock-up's,freezing and other wierd stuff Poser can pull out of it's hat. 1.Why is it in the read me file for you to use small mouse movements when dragging something? My lock-up's come when I move off the render screen to fast and go some where else. Even when trying to go from say the leg to the arm with the mouse... 2. Video cards....Now there is can of worms. But I have a middle of the road card. Nothin to fancy,But attached to it is a VooDoo 2...Now your gonna catch yourself saying "No Way"..But wait...I turned mine off and so far so good!!!! 3. Sound cards????? Dunno, But let me say this. I game,,Mainly Flight sims..but if you wanna freeze, lock-up or just plain blow up your system, Have your sound card settings wrong.. That is what got me too thinking about all this...The lock-up's and freezes in Flight-Sim. are just like what I was getting UNTIL I got everything worked out!!! So I pose the question, with so many varied complaints...MAYBE some of this stuff is HARDWARE related???? Or maybe my Poser 4 is taking a nap in preperation for the next round......

I think for the most part many of the problems are hardware related. I keep my system pretty tight and I rarely have a problem with poser at all. When I do its because of a missing texture file or sometimes a bad .cr2 hack of my own doing ;)

I don't have any kind of fancy video card, and I've had few problems with Poser locking up since I added more RAM. Poser has only crashed on me when I have been making extensive use of the Grouping Tool, without giving the program a rest.

Poser is, to say the least, a very complex piece of software. I believe that sometimes, Poser "trips over its' own feet" because of its' complexity. If you are "feeding" it too many commands (i.e., mouse clicks), too fast, the program doesn't have time to "clean its' own house" and tries to do too many things at the same time. No matter what clock speed processor you have, the CPU can only execute ONE instruction at any given instant. If it is "interrupted" in an awkward place in the program, it "hiccoughs" and winds up in "never-never land" and you get the infamous "Caught Exception C: blah, blah, blah...". I've had very few crashes or lockups and I believe some of the conflicts had to do with the sound card and video card. One significant change I had to make was to configure my video card to 16 bit color. Trying to use 24 bit color created many problems (including funny looking text in some parts of RDS5). Try changing some of these parameters (ONE AT A TIME ! ) and see what happens. Good luck. cheers, dr geep

Geep.. That's what I was doing, banging around as fast it would let me..And it was nothing but problems... So I went in and slowed a few things down...even the mouse double-click speed and Pointer trails... Never thought about goin to 24-bit tho....

Pointer trails EATS CPU power. See if you can get along without it. If the CPU is processing mouse movement and then translating it to moving video (pointer trails) and sending that data to the video card, it reduces the time to run the Poser routines. Just a thought.