From: Lewis (mlewis++at++interaccess.com)
Date: 10/29/2001 05:17:51
Hello
I use pfSwitch and pfSequence to animate my loaded data. i.e if have
mutliple children
under my pfSwtich node and the children are pfNodes created by the
pfLoadFile function
and I cyle through the children to animate my data.
If I am understanding this correctly when doing pfLoadFile to create a node,
performer caches this
data into shared memory given that this is under the PFSHAREDSIZE limit
otherwise the application
crashes.
Once these loaded pfNodes are conected in the performer tree and under a
switch, doing a setVal(childId)
will access this cached data for this pfNode thus saving much time not
having to load this pfNode again.
I find that when I cyle through the children of the pfSwitch, my animation
runs smoothly when I am using a portion
of my shared memory. But when I am loading enough pfNodes to near my
PFSHARED size limit. My animation
runs much slow, and with some frames it pauses even more when steping
through each child under the pfSwitch.
When performer slows down cylcing through the data, Is performer actually
going to virtual memory in these instances
which I would find odd since all my data would be in the PFSHARED size
limit. or is performer thrashing by spending time
doing paging operations in its seconday cache memory accessing the cached
data based on the child id.
Mike
This archive was generated by hypermail 2b29 : Mon Oct 29 2001 - 05:25:53 PST