I will wait for 64-bit rendering from some future version of Poser that has the presently proffered enhancements of Poser 8 (and maybe more). I already have Poser Pro (1) and going back to 32-bit rendering is not about to happen. If I bought Poser 8 and used all of its enhancements, I would not be able to load a scene from it into Poser Pro to render it. This leaves SM's top of the line product behind their development curve, which is a very curious way of doing business.

Most desktop computers being sold now can run a 64-bit operating system. It will take a while before most people own such a machine. Businesses will buy 64-bit very much more quickly, especially those that do graphics work. Through Poser Pro (1), Poser is one of the few graphics programs I own, or am likely to buy, that does not benefit much (if at all) from increased memory and faster processors/more processor cores. The only exception is the 64-bit rendering.

Because the code for 64-bit rendering is already written (including the ability to render on legacy 32-bit operating systems), putting out a new version of Poser that cannot render in 64-bit is backwards moving, not moving forward. If a lot of content is developed that takes advantage of the rigging, the lighting/illumination enhancements, or wxPython, then all the people/companies that bought Poser Pro (1) will be unable to use the new content. Content developers are always concerned about backwards compatibility. Now, SM has introduced forward compatability problems. Ouch! This deficit will discourage the development of content taking advantage of Poser 8’s enhancements.

For people who have 32-bit operating systems and do not have Poser, or who have an older version of Poser, this version is a step forward. I hope crowds of people buy it, and that Smith Micro makes lots of money so that the Poser applications survive. Then eventually they may drag all their lines of Poser into the 21st century.

lmk

Probably edited for spelling, grammer, punctuation, or typos.