Changing textures on the fly.

Mark Baranowski (baranowski++at++marklynn.demon.co.uk)
Wed, 20 Dec 1995 15:37:09 GMT

• Next message: Fernando D. Mato Mira: "Re: C++ new/delete operator with shared arena in 2.0"
• Previous message: Sharon Clay: "Re: Fileformats in performer 2.0"

As a 'newbie' to Performer (1.2) still waiting to go on the training
course, I am hoping someone will be able to give me an overview of the
issues involved in changing the texture maps used on pfGeoSets at
runtime.

We use .flt databases in Performer and Vega applications. I am
assuming that the pfGeoSets created by the loader will have a
pfGeoState attached.

Is a call to:

pfGStateAttr(geostate, PFSTATE_TEXTURE, newTex)

all I need to do, and will there be a problem identifying those
GeoStates which reference the particular texture?

As I want this to apply to all geometry which was modelled with the
original texture, is redefining the texture associated with that
particular texture index a viable alternative? (I guess I would have
to dip into GL (texdef2d and the like) to do that?)

Thanks in advance for any advice.

Merry Christmas.

Mark.
Mark Baranowski at work (baranowski++at++marklynn.demon.co.uk)
Pera, VR Division. Melton Mowbray, Lecicestershire. UK.
Tel: +44 1664 501501, Fax: +44 1664 501553

• Next message: Fernando D. Mato Mira: "Re: C++ new/delete operator with shared arena in 2.0"
• Previous message: Sharon Clay: "Re: Fileformats in performer 2.0"

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:52:10 PDT

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