poser5, latest patch, on 3,2 ghz with 2 gb ram and lots of free harddisk space. so why does it craps out?! as soon as i click on raytraced shadows it stops at "adding objects". i can click on cancel, then the box pops up with "canceling" and it takes forever to do it. i can't even stop the application with the task manager. only when i stop the process, p5 stops working. next bug: since sr4, i don't see textures on the model when i load it for the first time - everything is white. textures are there, as soon as i touch them with the pippette in the material room they show (but only for the body part touched). next bug: since sr4, this stupid application can't remember it's starting position for palettes. i know how to use ui dots, but if they have programmed it decently, there wouldn't even be a need for them! next bug: when i turn the dials, poser looses focus on mouse for hotkeys. i have to click somewhere in the screen to have them working again! and so on, and so on... i know that even programmers need to eat but please, curious labs (or who ever runs you), kick out those bosos that even microsoft wouldn't employ and get someone who knows how to do the job. poser5 must be the worst commercial application ever written! do i sound angry? YOU BET!

Wow You got it bad man. I was having freeze ups like you describe that got progressively worse until I couldn't use Poser 5 (On a similar speced machine too). I think my instability may have stemmed from copying my Poser 4 Runtime into P5 when I got my new comp. (On the old one I have the P4 runtime linked). Basically I did a clean re-install and this time installed Poser 4 on the new comp, copied Over the runtime to it and linked it. I've had basically no problems since. If I were you I'd do a clean install. :(

I had a weird "freezes at adding objects" problem which I managed to get round. Whenever I had a scene that was rendering fine for the first render I did but always locked up on the second render, even when I reverted to earlier scenes that had previously worked. I took out elements from the scene till this stopped happening. Then I readded the last element, in this case it was M3, piece by piece till it happened again. Using elimination I discovered the culprit was part of the Poser 5 hair (layer 1). By recreating this bit I fixed the problem. Hope this helps.

i'll try that. thanks, guys! :)