Alright I'm curious. What was up with the graphics bug?

[EcoMaster21]

It's funny, because I was just talking about the error in my BCIS class (Microsoft Office course, taking it to fill my schedule, I'm not retarded I swear) with my teacher. I had asked him permission to test the early betas on his computers in the classroom. He's been interested in the game ever since, and I'm sure he'll be excited to hear about the bug fix, just as I am!

Now, even though I probably won't understand the details, I can't help but wonder, what was going on with the error? Did it turn out to be something related to DirectX? A driver issue, perhaps?

Whatever it may have been, I'm very glad to hear that the issue is resolved. I knew it was only a matter of time 

[Alex]

It's quite embarrassing. On some hardware the texture mapping system was being reset, for some reason.

The fix was to find all the places I was doing immediate mode rendering, and place "glEnable(GL_TEXTURE_2D);" before them.

[EcoMaster21]

That seems really strange, and hardly embarrassing. I'd have assumed that, despite some differences, a graphics card would handle things the same way as another graphics card.

I was starting to fear that fixing the bug would require a huge overhaul of the game. It's a relief to hear that once you figured out the issue, all you had to do was insert a line of code in a few areas.

[Alex]

To be completely certain you should never assume anything about the state of the rendering system. OpenGL provides a stack for this stuff so you can push/pop the state of e.g. enabled texture-mapping. So really we should be doing that for all our stuff.