Enemy Territory OpenGl Error. I need 800x600 mode!!!

(Loafman) #1

I get an error when loading the full version of Enemy Territory. The test worked fine for me. The problem seems to be that the first resolution attemped is Mode 6 which is 1024x768. My resolution is set to 800x600 and that is the max my monitor can go (dont ask).

Is there any way to fix this? Maybe a command line switch or something? What I mean is, can I pass a switch on the command line to skip the intro (is the intro setting the screen to 1024x768)? Maybe I can edit a config file to fix this or something? Here is the part that fails in the error window:

----- R_Init -----
Initializing OpenGL subsystem
…initializing QGL
…calling LoadLibrary( ‘C:\WINDOWS\System32\opengl32.dll’ ): succeeded
…setting mode 6: 1024 768 FS
…using colorsbits of 32
…calling CDS: failed, bad mode
…trying next higher resolution: failed, bad mode
…restoring display settings
…created window@3,22 (1030x800)
Initializing OpenGL driver
…getting DC: succeeded
…GLW_ChoosePFD( 32, 24, 0 )
…39 PFDs found
…hardware acceleration found
…PIXELFORMAT 3 selected
…creating GL context: succeeded
…making context current: succeeded
…WARNING: fullscreen unavailable in this mode
…setting mode 6: 1024 768 FS
…using colorsbits of 16
…calling CDS: failed, bad mode
…trying next higher resolution: failed, bad mode
…restoring display settings
…window already present, CreateWindowEx skipped
Initializing OpenGL driver
…WARNING: fullscreen unavailable in this mode
…shutting down QGL
…unloading OpenGL DLL
…assuming ‘3dfxvgl’ is a standalone driver
…initializing QGL
…WARNING: missing Glide installation, assuming no 3Dfx available
…shutting down QGL
----- CL_Shutdown -----
RE_Shutdown( 1 )

GLW_StartOpenGL() - could not load OpenGL subsystem

(Loafman) #2

Just another update. I attempted to upgrade to the Catalyst 3.4 from 3.2 (I have a radeon all in wonder 8500 128 meg card) and that did not fix the problem.

GLW_StartOpenGL() - could not load OpenGL subsystem

sigh I was really looking forward to this. The test version worked fine for me, so I dont know what is going on. In comparing when the errors occur between test and full version, the error occurs right before (my reference is the working test version on my pc) the spash damage 3…2…1 screen is displayed. Hope that helps.

ugh.

(damocles) #3

I had a similar error when I first installed wolf. It turned out to be my monitor drivers in the end (natch). I was using default windows monitor drivers, installed the official drivers for my monitor and it worked fine. Took me bloody ages to find the problem though

(Loafman) #4

Figured it out. Like I said, my monitor does not exceed 800x600. I have XP and the setting did not allow anything past 800x600 either. Well, I changed XP so that it shows resolutions even if my monitor cant handle them.

Well, ET worked once I did this! It was set to 1024x768 as I suspected. When XP goes to an unsuported res it actually just shows 800x600 res, but everything falls off the screen.