Scene graph buffering

David Gray (david.gray++at++computer.org)
Fri, 04 Dec 1998 10:30:34 +1100

• Next message: Dorosky, Christopher G: "pfImageTile q'ing"
• Previous message: Marcus Barnes: "Re: Final: Problems with fading alphatexture in .flt"
• Next in thread: David Gray: "Re: Scene graph buffering"
• Reply: David Gray: "Re: Scene graph buffering"

I have a question regarding the interaction between the application
process (App) and a forked intersection process (Isect).

I would like to know when scene graph changes made by the App (e.g.
changing DCS matrices) are seen by Isect.

Given that processing in the Isect callback may span multiple frames, I
believe that there are three possibilities. The App changes may be
visible by Isect:

1. immediately,

2. at the next call to pfFrame in the App, or

3. the next time the Isect callback is called.

Which is it?

Thanks for your help,
David Gray.

CSC Australia Pty Limited Tel: +61 (2) 9901 1456
460 Pacific Highway Fax: +61 (2) 9901 1110
St Leonards NSW 2065 Australia Email: david.gray++at++computer.org

• Next message: Dorosky, Christopher G: "pfImageTile q'ing"
• Previous message: Marcus Barnes: "Re: Final: Problems with fading alphatexture in .flt"
• Next in thread: David Gray: "Re: Scene graph buffering"
• Reply: David Gray: "Re: Scene graph buffering"

This archive was generated by hypermail 2.0b2 on Thu Dec 03 1998 - 15:47:32 PST

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.