What SR3 DID fix for me was pretty much all of the remaining issues with the dynamic hair that I had (I don't animate dynamic hair so I can't speak to those issues). What SR3 did NOT fix was the problem with the program's priorization of tasks. It puts rendering and draping at the top of the food chaing and dumps user inputs and OS inputs to the bottom, making it SEEM as if the program locks up, especially on slower machines. This also makes it impossible to tell if it HAS locked up or not because there is no way to know if it's just ignoring messages from the OS and mouse or is locked in a tight loop where it will never see them. Generally, it DOES respond to the high priority EXIT NOW message from the OS, so it's probably still running. But there's no way to see progress because the display of progress is not updated until the high priority draping/rendering task lets a few cycles loose. When I braced them on this, CL claimed that Poser is "not written for multitasking." They're right about that!!! The trouble is, our OPERATING systems ARE and if you ignore that in a program it looks really clunky, as P5 does. Like many others here, I'm waiting for two things. An SR4 that deals with the real issues and streamlines the code as much as possible and DAZ Studio which will provide a basis for comparison of functions.