First of all, this is the first time I've upgraded my UT99 game since version 432 and I only did it because of the promise of the new UnrealEd 2.2, which works beautifully, even though it still has a couple of bugs. I am also enamored with the new audio capabilities that came with openAL.
When i first ran 469d with the heralded XOpenGL.dll (im running on a Windows 7 64-bit quad-core i7 with 8GB RAM, and openGL 6.1.7601), i just went with the default settings for XOpenGL and was pleasantly surprised at the difference in-game. The 3d video was definitely better, but i experienced reduced framerate during gameplay, which i never had with software rendering and wasnt going to tolerate. So i tweaked the settings for XOpenGL and played it and it was fine.
The problem didnt start until after the first run with XOpenGL. When i went back into it later, and every time after, i got this error message from Windows:
While working with UnrealEd, i think it ran out of memory or something, bc it wrote OVER my unrealtournament.ini file with everything it was trying to save, deleting all other game categories. On a hunch, i pulled the ini out of the (UT99) system folder, and started UT99 game again. As i thought, the game created a new unrealtournament.ini file, and allowed me to actually use XOpenGL again, which looked like the first time i ran it!
But on the SECOND run, i got the same error! Restarting didnt help, checking the log didnt help, then i tried a new approach:
I renamed the ini file, ran UT99 again, then duplicated the ini file it created (without quitting), then played a game, then quit UT99.
I then compared the newly generated ini file with the CLOSED ini file and found the differences. To test to see if the corruption was happening at the ini save part of UT99's exit routine, i checked the differing lines and voila! I found the problem!
The very first line in the [XOpenGLDrv.XOpenGLRenderDevice] category is:
UseBindlessTextures=Trueand this is generated every FIRST run. But when 469d exits, it saves this entry as FALSE, even though it may be set as True in the in-game preferences window. This ends up corrupting the file and every following game start, you get that error message. If you manually change it to True, the game runs fine.
