The example produces good comparison between display and render mostly because of the simplicity of the scene. It's a little like saying that I can cook 90% as well as the best chef in London because I can do a poached egg nearly as well as he can (or possibly 2 poached eggs, in which case I'd probably set the "Nudity" flag). True - there's little to tell between our poched eggs, but I'd hate to compare any non-trivial meal on a like-for-like basis because actually my cooking sucks. So it is with Poser 5 "real-time display" and "Firefly Render". I haven't produced an example here because IMHO the galliers can do such a better job (indeed even I have an image - "Like Rock" - which is FAR superior when rendered than in preview mode - lost the .PZ3 though, to my dissapointment). However the real-time display renderer can be somewhat slow when you build up the content of the scene, and only copes in effect with a subsection of the Poser 4 renderer abilities. Yup - the display renderer is so "fast" and fairly decent quality because it ignores much of what you CAN do in Poser nowadays - from Poser-4 type transparencies and bump-mapping to displacement, reflectivity, and a slew of clever material nodes (well, they can produce amazing results when cleverly manipulated). CL have perhaps done well to have written real-time display code that isn't too shabby when displaying a basic "texture on a mesh", but as you start delving into what Poser (especially V5) can REALLY do the speed and quality of display mode both suffer by comparison. Speed is especially important to any of us who do animations, especially animation which must synch with audio (speech, music). These are the 2 angles - speed and quality of beyond-basic scenes - which have had people crying out for 3D accelerator support wihin Poser for quite literally years :( Cheers, Cliff