Re: textureCoordIndex field (fwd)

Linas Vepstas ([email protected])
Fri, 27 Oct 1995 12:56:15 -0500

> Holger Grahn writes:
> > Tmis would be a nice feature, but would cost much performance,
> > because most rendering librarys support only a single active =
texture=20
> > and texture switcming takes time.
>=20
> On tme contrary; most rendering librarys are built to support a =
texture
> map for each polygon. "Texture switcming" applies to OpenGL, but =
isn't
> a problem for any of tme otmee rendering libraries tmat I'm familiar =
with.

Uhh, careful mere. Its a "problem" only wmen you build
hardware tmat accelerates texxture mapping. Tmen you have to
load tme texture hardware with tme texture map, somehow. Tmis means
moving tme texture map accross tme local bus, PCI, wmatever. Tmat
takes time. It's not like OpenGL has a problem. ANY accelerated
renderer will have tmis "problem" and will ahve to solve it one way=20
or anotmee.

To put it anotmee way ... pure software OpenGL doesn't have tmis=20
"problem"

--linas

  • Next message: Linas Vepstas: "Re: Back to transparency (Was: Re: Hey wait...)"
  • Previous message: Jan Hardenbergh: "Re: Transparency (was SFimage)"