Re: Swimming Textures

New Message Reply Date view Thread view Subject view Author view

Marcus Barnes (marcus++at++multigen.com)
Fri, 31 May 1996 11:19:19 -0700


On May 30, 11:33am, Scott A. Friedman wrote:
> Subject: Swimming Textures
> Hello,
>
> We are porting an application of ours to Performer 2.0 and are noticing
> that the textures in our models are 'swimming'. We are using MultiGen
> models and use TX-BILINEAR minification.

Is the swimming typical for bilinear minification (probably)? or just plain
broken (make sure you have all IRIX 5.3 RE/GL patches)?

> The weird part is that our Performer 1.2 application does NOT exhibit
> this same behaviour. That is, the same model and code and textures do
> not swim. Are there any differences between the two versions that would
> cause this? We are running on an RE2 using GL for both applications.

Older Flight Loaders for Performer 1.x forced MIPMAP_TRILINEAR minification on
all textures, when running on Reality Engine. The V11, V13 and V14 (and also
.dwb) loaders, shipped with Performer 1.2, have this common (an SGI decision)
texture filter behavior.

As a history note, I first enabled full use of MultiGen texture .attr files in
June 1994 with loader release R14.1a for 1.2 (one of my first feature
enhancements to the loader :-).

Regards.

--
   ____ ___  ____  _    Marcus Barnes, Member Technical Staff
  / __ `__ \/ __ `( )   MultiGen Inc. 550 S. Winchester Blvd. STE 500
 / / / / / / /_/ / /    San Jose CA 95128 WEB: http://www.multigen.com
/_/ /_/ /_/\__, /_/     PH:1-408-556-2654 FX:1-408-261-4102
          /____/        EMAIL: marcus++at++multigen.com
=======================================================================
List Archives, FAQ, FTP:  http://www.sgi.com/Technology/Performer.html
            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 2.0b2 on Mon Aug 10 1998 - 17:52:56 PDT

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