One thing that distinguishes Poser (and similar apps) from most other 3D apps is the extent of mesh deformation. For Bryce and its ilk most meshes are static (most of the time) so once the geometries have been loaded into the OpenGL (or DirectX) buffers they don't need to be changed and positioning or scaling can be done in single operation. In the case of Poser/DAZ, the (very large) geometries themselves are often altered during normal posing/morphing operations, and this may require some significant reloading of the hardware acceleration buffers. That additional overhead (which again falls on the CPU) has to be weighed against the speed gains for the accelerated pixel pushing power of the hardware. For me, this has always raised the question of whether Poser users would, in fact, see as significant speed gain in many circumstances as they expect. DAZ certainly seem to have confidence in this implementation, so having never tested the numbers myself, I'll be happy if they prove me wrong. Bill