Re: Flight loader Callback questions

New Message Reply Date view Thread view Subject view Author view

Marcus Barnes (marcus++at++multigen.com)
Fri, 13 Feb 1998 16:53:06 -0800


On Feb 13, 9:37pm, Mario Veraart wrote:
>1. If I have a database that uses external refs
> I don't always get a callback on all the nodes that are
> part of the performer tree.

nodes and (sub)trees that are instanced are not individually processed.
therefore such callbacks are not invoked.

[munch]

>What is the reason that for a second level external
>I don't get callbacks for a second instance of the
>first level external?

you may only be getting the 1st level callbacks because the external references
must be reloaded because at least one of their palettes is unique (color,
material, texture). you can confirm this with:

setenv PFNFYLEVEL 5

... the loader prints a notice for each file loaded and at DEBUG level prints a
message for each file referenced (cloned). you will only get one CB_CLONE
callback each time an externally referenced file is cloned.

>2. The callback function has in it's switch statement
>the constant CB_PATH. The Readme file says it is generated
>when we use the road or road path in the flight file.
>What do I have to model to get a callback with CB_PATH?

using the MultiGen Road Tools will produce both road and path (lane) nodes.
path nodes are converted to a geoset of line strips whose traversal masks are
set to zero for both DRAW and ISECT. this clears them from being culled, drawn
and intersected. the CB_PATH callback is provided so that the application can
access the information as desired.

Regards.

--
+ Marcus Barnes, Technical Staff        mailto:marcus++at++multigen.com +
+ Multigen Inc.                         http://www.multigen.com    +
+ 550 S. Winchester Blvd.               phoneto:1-408-556-2654     +
+ Suite 500 San Jose CA 95128           faxto:1-408-261-4102       +
=======================================================================
List Archives, FAQ, FTP:  http://www.sgi.com/Technology/Performer/
            Submissions:  info-performer++at++sgi.com
        Admin. requests:  info-performer-request++at++sgi.com

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:56:47 PDT

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