From: Bjoern Knafla (bknafla++at++nikocity.de)
Date: 03/08/2000 14:12:53
Hej,
I am a newbie performer user and incorporate it in a project where we want
to develop an articulated human figure.
To use skeleton-skinning I am calculating the position of the vertices in
the app-stage and copy the vertex array containing the new positions every
time into the attribs of the skin-GeoSets.
However I have read about pfMorphs (pfEngines aren't supported in our
version of performer) and hope to get answers to the following questions:
- Copying the new data into the attribs of a GeoSet seems to incorporate the
placement of the data into shared memory. Are there performance differences
between this method and the use of a pfMorph (passing a new array to the
pfMorph-node)?
- Depending on the number of bones influencing a vertex I have to call
numerous matrix-vertex-multiplications per vertex in the app-stage. Later on
in the draw-stage every vertex is transformed by the projection- and
matrixview-matrix. Is there a way (and would it be recommended...) to
execute all calculations in the draw-stage? This would allow the
concatenation of the skin-matrices with the projection- and
modelview-matrices which should discard nearly "NumberOfVertices"
matrix-multiplications. However it could put a great delay on the
draw-stage...
- While GeoSets/Geodes are mainly used for static data I am uncertain if my
per-frame attrib updating is the way to go/recommendet.?
I am curiously awaiting your answers and suggestions,
Bjoern Knafla
-- bknafla++at++techfak.uni-bielefeld.de
This archive was generated by hypermail 2b29 : Wed Mar 08 2000 - 14:17:28 PST