I think I finally had some success in making hair blow in the wind. This is Don with the "Neftis HardRock" hair. As you can see from the picture, I did not turn on the collision detection, because my system seemed to choke on that one, so I just tried it without it. First I loaded the hair, then parented the skullcap to the head, set up the wind object, then did the calculation in the Hair Room with "Calculate Dynamics". Not bad, huh?

Maybe it's not so noticeable from this angle, but the lack of collision detection made his bangs go through his forehead a little. Nothing that couldn't be fixed with a little postwork ;)

No it is I have been doing this all day long. I must confess I did have some blowing up a womans dress! Should I show it? Ron

Go for it ... a little Marilyn Monroe never hurt anybody. Wellll, except for the Kennedy boys I suppose. ;-)

LOL! Yes, let's see it! :-D

timoteo1....LOL, your funny...Sharen

What kind of system do you have Sue88, if you don't mind my asking? If your system meets the P5 requirements, it shouldn't be choking on collision detection, maybe take forever, but not choke. You might want to send info into CL for them to look at.

mabfairyqeen, I have a Dell, Pentium III, 866 mHz, 512 MB SDRAM, Windows ME. When I had collision detection on, first it seemed to take a very long time to do the dynamics, but then it just completely got hung up. I can do collision detection on cloth in the cloth room, but it seems that all those strands of hair were a little too much. With the hair and cloth stuff, sometimes things work for me, sometimes they don't. I'm not sure yet if it's me or the computer or P5. I'll have to experiment more.

Sue: To speed things up and drop the load a bit, you can close the library palette and run things in either wireframe or cell-shaded mode. Poser's library tracking leaves a bit to be desired and eats up a ton of resources. Also, the tracking mode chew up even more because it has to struggle with updating the scene while performing calculations. ;) Hope this helps. Paul

Thanks, Paul. I did have the library palette closed, but I think I was in smooth shaded display mode. I'll try it with wireframe next time. Is it also supposed to help with the rendering time? I had the display in wireframe when I rendered the picture, and I didn't notice any noticeable difference timewise. Sue

Well these are the system requirements on the product page: Windows 98, 2000, ME or XP 500MHz Pentium class or compatible (700Mhz or greater recommended) 128MB system RAM (256MB recommended) 24-bit color display, 1024 x 768 resolution 500MB free hard disk space Internet connection required for Content Paradise Your Pro Pack Serial Number So it's not your system as far as I can tell. It shouldn't be locking up, but what Entropic suggested might be the solution. Don't know for sure. Does it say anything about that in the manuel? If not, you might want to drop a note to CL, just so they're aware.

"I'll try it with wireframe next time. Is it also supposed to help with the rendering time? I had the display in wireframe when I rendered the picture, and I didn't notice any noticeable difference timewise. " Well, I don't think it will noticeably speed renders, although I imagine not. A lot of people are still kicking ass figuring out ways to optimize performance. One thing people are talking about is customizing the interface so it doesn't rely on PSD's. Theoretically the interface is skinnable, but I'm not good enough with XML to try it. As far as I can tell cell-shaded mode will present the smallest load on the system, and actually dropped my dynamics calculations in my tutorial from 58 minutes to 32 minutes on a Celeron 600, 384 Mb, Win ME system. Paul