2009/8/20 Joerg-Cyril.Hoehle@t-systems.com:
Hi,
This fixes bug #11167. It depends on my previous patch.
One unclear issue about glHint() is the scope. What textures does it affect? When?
An alternative would be, as Stefan Dösinger puts it: "just check if the app ever sets two contradicting filter types" but I don't know how "global" the effect of glHint() is (per UNIX process, per .exe, per GL context, per active texture, per ...)?
Another alternative would be to replace SetAutoGen with just a FIXME to at least get rid of the bogus >>>>>> glTexParameter call.
This isn't quite correct. The hint indeed applies to the entire context, and you should map the linear filter to GL_NICEST. We should probably generate mipmaps explicitly with glGenerateMipmapEXT() if the FBO extension is available.