Re: Performer questions

New Message Reply Date view Thread view Subject view Author view

Kevin Russo (russo++at++ait.nrl.navy.mil)
Mon, 7 Mar 94 12:11:01 PST

>> - In one of our applications at least, the culling does not work properly.
>> Objects suddenly vanish before they leave the viewing frustrum. Any ideas
>> why this could be? We are not changing any of the GeoSets or other data in
>> the hierarchy after it has been initially set up.
>
> Print out the scene with pfDebugPrint and make sure your bounding
> boxes are reasonable.

I found that for linestrips, anyway, Performer only checks if the first
point or so of the lineseg is in the viewing frustum, regardless of
the bounding box. Perhaps this little speed enhancing trick is at work
in other types of GeoSets?

I overcame it by installing a node pre-cull callback like this:
node_cull_pre_cb() { pfCullResult(PFIS_ALL_IN); return PFTRAV_CONT; }

It was most frustrating to watch my trajectory line segments disappear
any time the origin wasn't in view.

Kevin

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:50:11 PDT

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