"The major thing missing in P5's renderer is global illumination, but chances are you won't use that in animation anyway for performance reasons." Stewer, there's really a multitude of legitimate reasons why Poser just isn't a good solution for animation, and it's not all based on the renderer. I'd say the major thing with P5's native renderer is it's slowwww raytracing (things like raytraced water and mirrors for high quality animation output is near impossible to tolerate without network rendering capability). I've also experienced some issues with pixel roping and flickering that occurs now and then on certain objects if you don't set high enough render parameters, which also in turn puts a big hit on rendertime. There's also no G-Buffer channel output options (such as depth or Zbuffer output), so things like DOF and atmospherics must be done within the renderer, which would be OK if it had network rendering, but without it, quality DOF makes a render crawl. On some projects that are heavy on raytrace materials, I would like to, at least, do DOF and atmospherics in Combustion or AfterEffects using a depth channel. ;-) Also (this isn't the fault of the renderer) Poser does not recognize multiple processors, so my dual Xeon workstation is virtually useless in helping with render output. I realize there's workarounds to the network rendering issues, like putting multiple instances of the application on different boxes and copying the PZ3 to each one, but that's not a very practical solution either. Outputting to RIB is good, but we're talking about Poser's native rendering capability.

---

Tools :  3dsmax 2015, Daz Studio 4.6, PoserPro 2012, Blender v2.74

System: Pentium QuadCore i7, under Win 8, GeForce GTX 780 / 2GB GPU.