VOGONS


First post, by Sagadali523

User metadata
Rank Newbie
Rank
Newbie

I'm trying to play an old game on a modern system and suddenly I received a error message about OpenGL saying this:

COD 1.3 build win-x86 Mar 2 2004
----- FS_Startup -----
Current language: english
Current search path:
D:\Program Files (x86)\Call of Duty\main\pakb.pk3 (60 files)
D:\Program Files (x86)\Call of Duty\main\paka.pk3 (41 files)
D:\Program Files (x86)\Call of Duty\main\pak9.pk3 (149 files)
D:\Program Files (x86)\Call of Duty\main\pak8.pk3 (235 files)
D:\Program Files (x86)\Call of Duty\main\pak6.pk3 (3 files)
D:\Program Files (x86)\Call of Duty\main\pak5.pk3 (4858 files)
D:\Program Files (x86)\Call of Duty\main\pak4.pk3 (1668 files)
D:\Program Files (x86)\Call of Duty\main\pak3.pk3 (1992 files)
D:\Program Files (x86)\Call of Duty\main\pak2.pk3 (694 files)
D:\Program Files (x86)\Call of Duty\main\pak1.pk3 (2642 files)
D:\Program Files (x86)\Call of Duty\main\pak0.pk3 (12816 files)
D:\Program Files (x86)\Call of Duty/main
D:\Program Files (x86)\Call of Duty\main\localized_english_pak5.pk3 (46 files)
localized assets pak file for english
D:\Program Files (x86)\Call of Duty\main\localized_english_pak3.pk3 (7 files)
localized assets pak file for english
D:\Program Files (x86)\Call of Duty\main\localized_english_pak2.pk3 (9 files)
localized assets pak file for english
D:\Program Files (x86)\Call of Duty\main\localized_english_pak1.pk3 (3736 files)
localized assets pak file for english
D:\Program Files (x86)\Call of Duty\main\localized_english_pak0.pk3 (1204 files)
localized assets pak file for english

File Handles:
----------------------
30160 files in pk3 files
execing default.cfg
couldn't exec language.cfg
execing config.cfg
couldn't exec autoexec.cfg
Hunk_Clear: reset the hunk ok
...detecting CPU, found Intel Pentium III
Measured CPU speed is 2.69 GHz
System memory is 1024 MB (capped at 1 GB)
Video card memory is 4096 MB
Streaming SIMD Extensions (SSE) supported

----- Client Initialization -----
----- Initializing Renderer ----
-------------------------------
----- Client Initialization Complete -----
----- R_Init -----
Initializing OpenGL subsystem
...initializing QGL
...calling LoadLibrary( 'C:\Windows\system32\opengl32.dll' ): succeeded
...setting mode -1: 1080 1920 FS
...using colorbits of 32
...calling CDS: failed, bad mode
...trying next higher resolution: failed, bad mode
...restoring display settings
...registered window class
...created window@3,22 (1086x1949)
Initializing OpenGL driver
...getting DC: succeeded
...GLW_ChoosePFD( 32, 24, 8 )
...219 PFDs found
...hardware acceleration found
...PIXELFORMAT 11 selected
...creating GL context: succeeded
...making context current: succeeded
...WARNING: fullscreen unavailable in this mode
...shutting down QGL
...unloading OpenGL DLL
----- CL_Shutdown -----
RE_Shutdown( 1 )
-----------------------
Hunk_Clear: reset the hunk ok
Could not load OpenGL. Make sure that you have the latest drivers for your video card from the manufacturer's web site.

For some reason, I just had to get a widescreen by going to the game's directory and a folder called "main" so I've entered to edit the config file and that it was the "seta_r mode" caused this problem where I changed the number "4" to "-1", I don't know why that happened. I have followed any video about opengl issues on call of duty and I tried to, but it didn't work - I had to reinstall the game - that didn't work as well. I changed the scale of my display to 125 percent, still it didn't reveal anything until the same error message. The game is a CD I bought it yesterday and my specs are RTX 3050, Intel Core i7 12th gen, and a 16 GB of RAM

I appreciate a lot if you can help me how to deal with this problem

Reply 2 of 7, by BEEN_Nath_58

User metadata
Rank l33t
Rank
l33t

Try setiing mohaa.exe or quake2.exe as the executable name?

previously known as Discrete_BOB_058

Reply 3 of 7, by UCyborg

User metadata
Rank Oldbie
Rank
Oldbie
Sagadali523 wrote on 2025-02-12, 18:45:

...setting mode -1: 1080 1920 FS
...using colorbits of 32
...calling CDS: failed, bad mode

Surely you meant to set resolution to 1920x1080 and not 1080x1920. Flip the values of r_customwidth and r_customheight in config.cfg (config_mp.cfg for multiplayer).

BEEN_Nath_58 wrote on 2025-02-12, 19:52:

Try setiing mohaa.exe or quake2.exe as the executable name?

While I'm probably not qualified to properly judge with my dated hardware and drivers, surely NVIDIA still has OpenGL extension string limitation active by default for CoD?

0hPczFm.png

Or maybe I set it myself and forgot about it, although my NVIDIA Profile Inspector backup of profiles suggests it must already be set by default, along with Profile Inspector's description of selected setting.

Arthur Schopenhauer wrote:

A man can be himself only so long as he is alone; and if he does not love solitude, he will not love freedom; for it is only when he is alone that he is really free.

Reply 4 of 7, by Sagadali523

User metadata
Rank Newbie
Rank
Newbie
UCyborg wrote on 2025-02-12, 20:32:
Sagadali523 wrote on 2025-02-12, 18:45:

...setting mode -1: 1080 1920 FS
...using colorbits of 32
...calling CDS: failed, bad mode

Surely you meant to set resolution to 1920x1080 and not 1080x1920. Flip the values of r_customwidth and r_customheight in config.cfg (config_mp.cfg for multiplayer).

Actually, I already put the 1920x1080 in the config file, not the 1080x1920.

Reply 5 of 7, by UCyborg

User metadata
Rank Oldbie
Rank
Oldbie

So, is it solved now? Because the console messages you posted say you tried to set resolution to 1080x1920, not 1920x1080.

Arthur Schopenhauer wrote:

A man can be himself only so long as he is alone; and if he does not love solitude, he will not love freedom; for it is only when he is alone that he is really free.

Reply 6 of 7, by BEEN_Nath_58

User metadata
Rank l33t
Rank
l33t
UCyborg wrote on 2025-02-12, 20:32:
While I'm probably not qualified to properly judge with my dated hardware and drivers, surely NVIDIA still has OpenGL extension […]
Show full quote

While I'm probably not qualified to properly judge with my dated hardware and drivers, surely NVIDIA still has OpenGL extension string limitation active by default for CoD?

0hPczFm.png

Or maybe I set it myself and forgot about it, although my NVIDIA Profile Inspector backup of profiles suggests it must already be set by default, along with Profile Inspector's description of selected setting.

Logically it should, but sometimes it may fail if there is a check put in place to detect if its the proper codsp.exe/codmp.exe. I mentioned Quake2.exe and mohaa.exe since they also have extension limit but not a check of the executable.

previously known as Discrete_BOB_058

Reply 7 of 7, by leileilol

User metadata
Rank l33t++
Rank
l33t++

Call of Duty came after the Geforce3 which already dealt with the excess extension business. Note that issue only matters for printing the string to Q3's old menu system (fixed in 2001), Q3 never had the issue with it printing to console.

apsosig.png
long live PCem