Rémi Arnaud (remi++at++remi.engr.sgi.com)
Wed, 6 May 1998 11:08:12 -0700 (PDT)
Every libpf object (pfGroup, pfLOD...) have multiple copies that each correspond of
one of the APP/CULL/DRAW stage of the software pipeline. Performer synchronization
mechanism works using the addUpdate mechanism which is hidden inside pf objects.
This mechanism works only if called from the Application process, no other process
can modify the scene graph without perturbating the synchronization mechanism, and
that can be fatal. This problem was very difficult to track, so 2.2 has this
warning that let you know (in that particular case) that the DBASE process did a
direct modification to a pfGroup node. So it tells you that the mandatory pfBuffer
mechanism was not used in the Dbase process, and that the scene graph may be
corrupted.
I hope this helps.
_ / _ _
|_) _ ._ _ o /\ |_)|\ | /\ | || \
| \(/_| | || /--\| \| \|/--\|_||_/
=======================================================================
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:57:22 PDT