Re: Performer 2.0 questions

New Message Reply Date view Thread view Subject view Author view

Michael Jones (mtj++at++babar)
Thu, 9 Feb 1995 16:38:34 -0800


On Feb 9, 4:14pm, Robert Reif wrote:
> Subject: Performer 2.0 questions

:Will the following features be in the next Performer release?
:
:1. A function to clean a scene graph of excess nodes like what is available
:in the MultiGen flight loader.

Yes. This general ability is also used in the OpenInventor loader beta
that's on our ftp server. It will be available to all loaders and applications.

:2. A function to allow appending textures to a texture list so more than
:one node hierarchy's textures can be loaded.

You can make as many texture lists as you want, you can use normal
list API to glue lists together, and you can change the existing code at will.
Any of these will accomplish what you describe.

:3. A way to save a node hierarchy to disk for re-reading later, or preferably
:to some of the supported input formats to allow editing. You could then use
:Performer to write a file conversion program.

You can do this now, of course. Several companies have written such
programs, and at least one has been made available for public FTP.
The only issue here is more business than technical, in that at least
one of the loaders provided with IRIS Performer clearly prohibits
this translation and export step. So you would not want to convert
files in that format without permission.

This prohibition aside, I imagine that future versions of Performer will
have integrated support for exporting data in at least four formats:
OpenInventor, Alias, Wavefront, and a fast-loading Performer format.
These will not all be available in the next release, though.

-- 

Be seeing you, Phone:415.390.1455 Fax:415.965.2658 M/S:8U-590 Michael T. Jones Silicon Graphics, Advanced Graphics Division mtj++at++sgi.com 2011 N. Shoreline Blvd., Mtn. View, CA 94039-7311


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

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