I think that I ran into this today while working on the X1900XT on Windows, so
it appears to be a potentially general issue. Some notes:
1) It occurs in both the ARB and GLSL backends.
2) The GL_INVALID_OPERATION is actually triggered by drawing, it is simply be
"caught" by the next Sh GL function to be called. That means that it could be
caused by anything from improperly setup state to incorrectly bound textures, etc.
3) Using a single texture (either kd or ks) avoids the problem...
4) Mipmapping or not doesn't seem to matter.
|