发信人: Gamble_Tan@bbs.ustc.edu.cn (岫云), 信区: cnunix
标 题: SGI performer FAQ
发信站: 中国科大BBS站 (Sat Jun 20 06:17:09 1998)
转信站: Lilac!ustcnews!ustcbbs
SGI performer Frequently Asked Questions (FAQ)
This is one of the Silicon Graphics FAQ series, which consists of:
SGI admin FAQ - IRIX system administration
SGI apps FAQ - Applications and miscellaneous programming
SGI audio FAQ - Audio applications and programming
SGI diffs FAQ - Changes to the other FAQs since the last posting
SGI graphics FAQ - Graphics and user environment customization
SGI hardware FAQ - Hardware
SGI impressario FAQ - IRIS Impressario
SGI inventor FAQ - IRIS Inventor
SGI misc FAQ - Introduction & miscellaneous information
SGI movie FAQ - Movies
SGI performer FAQ - IRIS Performer
SGI pointer FAQ - Pointer to the other FAQs
SGI security FAQ - IRIX security
Read the misc FAQ for information about the FAQs themselves. Each FAQ is
posted to comp.sys.sgi.misc and to the news.answers and comp.answers
newsgroups (whose purpose is to store FAQs) twice per month. If you
can't find one of the FAQs with your news program, you can get it from
ftp://viz.tamu.edu/pub/sgi/faq/
ftp://rtfm.mit.edu/pub/usenet/news.answers/sgi/faq/
(rtfm.mit.edu is home to many other FAQs and informational documents,
and is a good place to look if you can't find an answer here.) The FAQs
are on the World Wide Web at
http://www-viz.tamu.edu/~sgi-faq/
If you can't use FTP or WWW, send mail to mail-server@rtfm.mit.edu with
the word 'help' on a line by itself in the text, and it will send you a
document describing how to get files from rtfm.mit.edu by mail. Send the
command 'send usenet/news.answers/sgi/faq/misc' to get the SGI misc FAQ,
and similarly for the other FAQs. Send the command 'send
usenet/news.answers/internet-services/access-via-email' to get the
"Accessing the Internet by E-Mail FAQ".
You may distribute the SGI FAQs freely and we encourage you to do so.
However, you must keep them intact, including headers and this notice,
and you must not charge for or profit from them. Contact us for other
arrangements. We can't be responsible for copies of the SGI FAQs at
sites which we do not control, and copies published on paper or CD-ROM
are certain to be out of date. The contents are accurate as far as we
know, but the usual disclaimers apply. Send additions and changes to
sgi-faq@viz.tamu.edu.
Topics covered in this FAQ:
---------------------------
-1- What is IRIS Performer?
-2- Where can I get more technical information about IRIS Performer?
-3- Where can I get more product information about IRIS Performer?
-4- The IRIS Performer mailing list
-5- The IRIS Performer FTP Archives
-6- The IRIS Performer WWW Pages in Silicon Surf
-7- The IRIS Performer Technical Report
-8- How does IRIS Performer relate to IRIS Inventor?
-9- What version of IRIS Performer should I use?
-10- What are all of the released versions of IRIS Performer?
-11- What patches should be used with IRIS Performer?
-12- Does IRIS Performer use IRIS GL or OpenGL?
-13- Is there a IRIS Performer file format?
-14- What database file formats can IRIS Performer read?
-15- Is there an IRIS Inventor file reader for IRIS Performer?
-16- What are the .tlf files used by the Performer Town and Village?
-17- What are the minimum requirements for using IRIS Performer?
-18- Binary Compatibility on different machines
-19- Binary Compatibility on different releases
-20- Guaranteeing Real Time performance
-21- How do I make GL calls from within a IRIS Performer program?
-22- How do I overlay graphics on top of my Performer scene?
-23- What is the difference between phases FREE, FLOAT, and LOCK?
-24- Use of PFTMPDIR to configure shared memory
-25- Which rendering primitives does IRIS Performer support?
-26- How do I do triangle meshes in Performer?
-27- ================= Known Problems =================
-28- Video Rate sometimes reported incorrectly
-29- Problems with Performer Town or Village demos
-30- Antialiasing
-31- Coplanar Polygons & pfDecal on certain platforms
-32- Networked graphics (DGL & GLX)
-33- Transparency
-34- Gangdraw and cursor loading
-35- Frame control on low- and mid-range machines
-36- Timing on pre-1992 platforms
-37- 2.0 Warnings from ld when building on IRIX 6.2
-38- 2.0 Bug OpenGL functions missing when building static executables
-39- 2.0 Bug Z buffer problems when moving windows on 5.3 EXtreme
-40- 2.0 Bug Use of more than 512 simultaneous textures
-41- 2.0 Bug IRIS GL on dual-head systems
-42- 2.0 Bug Resizing of pfPipeWindows in MP X apps
-43- 2.0 Bug Applying frustums transformed by pfOrthoXformFrust
-44- 2.0 Bug pfFlatten with pfCycleBuffer attribute arrays
-45- 2.0 Bug Sorting lights with pfChanBinSort()
-46- 2.0 Bug OpenGL disables back material modes
-47- 2.0 Bug CPU statistics in IRIX 6
-48- 2.0 Bug pfdLoadFile_flt FLT loader in IRIX 6
-49- 2.0 Bug hello sample program in IRIX 6
-50- 2.0 Bug Forked X input handing in IRIX 6.2
-51- 2.0 Bug Intersections with pfBillboard nodes
-52- 2.0 Bug Channel fade LOD attributes & mixed gfx configs
-53- 2.0 Bug libpfui C API incomplete
-54- 2.0 Bug libpfdb pfdLoadFile_dxf incomplete
-55- 2.0 Bug libpfdb pfdLoadFile_sgo incomplete
-56- 2.0 Bug IRIS GL perfly on Indy
-57- 2.0 Bug pguide/libpf/C/pipewin sample program
-58- 2.0 Bug pguide/libpf/C/lpstate sample program
-59- 2.0 Bug pfInitClock() and Video Rate on 250MHz IMPACT
-60- 1.2 Bug Billboard normals and intersections
-61- 1.2 Bug Incompatibility with IRIX 6.1 XFS
-62- 1.2 Bug Billboards with multiple pfGeoSets
-63- 1.2 Bug Flattening transformation hierarchies
-64- 1.2 libpf Bug Hang on Exit, 5.2 VGX
-65- 1.2 libpf Cull with overlapped draw latency
-66- 1.2 libpf Cull with overlapped draw hang
-67- 1.2 libpf Transparency Sorting
-68- 1.2 libpf Multiple EarthSky fog
-69- 1.2 libpf Bug Limit Phase
-70- 1.2 libpr Highlighting when using wireframe
-71- 1.2 libpf APPCULLDRAW does not honor LIMIT/FLOAT/LOCK phases
-72- 1.2 libpf Phase toggling overlapped cull and draw
-73- 1.2 libpf pfDataPool warning on exit
-74- 1.2 libpf Multi-channel stats warning messages
-75- 1.2 libpf Video warnings on Indy when multiprocessed
-76- 1.2 stats Frame statistics for lightpoints
-77- 1.2 stats Pixel fill statistics under 4.0.5 on RealityEngine
-78- 1.2 libpr Directional pfLightPoints
-79- 1.2 libpfutil pfuCollide is jerky
-80- 1.2 libpfutil pfuSaveImage broken
-81- 1.2 libpfsgi pfLoadDxf loader is incomplete
-82- 1.2 libpfsgi pfLoadIv loader is incomplete
-83- 1.2 GLX Overlay text with GLX on 4.0.5
-84- 1.2 GLX Toggling antialiasing with GLX on 4.0.5 RealityEngine
-85- 1.2 GLX Toggling antialiasing with GLX on any RealityEngine
-86- 1.2 GLX on 4.0.5 Indigo, sample programs hang on startup.
-87- 1.2 samples smallfly drive models broken
-88- 1.2 samples pickfly drops core under abuse
-89- 1.2 samples detail example broken on 4.0.5
-90- 1.2 friends Belvis makefile requires pmake
-91- 1.2 friends Toon has bad models and textures
-92- 1.2 docs pfuGetGLXWin wrong on reference page
-93- 1.2 docs pfuLockDownApp gives the incorrect location
-94- 1.1 Bug with FP underflow
-95- 1.1 Bug with Multipipe Onyx
-96- 1.1 Bug Installing on Indy or Indigo2 XL
-97- 1.1 Bug Unable to determine Indy graphics type
-98- 1.1 Bug perfly cannot find libpf.so on Indy running 5.1
-99- 1.1 Bug perfly FP error messages in 5.0.1
-100- 1.1 Bug Installation on IRIX 5.2 - missing prerequisites
-101- 1.0/1.1 Bug intersections with pfSwitch'es
-102- 1.0/1.1 Bug with pfTexture()
-103- 1.0/1.1 Bug with pfAntiAlias()
-104- 1.0/1.1 Bug with pfFlatten()
-105- 1.0/1.1 Bug with pfSequences
-106- 1.0/1.1 Bug with pfClosestPtOnPlane()
-107- 1.0/1.1 Bug on ELAN/XS with wireframe PFGS_QUADS
-108- 1.0/1.2-IRIX4 Bug Z buffer configuration on 4.0.5 RealityEngine
-109- 1.0 Bug pfInit(): mmap failed for /dev/zero
-110- 1.0 Doc Bug in pfMakePolarSeg() man page
-111- 1.0 Doc Bug in pfDispList() man page
-112- 1.0 Doc Bug in PFPG (simple.c)
-113- 1.0 Bug in pfGetTime()
-114- 1.0 Bug in pfNodeBBox()
-115- 1.0 Bug in pfInitGfx() with Z-buffer on RealityEngine
-116- 1.0 Bug in libpfflt combineLODs()
-117- 1.0 Bug with two-sided material and pfMtlColorMode()
-118- 1.0 Bug in pfFilePath()
-119- 1.0 Bug in pfGetCurGState()
-120- 1.0 Bug in pfGetCurState()
-121- 1.0 Bug with cloned scenes
-122- 1.0 Bug intersections in collide.c
-123- 1.0 Bug with flattened pfLightPoints
-124- 1.0 Bug intersections with pfSequences
-125- 1.0 Bug intersections with non-indexed quads
----------------------------------------------------------------------
Subject: -1- What is IRIS Performer?
Date: 12 Dec 95 00:00:01 EST
IRIS Performer provides a powerful and extensible programming
interface (with ANSI C and C++ bindings) for creating real-time
visual simulation and other interactive graphics applications.
IRIS Performer 2.0 supports both the IRIS Graphics Library (IRIS
GL) and the industry standard OpenGL graphics library; these
libraries combine with the IRIX operating system and REACT
extensions to form the foundation of a powerful suite of tools and
features for creating real-time visual simulation applications on
Silicon Graphics systems.
IRIS Performer is an integral part of the Onyx/Onyx2 RealityEngine
& InfiniteReality and Indigo2/Octane Impact graphics systems and
provides interfaces to advanced features of RealityEngine-class
graphics. IRIS Performer is compatible with uniprocessor and
multiprocessor SGI graphics platforms and attains maximum
performance on all. IRIS Performer provides an extensible basis
for creating real-time 3D graphics applications in the fields of
visual simulation, entertainment, virtual reality, broadcast video,
and computer aided design. IRIS Performer is the flexible,
intuitive, toolkit-based solution for developers who want to
optimize performance on Silicon Graphics systems.
IRIS Performer consists of two main libraries, libpf and libpr, and
four associated libraries, libpfdu, libpfdb, libpfui, and
libpfutil.
The basis of IRIS Performer is the performance rendering library
libpr, a low level library providing high speed rendering functions
based on pfGeoSets, efficient graphics state control using
pfGeoStates, and other application- neutral functions.
Layered above libpr is libpf, a real-time visual simulation
environment providing a high-performance multi-processing database
rendering system that takes best advantage of IRIS symmetric
multiprocessing CPU hardware.
The database utility library libpfdu provides powerful functions
for defining both geometric and appearance attributes of three
dimensional objects, encourages sharing of state and materials and
generates efficient triangle strips from independent polygonal
input.
The database library libpfdb uses the facilities of libpfdu, libpf,
and libpr to import database files in many popular industry
standard database formats. These loaders also serve as a guide to
developers creating new database importers.
libpfui contains user interface building blocks for creating
manipulators common to many interactive applications. This library
has both a C and C++ API and is GL independent.
Completing the suite of libraries is libpfutil, the IRIS Performer
utility library. It provides a collection of important convenience
routines implementing such diverse tasks as smoke effects,
MultiChannel Option support, graphical user interface tools, X and
IRIS GL event collection and management, and traversal functions.
For aid in application development, IRIS Performer includes sample
application source code ranging from simple programs to illustrate
particular features to the comprehensive, GUI-driven file viewer
perfly.
In addition to these SGI-developed tools, IRIS Performer also
includes a very large repository of sample code, databases, games,
and movies contributed by the Friends of Performer: companies and
individuals with services of general interest to the IRIS Performer
community. We encourage you to sample their wares.
------------------------------
Subject: -2- Where can I get more technical information about IRIS
Performer?
Date: 12 Dec 95 00:00:01 EST
The three best resources for additional information are:
- The IRIS Performer mailing list
- The IRIS Performer FTP Archives
- The Performer WWW pages in Silicon Surf
- The IRIS Performer Technical Report
See below for further information.
------------------------------
Subject: -3- Where can I get more product information about IRIS
Performer?
Date: 12 Dec 95 00:00:01 EST
For product information about IRIS Performer or SGI Visual
Simulation issues contact Ralph Humphries (ralphh@asd.sgi.com). To
learn about SGI Virtual Reality solutions contact Joshua Mogal
(mogal@asd.sgi.com). To just give in and buy a copy call SGI
Direct at 1-800-800-7441 (product SC4-PERF-2.0), or to have both a
demonstration and a presentation call your local SGI sales office.
Brochure-style information about IRIS Performer is also available
from the Performer WWW pages in Silicon Surf (see below)
------------------------------
Subject: -4- The IRIS Performer mailing list
Date: 12 Dec 95 00:00:01 EST
The IRIS Performer mailing list is a resource for developers who
are using IRIS Performer to maximize the performance of their
graphics applications on Silicon Graphics hardware. The list is an
unmoderated, free-form discussion of IRIS Performer with issues
both technical and non-technical; and provides feedback to Silicon
Graphics about the product. Much like the comp.sys.sgi.*
newsgroups, it is not an official support channel but is monitored
by the IRIS Performer development team, so it's an excellent source
of early information about upcoming events and product features, as
well as a venue for asking questions and having them answered.
To become a subscriber to the IRIS Performer mailing list you must
send email to:
info-performer-request@sgi.com
New subscribers are added "by hand". Once your request is processed
you will recieve submission/posting instructions, some guidelines,
and a current copy of the Performer Frequently-Asked-Questions (FAQ)
list.
The mailing list has become rather large and carries several
hundred messages per month. A performer newsgroup with a gateway
to the mailing list may be created if there is enough interest.
Mailing list archives are available in the Performer FTP area (see
below) in ftp://sgigate.sgi.com/pub/Performer/monthly-archives/
------------------------------
Subject: -5- The IRIS Performer FTP Archives
Date: 12 Dec 95 00:00:01 EST
An archive of Performer-related material is available via anonymous
FTP: ftp://sgigate.sgi.com/pub/Performer
Current Contents:
README - Overview file
FAQ - The Performer FAQ
INFO-PERFORMER - information about the Performer mailing list
src/ - Sample source code & misc patches
docs/ - IRIS Performer docs including SIGGRAPH '94 paper
selected-topics/ - directory of info, Q&A, etc from mailing list
monthly-archives/ - raw archives (monthly) of the mailing list
CortaillodCentre/ - goodies from SGI's Cortaillod Office
RealityCentre/ - goodies from SGI's RealityCentre in the UK
------------------------------
Subject: -6- The IRIS Performer WWW Pages in Silicon Surf
Date: 12 Dec 95 00:00:01 EST
Silicon Surf (http://www.sgi.com/) contains an archive of
Performer-related technical and promotional material in the
_Extreme Tech_ section.
http://www.sgi.com/Technology/Performer contains links
to further information regarding:
- What is IRIS Performer ?
- IRIS Performer 2.0 Technical Information
- IRIS Performer 2.0 Product Information
- IRIS Performer Friends, Goodies, & Free Stuff!
- The IRIS Performer Mailing List
- The IRIS Performer Anonymous FTP Archives
- The IRIS Performer Frequently Asked Questions (FAQ).
------------------------------
Subject: -7- The IRIS Performer Technical Report
Date: 12 Dec 95 00:00:01 EST
The IRIS Performer 2.0 Technical Report (IRIS-PERF-TR-10/95) is
available in hardcopy from your local Silicon Graphics sales
office. An electronic copy (Postscript format) is also available
via FTP from:
ftp://sgigate.sgi.com/pub/Performer/docs/pf2.0techreport/
------------------------------
Subject: -8- How does IRIS Performer relate to IRIS Inventor?
Date: 26 Jun 93 00:00:01 EST
The short answer is, Performer was designed for vis-sim, while
Inventor was designed to be more general purpose.
IRIS Performer is for developers who need to extract maximum
performance from SGI machines for visual simulation, virtual
reality, game development, and high-end CAD systems. Often these
applications need multi-processor Onyx systems with multiple
RealityEngine pipelines with a high degree of parallelism and
running at fixed frame rates.
Inventor is designed for maximum programmer productivity when
writing other kinds of 3D applications, like modelling, animation,
visualization, etc.
Both toolkits are general purpose enough that they could be extended
into the domain of the other, but the question you should consider is
"what is the *fundamental* goal of my graphics development?" If it's
portability to non-SGI systems, easy X-window system integration, or
handy graphic widgets, IRIS Inventor is for you. If it's brochure-
level performance in advanced graphic applications for the specific
domains listed above, then IRIS Performer would be the likely tool.
------------------------------
Subject: -9- What version of IRIS Performer should I use?
Date: 17 Mar 97 00:00:01 EST
IRIX performer_eoe performer_dev +Patches
-----------------------------------------------------------------------
6.4 2.0.4 2.0 1392 (dev)
6.3 2.0.3 2.0 1696 (eoe), 1392 (dev)
6.2 (IR only*) 2.1 2.1 n/a
6.2 (non-IR*) 2.0.1 2.0 1696 (eoe), 1392 (dev)
5.3 2.0 2.0 1414 (eoe & dev)
(*) Onyx [not Onyx2] InfiniteReality systems running 6.2 should use
IRIS Performer 2.1 (eoe and dev). Note that Performer 2.1 is
-only- officially supported on Onyx InfiniteReality systems running
IRIX 6.2. Other systems running 6.2 should use 2.0.1 eoe and 2.0
dev, (plus patches) as indicated above.
------------------------------
Subject: -10- What are all of the released versions of IRIS Performer?
Date: 17 Mar 97 00:00:01 EST
Performer 2.0.4: performer_eoe updated for compat. with IRIX 6.4
[equivalent updates in patch 1696 for 6.2 & 6.3]
Performer 2.0.3: performer_eoe updated for compat. with IRIX 6.3
Performer 2.1.2: nickname of the 2.1 compatibility libs in 2.0.4
Performer 2.1.1: nickname of the 2.1 compatibility libs in 2.0.3
Performer 2.1: Onyx InfiniteReality systems only (eoe and dev)
Performer 2.0.2: nickname of patches 1347+1392 (for IRIX 6.x) or
patch 1414 (for IRIX 5.x) for Performer 2.0.1/2.0
Performer 2.0.1: 2.0 EOE update only, for systems running 6.2 (non-IR)
Performer 2.0: For IRIX 5.3, 6.1, or (dev only) 6.2
IRIS Performer 1.2/IRIX5: (obsolete) For IRIX 5.2, 5.3, 6.0.1, 6.1
IRIS Performer 1.2/IRIX4: (obsolete) For IRIX 4.0.5(A-J) only
IRIS Performer 1.1: (obsolete) For IRIX 5.x only
IRIS Performer 1.0: (obsolete) For IRIX 4.x only
Patch 1696: performer_eoe updates equivalent to 2.0.4.
updates 2.0.1, 2.0.2, 2.0.3 to revs equiv to 2.0.4.
Replaces 1347.
Patch 1414: performer 2.0 eoe & dev patch for IRIX 5.3 only
Patch 1392: performer_dev 2.0 patch for IRIX 6.2, 6.3, 6.4.
Patch 1347: performer_eoe 2.0.1 patch for IRIX 6.2 only
Historical/Background information:
Note that the above list is included only for completeness' sake.
You probably do not need the "highest numbered" version of
Performer. For example, Performer 2.1 was released -before-
Performer 2.0.4.
Except for Onyx InfiniteReality, systems running 6.2 should load
performer_eoe 2.0.1 from the IRIX cd, and performer_dev 2.0 from
the Performer 2.0 CD. Then load the patches as described below.
Onyx InfiniteReality systems running 6.2 should load performer_eoe
and performer_dev 2.1 from the Performer 2.1 cd.
Systems running 6.3 (O2) should load performer_eoe 2.0.3 from the
IRIX cd, and performer_dev 2.0 from the Performer 2.0 CD. Then
load the patches as described below.
Systems running 6.4 (Origin 200, Origin 2000, Onyx2 IR, Onyx2
Reality, Octane) should load performer_eoe 2.0.4 from the IRIX cd,
and performer_dev 2.0 from the Performer 2.0 CD. Then load the
patches as described below.
Performer 2.1 is only officially supported on Onyx InfiniteReality
systems running IRIX 6.2. It may work on other platforms, but is
only fully tested on Onyx IR. Also note that 2.0.4, 2.0.3, or
2.0.1+patch1347 are all more recent than 2.1.
The N32 and N64 libraries in Performer 2.0 are not intended for
systems running IRIX 6.1. If you require N32 or N64 functionality,
you need to upgrade to 6.2 (or above) and use 2.0.1 (or above).
Performer 2.0 was originally shipped for 5.3. In 6.2, the
performer_eoe portion was updated to version 2.0.1; in 6.3, to
2.0.3; and in 6.4, to 2.0.4. performer_dev 2.0 (plus patch) is to
be used with each.
No further releases of Performer are planned for IRIX 4.x or 5.x.
Performer 1.2 was shipped for both 4.0.5 and 5.2 systems. If you
are using IRIS Performer 1.2, only install that version that is
appropriate for your machine. The IRIS Performer version is
indicated by the "IRIX4" or "IRIX5" string in each product name.
IRIX4 products should only be installed on 4.0.5 systems. IRIX5
products can be installed on 5.2, 5.3, 6.0.1, and 6.1 systems.
When a choice is possible between using Performer 1.2 with IRIX 5.x
or IRIX 4.0.5, IRIX 5.x is highly preferable. IRIX 5.3 is the
current operating system release and contains many bug fixes and
enhancements utilized by IRIS Performer. IRIS Performer 1.2/IRIX4
was intended only for users who are unable to upgrade to IRIX 5.x.
------------------------------
Subject: -11- What patches should be used with IRIS Performer?
Date: 14 Oct 96 00:00:01 EST
performer_eoe:
6.4: No patches required for performer_eoe 2.0.4
6.3: Patch 1696 - updates Performer 2.0.3 EOE -> 2.0.4 EOE
6.2: Patch 1696 - updates Performer 2.0.1 EOE -> 2.0.4 EOE
5.3: Patch 1414 - updates Performer 2.0 eoe & dev -> 2.0.2.
performer_dev:
All performer_dev 2.0 should be upgraded to performer_dev 2.0.2.
6.4: Patch 1392 - updates Performer 2.0 DEV -> 2.0.2 DEV
6.3: Patch 1392 - updates Performer 2.0 DEV -> 2.0.2 DEV
6.2: Patch 1392 - updates Performer 2.0 DEV -> 2.0.2 DEV
5.3: Patch 1414 - updates Performer 2.0 eoe & dev -> 2.0.2.
Patch 1696 updates all performer_eoe 2.0.x to 2.0.4. Patch 1696
replaces patch 1347.
performer_eoe 2.0.2 and 2.0.4 are both compatible with
performer_dev 2.0.2.
All of the patches require the base subsystems to be loaded first.
Customers with SupportFolio online access can download patches from:
http://www.sgi.com/Support/patch_intro.html
------------------------------
Subject: -12- Does IRIS Performer use IRIS GL or OpenGL?
Date: 12 Dec 95 00:00:01 EST
Performer 2.1 is OpenGL only, having bindings for O32 (32-bit)
OpenGL, N32 (32-bit) OpenGL, and N64 (64-bit) OpenGL.
IRIS Performer 2.0, 2.0.1, "2.0.2", 2.0.3, and 2.0.4 contain
bindings for O32 IRIS GL, O32 OpenGL, N32 OpenGL, and N64 OpenGL.
IRIS Performer 1.0, 1.1, and 1.2 use IRIS GL (32-bit).
------------------------------
Subject: -13- Is there a IRIS Performer file format?
Date: 26 Oct 93 00:00:01 EST
Yes. Performer "2.0.2", 2.0.3, 2.0.4, and 2.1 now include pfb (a
fast-loading binary database format) support in libpfpfb. It also
adds support of "pfa" format, a slow-loading ascii version of pfb.
The 'pfconv' program can be used to convert other file formats to
pfb.
Prior releases do not have a Performer-specific file format.
------------------------------
Subject: -14- What database file formats can IRIS Performer read?
Date: 12 Dec 95 00:00:01 EST
Performer "2.0.2", 2.0.3, 2.0.4, and 2.1 add support of the
following two formats, in addition to those available in Performer
2.0:
pfa: IRIS Performer ASCII format developed by Rob Mace
pfb: IRIS Performer BINARY format (very fast) developed by Rob Mace
IRIS Performer 2.0 and 2.0.1 contain direct import capabilities for:
3ds: AutoDesk 3DStudio binary data
bin: Minor SGI format used by powerflip
bpoly: Side Effects Software PRISMS binary
byu: Brigham Young University CAD/FEA data
dwb: Coryphaeus Software Designer's Workbench
dxf: AutoDesk AutoCAD ASCII format
flt11: MultiGen public domain Flight v11 format
flt14: MultiGen OpenFlight v14 format
gds: McDonnell-Douglas GDS things data
gfo: Minor SGI format (radiosity output)
im: Minor SGI format (IRIS Performer example)
irtp: AAI/Graphicon Interactive Real-Time PHIGS
iv: SGI OpenInventor / VRML 1.0
lsa: Lightscape radiosity solutions (ASCII)
lsb: Lightscape radiosity solutions (binary)
m: University of Washington mesh data
medit: Medit Productions medit modeling tool
nff: Eric Haines' ray tracing test data format
obj: Wavefront Technologies data format
post: Minor SGI format (example gridded terrain loader)
phd: Minor SGI format (polyhedra)
poly: Side Effects Software PRISMS ASCII data
pts: University of Washington point data
ptu: Minor SGI format (IRIS Performer example)
s1k: US ARMY SIMNET databases (Texas Instruments)
sgf: US NAVY standard graphics format
sgo: Minor SGI format
spf: US NAVY simple polygon format
sponge: Sierpinski sponge 3D fractal generator
star: Yale University compact star chart data
stla: 3D Structures Stereolithography (ASCII)
stlb: 3D Structures Stereolithography (binary)
sv: Format of John Kichury's i3dm modeler
tri: University of Minnesota Geometry Center data
unc: University of North Carolina data
Several other file formats will be available via translators:
via Acuris Corporation translators (to OpenInventor):
iges Old standard computer aided design interchange format
alias Alias Research animation system data
3ds AutoDesk 3DStudio
obj Wavefront Technologies OBJ format
dxf AutoDesk AutoCAD format
softimage Microsoft/Softimage animation system data
via Clarus AB translators:
step New standard computer aided design interchange format
vertigo Vertigo animation system data
via Syndesis Corporation translators (to OpenInventor):
3D Studio, BRender, Alias polyset, CAD-3D, CADL, DXF, Imagine,
Inventor, LightWave objects and scenes, MovieBYU, Haines NFF,
Sense8 NFF, POV-Ray, Pro/ENGINEER, Prisms, RAW, RenderWare,
Sculpt, SGI spin, Soft F/X, stereolithography, StyleGuide,
Swivel, GDS "things", trueSpace, Vertigo, Vista DEM, VideoScape
and Wavefront formats.
IRIS Performer 1.2 includes loading utilities and file loaders for:
- The SGI .bin, .sgo, .gfo, .poly, and .ptu formats
- IRIS Inventor's .iv format.
- Coryphaeus' Software .dwb format.
- Software Systems (MultiGen Inc) Version 11, 13, and 14 .flt
- The SuperViewer .sv format used in I3DM
- Lightscape Graphics Software's .lsa and .lsb formats
- Autodesk's AutoCAD .dxf format
- Miscellaneous formats (.gfo, .irtp, .stla, .stlb).
For source code to loaders for MultiGen .flt versions greater than
11, contact MultiGen, Inc at (408) 556-2600.
IRIS Performer 1.0 and 1.1 include database loaders for MultiGen v11
"flt", SGI "bin", and SGI "obj" formats.
------------------------------
Subject: -15- Is there an IRIS Inventor file reader for IRIS
Performer?
Date: 12 Dec 95 00:00:01 EST
Yes. IRIS Performer 2.x ships with a fully-functional Open
Inventor 2.0 file loader.
IRIS Performer 1.2 ships with a minimal .iv reader that will read a
subset of the IRIS Inventor 1.0 format.
A port of the more robust 2.x reader for Open Inventor files is
also available for Performer 1.2, in the Performer FTP Archives:
ftp://sgigate.sgi.com/pub/Performer/src/pfiv1.6.tar.Z
No Inventor file reader exists for Performer 1.0 or 1.1.
------------------------------
Subject: -16- What are the .tlf files used by the Performer Town and
Village?
Date: 8 Apr 94 00:00:01 EST
They are encrypted .flt files of the Town and Village database.
Only the "demo" version of perfly shipped with RealityEngine
systems in demos.sw.visualization can read these files.
Unencrypted versions of the Town and Village databases are included
in the performer_friends.sw.town subsystem of Performer 1.2 and 2.0.
------------------------------
Subject: -17- What are the minimum requirements for using IRIS
Performer?
Date: 12 Dec 95 00:00:01 EST
IRIS Performer 2.1 is only for IRIX 6.2
IRIS Performer 2.0.4 (eoe) is only for IRIX 6.4
IRIS Performer 2.0.3 (eoe) is only for IRIX 6.3
IRIS Performer 2.0.1 (eoe) is only for IRIX 6.2.
IRIS Performer 2.0 is for IRIX 5.3, 6.1, or 6.2.
Patch 1347 (eoe) is only for IRIX 6.2
Patch 1396 (eoe) is for IRIX 6.2 or IRIX 6.3
Patch 1392 (dev) is for IRIX 6.2, IRIX 6.3, or IRIX 6.4
IRIS Performer 1.2/IRIX5 requires IRIX 5.2 or 5.3.
IRIS Performer 1.2/IRIX4 requires IRIX 4.0.5. Because IRIX 4.0.5F
added several new Graphics Library (GL) calls to support
RealityEngine features, any application that uses GL routines or
tokens found only in 4.0.5F and later, will not run properly under
4.0.5C and earlier releases.
------------------------------
Subject: -18- Binary Compatibility on different machines
Date: 12 Dec 95 00:00:01 EST
Applications compiled with IRIS Performer 2.0 using IRIX 5.3 will
run unmodified across all SGI platforms. For best performance, use
IRIS GL with RealityEngine and other pre-Impact systems and use
OpenGL for Impact and post-Impact graphics hardware.
OpenGL-oriented systems provide the IGLOO (Iris GL on OpenGL)
portability layer to execute IRIS GL applications, but it is not
the maximum performance route. Performance oriented developers are
advised to generate both IRIS GL and OpenGL executables, by linking
with the API-compatible IRIS Performer 2.0 IRIS GL and OpenGL
libraries. In this way, you can assure optimum performance across
present and future graphics systems. For OpenGL development on
RealityEngine with IRIX 5.3, patch 154 (or a superseding patch)
--
※ 来源: 中国科大BBS站 [bbs.ustc.edu.cn]
Powered by KBS BBS 2.0 (http://dev.kcn.cn)
页面执行时间：416.490毫秒