with animation, concern over render time is never a fuss. I don't engage motion blur in Poser, although it is an option. It is better to run the render straight and use the motion blur effect in After Effects. Poser can calculate DOF as well, but same thing: generate a depth map in poser and engage in After Effects, that's much better. In a similar vein, muti-pass rendering functions fine in Poser, as it has a shadow catcher function and any combination of items can be made visible/invisible. There are some who have even worked out ways to use multi-pass strictly on a distance-from-camera layer basis. I have never needed to go that far. The principle advantage is that you if during composite you find one of the layers has a problem, you only need to re-render that layer. Might be going to multi-pass for that reason at some point. The hair WILL render in full motion all by itself; I guess you could render just the hair. I have no idea if this would work okay; I doubt if it would save any raw render time. What is key is: you can make the hair invisible to raytrace. That way, if you need raytrace on for reflection, or anything else, you don't suffer a hit on the hair. An important policy has to do with the simulation. If collision is not on, simulation (calculation of the hair motion prior to render) goes very fast. With collision on, it can bog down, but there is a fine proxy trick: you can calculate over a sphere or a low-res cage of the head, thus reducing sim time significantly. As to your experience of "wouldn't touch it" a few years ago, I think that the contrast with it now being used 'informally' speaks a lot about how far the app has come. I saw a commercial yesterday on the olympics that was definitely at least begun in Poser, some of the models were definitely from there. Might have been rendered elsewhere. ::::: Opera :::::