Quote - _Don't see why most Poser legacy content wouldn't work in current versions of Poser. If it worked in Poser 7, should work in Poser 9. There are exceptions and differences of course depending on what kind of content you're talking about, scripts in particular. Things like props and figures... Totally compatible. Many times you'll just find that more recent developments have made older content obsolete, sub-par or in need of an overhaul.

Missed this.

Example is the problem with back facing polygons rendering with strange surface anomolies or other content. Hair for instance that rendered in P4 with its simple engine has to have back facing polygons turned off or made invisible to the P7 Firefly render engine to minimize or eliminate the noise it gets. Sometimes even those measures don't work. Surface spots and strange hash marks on buildings and props are a pain. It gets wore when you need to go back to a .pz3 created in P4 to upgrade the render quality in FireFly and have these strange anomolies in the render in P7. The migration to a better render engine and all the lighting stuff that goes with it is worth it if.....IF...these anomolise can be dealt with. My concern is will I be geting the same problem in newer versions of Poser? I know, you have no way of knowing but that is my concern. I guess I just need to jump in.

What about the rendering strenght of these newer versions? Will I have any problems using them on my Macbook Pro? Are they 32 or 64 bit adddress and is there any reason why I should bother being concerned?

Poser 4 sucked with solid RM use. It was a pig . Poser 7 hasn't been much sweeter. Poser 7 now crashes on me if i try to test render at half resolution (1500 x 1500 @300dpi) more than once without closing Poser and relaunching (I use complex scenes, fully propped and lit at 3000 x 3000 at 300 dpi). It's a real pain in the heinie! Apparently P7 doesn't address all the RAM I have in system (8Gigs). Will that RAM be addressed more effectively using newer versions of Poser (9 or 10)?