Re: Performer 1.0 on Extremes

New Message Reply Date view Thread view Subject view Author view

Jim Helman (jimh++at++surreal)
Mon, 13 Dec 93 12:32:15 -0800

If you ware picking a single object, you probably just want the
closest hit, which is the default if you do not OR PFPK_M_ALL into
the mode. You can also OR in

     /* isect modes */
     #define PFTRAV_IS_PRIM 0x01 /* report isects at poly level */
     #define PFTRAV_IS_GSET 0x02 /* report isects at geosets */
     #define PFTRAV_IS_GEODE 0x04 /* XXX - libpf report isects at geode nodes */
     #define PFTRAV_IS_NORM 0x08 /* return normal */
     #define PFTRAV_IS_CULL_BACK 0x10 /* ignore backfacing polygons */
     #define PFTRAV_IS_CULL_FRONT 0x20 /* ignore frontfacing polygons */

1.2 uniquely identifies the object intersected by a path through the
scene graph. Unfortunately, 1.0/1.1 only provides the pfGeoSet. If
your models are not instanced (i.e. the same subgraph or geoset does
not exist under multiple DCSes) the pfGeoSet will provide a unique ID.
If you need to retain instancing, you could switch to pfSegsIsectNode,
use a preIntersection traversal callback on each DCS and a
discriminator callback to log the current DCS.

rgds,

-jim helman

jimh++at++surreal.asd.sgi.com
415/390-1151

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:07 PDT

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