Richard M. Spencer (rspencer++at++es.rti.org)
Mon, 18 Nov 1996 16:58:42 -0500 (EST)
We have a driving simulation terrain database we created from scratch but we
want to make some efficiency modifications. Most questions apply to both
Vega and Performer and the bug applies to the 3D Studio loader.
P1) The database was built in 3D Studio but we converted the models to
Inventor format due to problems with the 3D Studio loader tagging all
parts of colored objects as textured and showing up black. We would
prefer to do all modelling in 3D Studio only without the conversion but
the 3D Studio loader and/or the Autodesk/Kinetix library has this bug.
Also, the 3DS loader uses the IrisGL ImageView API to load textures and
we are running on OpenGL-only Impacts and IRs (I know this particular
problem has been posted on the Performer news group before). The 3DS
loader also failed to load the rather large terrain database but the
Inventor loader had no problem.
P2) Unfortunately, the Object Property editor does not load Inventor objects.
Q1) How should I break up the terrain into pieces so that I can page it and
its textures piecemeal when they come into view? Is this a LOD function
or just a cull function, or both (Fade LOD)?
Q2) If I create my objects with two or more levels of detail, how do I
point to the LOD sets preferably from the Vega/Lynx adf or programmatically
using the Vega or Performer API?
Thanks
Richard M. Spencer Research Triangle Institute
rspencer++at++es.rti.org Center for Digital Systems Engineering
919-541-6733 (voice) 3040 Cornwallis Road, Herbert Bldg, Rm 246
919-541-6515 (fax) P.O. Box 12194; RTP, NC 27709-2194
=======================================================================
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:58 PDT