duanemoody: "Add to this the fact that when pressed for details, CL grudgingly admits a large portion of Poser 5's code hasn't been ported from Carbon to Mach yet; for the rest of you out there this means it's still essentially running as OS 9 code, through a compatibility layer instead of written for the native OS. An app written for Win98 running in XP doesn't have this kind of hurdle to go through. Every other app I run on the Mac that's written for OS X from the ground up is blazingly fast, 3D apps included. Presumably Poser 6 will be truly OS X native code and this test will be more relevant between platforms." He, He! EXACTLY the same thing could be said for Poser (4 & 5) on Windows. Much of the code is still "running as OS 9 code, through a compatibility interface instead of native Windows OS. An app written for current Windows OS's running in XP doesn't have this kind of hurdle to go through. Every other app I run on Windows that's written for current Windows from the ground up is blazingly fast, 3D apps included.". Look at the file dialogs for a clear example of the hamstringing occuring. Or try an HT CPU. Your last sentence similarly substituted would read: "Presumably Poser 6 will be truly current Windows native code." I wish, but doubt there's much chance. History indicates it'll still be Windows calls done by a very old (Win 3.1?) (largely-) Widnows compatible interface library. So don't feel too hard done by. It's not a MacOS vs OSX per se, it's just that CL doesn't do rewrites of their code if they can possibly avoid it. ;-)