Yves Martel (martel++at++signifi.com)
Tue, 03 Feb 1998 18:23:12 -0500
I have a problem writing my Alias SDL loader with Performer 2.2.
The problem I have is with the animations:
as a first solution to the animations, whenever I detect that a node is
animated, I insert a DCS in the geometry's tree and the loader keep the
animation matrices and a pointers to the DCS in an external data
structure. The application then has the responsability to go through the
structure and update the DCS for each frame with the appropriate matrix.
This solution works perfectly but it is not very elegant (I have to keep
that external data structure...)
I thought an other solution would be to create a Sequence of SCS for
each moving nodes. This solution would be much more elegant, the
application would only have to start the sequences... But that's where
my trouble start! This system works fine for very small animations,
but the time my loader take to exit seems to grow geometrically with
the number of children in the Sequences!
As soon as I start having more than 10 or 20 children for the sequences
(my test case has an arm with 3 joints, so 3 pfSequences) the program
take a looooong time exiting the loader! (something is happening
between the "return" in my loader and the "pfdLoadFile" in the
application).
I know I should probably be using a FSC with a pfEngine and a pfFlux
(and I'm working on it) but I still would like to know if the
"Sequence" solution should work, and what am I doing wrong ?
_______________________________________________________
Yves Martel Signifi.gVR
mailto:Martel++at++signifi.com 417 St-pierre suite 208
Tel: (514) 288-1453 Montreal, QC, CANADA
Fax: (514) 288-4112 H2Y 2M4
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
Submissions: info-performer++at++sgi.com
Admin. requests: info-performer-request++at++sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:56:43 PDT