RE: isect

New Message Reply Date view Thread view Subject view Author view

From: Tomlinson, Gordon (GORDON.TOMLINSON++at++ca.com)
Date: 09/27/2001 07:09:02


HI Dirk

Have you made the updating of the bounding spheres on all the parent
groups and DCS' Dynamic..

Or when you do a write complete force a bounding sphere update.
Spheres are the first thing checked with itersections bounding boxes
of geosets are only check if the sphere test is passed

Regards

Gordon.
_________________________________________________________________
Gordon Tomlinson

Manager
Urban Simulation Products Engineering.

MultiGen-Paradigm
"a Computer Associates Company"
Suite 200, 16415 Addison Road, Addison, TX 75001 USA

Tel: 972 380 9798 ext 309 Fax: 972 380 9468

Email: gordon.tomlinson++at++ca.com

-----Original Message-----
From: Dirk Scheffter [mailto:scheff++at++iff.fhg.de]
Sent: Thursday, September 27, 2001 7:49 AM
To: info-performer++at++sgi.com
Subject: isect

pfHi there,

I use fluxed geosets which I modify in my app.
Geosets itself works correctly and are culled and displayed correctly.

(I recompute bounding boxes of geosets before writeComplete.)

But, I have extrem problems with intersection.

I apply intersection to a DCS which has DCS children which have geode
children which own the fluxed geosets.
(Oops, example:
(scene)
  DCS
    DCS
      geode
        fluxed geoset
        fluxed geoset
        ...
      geode
        fluxed geoset
        fluxed geoset
      ...
   DCS
   ...
)

The effect is that intersection works at initial appearance and in a
certain circle(!) around it. This circle is smaller than the channel
rectangle.

I tried to uncache intersection:

for all DCS nodes after creation I call:
pPfDCS->setTravMask(PFTRAV_ISECT, PFIS_SET_PICK,
  PFTRAV_SELF | PFTRAV_DESCEND | PFTRAV_IS_UNCACHE, PF_SET);

(This should include geodes, also, which are added before.)

For all geosets after creation I call:

pPfGSet->setIsectMask(PFIS_SET_PICK, PFTRAV_SELF | PFTRAV_IS_UNCACHE,
  PF_SET);

(This is done in the Flux init callback.)

Although I use isect class PFIS_SET_PICK I call pPfDCS->isect()
which isn't a problem in my mind. (PFIS_SET_PICK is just only a certain
value.)

Well, and my intersection ray is as long as the far clip distance
(1000m) and geometry appears rather close to near clip plane (1.5m).

Is there anybody, knowing the effect resp. the trick to come around it
resp. can enlight me?

Best regards,
Dirk.

-----------------------------------------------------------
Dipl.-Inf. Dirk Scheffter scheff++at++iff.fhg.de
Fraunhofer IFF fon: +49 (0) 391/40 90-854
Sandtorstr. 22 fax: +49 (0) 391/40 90-870
D-39106 Magdeburg http://www2.iff.fhg.de/~scheff
Germany
-----------------------------------------------------------

-----------------------------------------------------------------------
 List Archives, FAQ, FTP: http://www.sgi.com/software/performer/
Open Development Project: http://oss.sgi.com/projects/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 2b29 : Thu Sep 27 2001 - 07:21:34 PDT

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