Veraart (rioj7++at++fel.tno.nl)
Thu, 11 Jul 1996 14:25:07 +0200 (MET DST)
I have an application that does a lot of intersection queries on a terrain
database file in flight format.
The application was first written for Performer 1.2. I turns out that
for a few polygons in the database the intersection was wrong. The returned
height was about 20 to 50 m wrong, above or below the actual polygon height.
Almost all samples/intersections taken on these polygons gave a wrong answer.
Due to circumstances I had to port the application to Performer 2.0.
Now the problems are gone and it works about 10 times faster.
The performer 1.2 version took 8 hours on a 8 CPU ONYX (fully utilised)
The performer 2.0 version took 45 minutes on the same computer.
My questions:
Was there a bug fix in teh intersection part of Performer or
the flight performer loader?
What is the reason that it runs 10 times faster?
Mario
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
Submissions: info-performer++at++sgi.com
Admin. requests: info-performer-request++at++sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:53:10 PDT