What we need most as a community of POSER users is quality documentation!

  What POSER needs DESPERATELY is CREDIBLE DOCUMENTATION!
The superfluous computer generated circular references that lead to meaningless
entries is unacceptable. As far as I can tell, most of POSER PROS documentation
is identical to that of POSER 5. That’s 4 full versions of POSER and NO improvement
in documentation AT ALL! As to the first entry here, POSER PYTHON would be of
great help in some of the areas mentioned and I’m sure in many other situations as
well. Unfortunately, the POSER PYTHON documentation seems to come from
POSER 3!

   If the people in charge of  POSER are serious about the future of POSER, then,
they need to assemble a small team of qualified individuals, who have the sole
purpose of systematically addressing POSER documentation and making that doc-
umentation available for free download by POSER users. The single goal
of this small team would be to strive to increase to productivity level of the
POSER community as a whole. This in turn would cause an increase of both
quantity and quality of POSER stills and animations, which in turn would raise
the awareness of POSER on the whole, which in turn would cause an increase
in demand for the product.

   Let me ask you this: If you take a U.S. History class, who knows more about
U.S. History, you, or the teacher? We would hope that the correct answer is the
teacher. It would stand to reason then, that the people that work on POSER know
more about it than we do! Therefore, they are the most qualified to provide the
required information that would allow us to make more efficient and effective use
of POSER!

   I would suggest that they begin with POSER PYTHON, as the documentation
is all but nonexistent. Then, proceed on to the FireFly Render Engine and the
Material Room. Use your imagination. Everything you wanted to know about the
FireFly Rendering Engine and some things you didn’t, but were afraid to ask.
Such As: Where exactly did the FireFly render engine come from? What is it’s
History? How does it handle ray tracing? How exactly does it use/allocate memory?
I’m sure as a community of POSER users, we could fill pages with relevant
questions on the inner and outer workings of FireFly alone. And so on…

What we need most as a community of POSER users is quality documentation!
Quality documentation that comes straight from the horses mouth.
Only then will we be able to proceed.