RE: [5/5] wined3d: Handle texture coordinates the same way we handle other vertex attributes

[Stefan Dösinger]

Here's a thought regarding handling the lack of GL_ARB_multitexture support.
Since pretty much all cards out there have multitexture support(even my
junky Mach64 card), we could just use one texcoord function array, and if
multitextures are really not supported, use a wrapper function that calls
the non-multitexture gl function and just drops the texture unit. That
avoids the if check in this pretty performance critical part on probably all
cards out there that are in use.
> -----Original Message-----
> From: [e-mail] [mailto:wine-patches-
> [e-mail]] On Behalf Of Henri Verbeet
> Sent: Wednesday, September 24, 2008 9:14 AM
> To: [e-mail]
> Subject: [5/5] wined3d: Handle texture coordinates the same way we
> handle other vertex attributes

[5/5] wined3d: Handle texture coordinates the same way we handle other vertex attributes

[Henri Verbeet]

2008/9/24 Stefan Dösinger :
> Here's a thought regarding handling the lack of GL_ARB_multitexture support.
> Since pretty much all cards out there have multitexture support(even my
> junky Mach64 card), we could just use one texcoord function array, and if
> multitextures are really not supported, use a wrapper function that calls
> the non-multitexture gl function and just drops the texture unit. That
> avoids the if check in this pretty performance critical part on probably all
> cards out there that are in use.

Yeah, although I wouldn't be opposed to simply making ARB_multitexture
a hard requirement either. I doubt there are any configurations left
that don't support multitexture but that would otherwise be able to
run Wine.

[5/5] wined3d: Handle texture coordinates the same way we handle other vertex attributes

[Stefan Dösinger]

> Yeah, although I wouldn't be opposed to simply making ARB_multitexture
> a hard requirement either. I doubt there are any configurations left
> that don't support multitexture but that would otherwise be able to
> run Wine.

I guess(and we discussed that on IRC, just adding it for the sake of the archives) that we can happily emulate ARB_multitexture with a texture limit of 1 texture if it isn't supported if we really want compatibility for such old cards. That should free us from quite a a few ugly and needlessly expensive if checks