Jump to content
The Dark Mod Forums

Open GL Problem


LEGION

Recommended Posts

Hi everyone,

 

i just installed Doom3 with the latest patch 1.3.1 and wanted to run it (I´ve not yet installed the darkmod) and the starting console tells me this:

 

 

----------------------------------------- ---------------------

 

--------------------------------------

----- R_InitOpenGL -----

Initializing OpenGL subsystem

...registered window class

...registered fake window class

...initializing QGL

...calling LoadLibrary( 'opengl32' ): succeeded

...calling CDS: ok

...created window @ 0,0 (640x480)

Initializing OpenGL driver

...getting DC: succeeded

...PIXELFORMAT 10 selected

...creating GL context: succeeded

...making context current: succeeded

 

------- Input Initialization -------

Initializing DirectInput...

mouse: DirectInput initialized.

keyboard: DirectInput initialized.

------------------------------------

sound: STEREO

X..GL_ARB_multitexture not found

X..GL_ARB_texture_env_combine not found

X..GL_ARB_texture_cube_map not found

X..GL_ARB_texture_env_dot3 not found

X..GL_ARB_texture_env_add not found

X..GL_ARB_texture_non_power_of_two not found

X..GL_ARB_texture_compression not found

X..GL_EXT_texture_filter_anisotropic not found

...using GL_1.4_texture_lod_bias

X..GL_EXT_shared_texture_palette not found

X..GL_EXT_texture3D not found

X..GL_EXT_stencil_wrap not found

X..GL_NV_register_combiners not found

X..GL_EXT_stencil_two_side not found

X..GL_ATI_separate_stencil not found

X..GL_ATI_fragment_shader not found

X..GL_ATI_text_fragment_shader not found

X..GL_ARB_vertex_buffer_object not found

X..GL_ARB_vertex_program not found

X..GL_ARB_fragment_program not found

********************

ERROR: The current video card / driver combination does not support the necessary features.

********************

Error during initialization

Shutting down OpenGL subsystem

...wglMakeCurrent( NULL, NULL ): success

...deleting GL context: success

...releasing DC: success

...destroying window

...resetting display

...shutting down QGL

...unloading OpenGL DLL

----------------------------------------- ----------------------------------------- - --

 

 

This is not the complete console text, but I think the important one.

 

My graphics card is: Nvidia Geforce 9800 GT with the latest drivers (GeForce/ION Driver Release 197) released 2010.03.25

 

I can´t believe my card doesn´t can handle Doom3!? So what´s to do here?

Maybe some third party OpenGL drivers?

 

I have to add that this is a new system and I only played the first two Thief´s and the game "ShadowMan" and they all worked just fine.

 

Please help me and don´t say my Geforce is not a good card!!!

 

best regards,

 

LEGION

-> Crisis of Capitalism

-> 9/11 Truth

->

(hard stuff), more
Link to comment
Share on other sites

Have you tried downgrading your drivers? I had a problem with OpenGL (albeit in another, older game) after using the latest nVidia drivers. Downloading earlier drivers (can't remember the version, but they were dated August last year I believe) fixed the issue I was having.

Link to comment
Share on other sites

The very latest drivers are not always the "best". One example for that is the official NVidia Drivers that caused people's graphics-cards to overheat in droves.

 

I usually ( when thinking about updating the drivers ) read the forums on guru3d.com to see whether a more recent driver is getting good "reviews" there, or if it makes problems.

Link to comment
Share on other sites

GeForce/ION Driver Release 197 released 2010.03.25

try two things -

 

1. completely uninstall the gfx driver and reboot, then reinstall the driver - see how you go

2. if that dont work, then do as the others have said and pick an older driver - I suggest the 195 series.

Link to comment
Share on other sites

Also make sure that you do driver uninstalling "properly".

 

Meaning uninstall them, then reboot into safe-mode to use something like Driver-Sweeper to get rid of the remaining files, then boot again normally to do the installation of the new driver.

Link to comment
Share on other sites

Also make sure that you do driver uninstalling "properly".

 

Meaning uninstall them, then reboot into safe-mode to use something like Driver-Sweeper to get rid of the remaining files, then boot again normally to do the installation of the new driver.

 

Ok, I have Driver Sweeper and the 195 driver version, but I don´t know how to "uninstall" the actual driver!? It´s not in my Software-List.

 

And, I just run the Sweeper and it shows me "ATI-Display" files! I never had an ATI on this system and can´t remember downloading drivers. Is this an emulating thing from Nvidia or is there something wrong?

 

Thanks for help.

-> Crisis of Capitalism

-> 9/11 Truth

->

(hard stuff), more
Link to comment
Share on other sites

Strange, normally the driver should be in the software-list called "NVidia Drivers" or similar. At least it shows up there in Windows 2000/XP.

 

The first Screen in Driver Sweeper just shows you a list of options, the ATI Drivers happen to be on top of the list.

 

After you uninstalled the driver and are in safe-mode, you can check the "NVidia Display" checkbox here, then click on "Analyse" and after it's done on "Clean".

Link to comment
Share on other sites

Ok, THANK YOU VERY MUCH!!!

 

It´s working now!!

 

You´re right, there is "Nvidia Driver" in the Software List, but it´s so little, I thought it´s the wrong thing. I used the Device Manager for uninstall...

 

But I don´t understand this ATI thing, there are several files, and they´re still on the list after I "cleaned" them!?

 

But the main thing is, DOOM 3 is running now!

 

Thanks for helping me out!!

-> Crisis of Capitalism

-> 9/11 Truth

->

(hard stuff), more
Link to comment
Share on other sites

  • 8 months later...

Can you copy more of your console error?

 

Also, is the screen you are trying to play from designated as your Primary display?

 

(I would try the 195 WHQL version tried in this thread if you haven't already.)

 

Finally, this may sound strange but some Spyware has been know to hook into the Device Manager registry keys (the symptom is usually a blank white page when opening the Device Manager), you could try running Super Antispyware or some other anti malware then running the driver cleaner then reinstalling the drivers.

 

If it were my system, I would also download the latest BIOS from ASUS in case the card isn't being properly detected but upgrading your BIOS is risky so I will let you make that call.

Please visit TDM's IndieDB site and help promote the mod:

 

http://www.indiedb.com/mods/the-dark-mod

 

(Yeah, shameless promotion... but traffic is traffic folks...)

Link to comment
Share on other sites

Can you copy more of your console error?

 

Also, is the screen you are trying to play from designated as your Primary display?

 

(I would try the 195 WHQL version tried in this thread if you haven't already.)

 

Finally, this may sound strange but some Spyware has been know to hook into the Device Manager registry keys (the symptom is usually a blank white page when opening the Device Manager), you could try running Super Antispyware or some other anti malware then running the driver cleaner then reinstalling the drivers.

 

If it were my system, I would also download the latest BIOS from ASUS in case the card isn't being properly detected but upgrading your BIOS is risky so I will let you make that call.

 

here you go

 

DOOM 1.3.1.1304 win-x86 Jan 16 2007 15:36:51

2137 MHz Intel CPU with MMX & SSE & SSE2 & SSE3 & HTT

3072 MB System Memory

512 MB Video Memory

Winsock Initialized

Found interface: {C6EC722A-ECCE-4323-AA81-BD04BBD41267} Marvell Yukon 88E8053 PCI-E Gigabit Ethernet Controller #2 - Miniport d'ordonnancement de paquets - 0.0.0.0 NULL netmask - skipped

Found interface: {C7158351-7315-4709-A594-5272A2895950} Marvell Yukon 88E8053 PCI-E Gigabit Ethernet Controller - Miniport d'ordonnancement de paquets - 192.168.0.199/255.255.255.0

Sys_InitNetworking: adding loopback interface

doom using MMX & SSE & SSE2 & SSE3 for SIMD processing

enabled Flush-To-Zero mode

enabled Denormals-Are-Zero mode

------ Initializing File System ------

Loaded pk4 d:\program files\steam\steamapps\common\doom 3\base\game00.pk4 with checksum 0x29cdb978

Loaded pk4 d:\program files\steam\steamapps\common\doom 3\base\game01.pk4 with checksum 0x51c6981f

Loaded pk4 d:\program files\steam\steamapps\common\doom 3\base\game02.pk4 with checksum 0xf3ec6f7

Loaded pk4 d:\program files\steam\steamapps\common\doom 3\base\game03.pk4 with checksum 0x5d4230ea

Loaded pk4 d:\program files\steam\steamapps\common\doom 3\base\pak000.pk4 with checksum 0x28d208f1

Loaded pk4 d:\program files\steam\steamapps\common\doom 3\base\pak001.pk4 with checksum 0x40244be0

Loaded pk4 d:\program files\steam\steamapps\common\doom 3\base\pak002.pk4 with checksum 0xc51ecdcd

Loaded pk4 d:\program files\steam\steamapps\common\doom 3\base\pak003.pk4 with checksum 0xcd79d028

Loaded pk4 d:\program files\steam\steamapps\common\doom 3\base\pak004.pk4 with checksum 0x765e4f8b

Loaded pk4 d:\program files\steam\steamapps\common\doom 3\base\pak005.pk4 with checksum 0x8ffc3621

Loaded pk4 d:\program files\steam\steamapps\common\doom 3\base\pak006.pk4 with checksum 0x95b65ab

Loaded pk4 d:\program files\steam\steamapps\common\doom 3\base\pak007.pk4 with checksum 0x666bdb3c

Loaded pk4 d:\program files\steam\steamapps\common\doom 3\base\pak008.pk4 with checksum 0x23ae5993

Current search path:

d:\program files\steam\steamapps\common\doom 3/base

d:\program files\steam\steamapps\common\doom 3\base\pak008.pk4 (3 files)

d:\program files\steam\steamapps\common\doom 3\base\pak007.pk4 (38 files)

d:\program files\steam\steamapps\common\doom 3\base\pak006.pk4 (48 files)

d:\program files\steam\steamapps\common\doom 3\base\pak005.pk4 (63 files)

d:\program files\steam\steamapps\common\doom 3\base\pak004.pk4 (5137 files)

d:\program files\steam\steamapps\common\doom 3\base\pak003.pk4 (4676 files)

d:\program files\steam\steamapps\common\doom 3\base\pak002.pk4 (6120 files)

d:\program files\steam\steamapps\common\doom 3\base\pak001.pk4 (8972 files)

d:\program files\steam\steamapps\common\doom 3\base\pak000.pk4 (2698 files)

d:\program files\steam\steamapps\common\doom 3\base\game03.pk4 (2 files)

d:\program files\steam\steamapps\common\doom 3\base\game02.pk4 (2 files)

d:\program files\steam\steamapps\common\doom 3\base\game01.pk4 (2 files)

d:\program files\steam\steamapps\common\doom 3\base\game00.pk4 (2 files)

game DLL: 0x0 in pak: 0x0

Addon pk4s:

file system initialized.

--------------------------------------

----- Initializing Decls -----

------------------------------

------- Initializing renderSystem --------

using ARB renderSystem

renderSystem initialized.

--------------------------------------

5206 strings read from strings/english.lang

Couldn't open journal files

execing editor.cfg

execing default.cfg

execing DoomConfig.cfg

couldn't exec autoexec.cfg

5206 strings read from strings/english.lang

----- Initializing Sound System ------

sound system initialized.

--------------------------------------

----- R_InitOpenGL -----

Initializing OpenGL subsystem

...registered window class

...registered fake window class

...initializing QGL

...calling LoadLibrary( 'opengl32' ): succeeded

Couldn't find proc address for: wglGetExtensionsStringARB

Couldn't find proc address for: wglSwapIntervalEXT

Couldn't find proc address for: wglGetPixelFormatAttribivARB

Couldn't find proc address for: wglGetPixelFormatAttribfvARB

Couldn't find proc address for: wglChoosePixelFormatARB

Couldn't find proc address for: wglCreatePbufferARB

Couldn't find proc address for: wglGetPbufferDCARB

Couldn't find proc address for: wglReleasePbufferDCARB

Couldn't find proc address for: wglDestroyPbufferARB

Couldn't find proc address for: wglQueryPbufferARB

Couldn't find proc address for: wglBindTexImageARB

Couldn't find proc address for: wglReleaseTexImageARB

Couldn't find proc address for: wglSetPbufferAttribARB

...calling CDS: ok

...created window @ 0,0 (640x480)

Initializing OpenGL driver

...getting DC: succeeded

...PIXELFORMAT 7 selected

...creating GL context: succeeded

...making context current: succeeded

Couldn't find proc address for: wglGetExtensionsStringARB

Couldn't find proc address for: wglSwapIntervalEXT

Couldn't find proc address for: wglGetPixelFormatAttribivARB

Couldn't find proc address for: wglGetPixelFormatAttribfvARB

Couldn't find proc address for: wglChoosePixelFormatARB

Couldn't find proc address for: wglCreatePbufferARB

Couldn't find proc address for: wglGetPbufferDCARB

Couldn't find proc address for: wglReleasePbufferDCARB

Couldn't find proc address for: wglDestroyPbufferARB

Couldn't find proc address for: wglQueryPbufferARB

Couldn't find proc address for: wglBindTexImageARB

Couldn't find proc address for: wglReleaseTexImageARB

Couldn't find proc address for: wglSetPbufferAttribARB

 

------- Input Initialization -------

Initializing DirectInput...

mouse: DirectInput initialized.

keyboard: DirectInput initialized.

------------------------------------

sound: STEREO

X..GL_ARB_multitexture not found

X..GL_ARB_texture_env_combine not found

X..GL_ARB_texture_cube_map not found

X..GL_ARB_texture_env_dot3 not found

X..GL_ARB_texture_env_add not found

X..GL_ARB_texture_non_power_of_two not found

X..GL_ARB_texture_compression not found

X..GL_EXT_texture_filter_anisotropic not found

X..GL_EXT_texture_lod not found

X..GL_1.4_texture_lod_bias not found

X..GL_EXT_shared_texture_palette not found

X..GL_EXT_texture3D not found

X..GL_EXT_stencil_wrap not found

X..GL_NV_register_combiners not found

X..GL_EXT_stencil_two_side not found

X..GL_ATI_separate_stencil not found

X..GL_ATI_fragment_shader not found

X..GL_ATI_text_fragment_shader not found

X..GL_ARB_vertex_buffer_object not found

X..GL_ARB_vertex_program not found

X..GL_ARB_fragment_program not found

********************

ERROR: The current video card / driver combination does not support the necessary features.

********************

Error during initialization

Shutting down OpenGL subsystem

...wglMakeCurrent( NULL, NULL ): success

...deleting GL context: success

...releasing DC: success

...destroying window

...resetting display

...shutting down QGL

...unloading OpenGL DLL

 

I will try the driver sweeper without the spybot running

yes it is my primary dsplay

i usually work my way around those problem but this one gets me !!

Edited by PatLess
Link to comment
Share on other sites

Make sure Spybot's "Tea Timer" is not protecting either the Windows\System32 directory or the opengl32.dll. I believe a vendor version replaces this one.

 

Try placing NVOGLNT.DLL in your Doom 3 install directory as a workaround.

Edited by nbohr1more

Please visit TDM's IndieDB site and help promote the mod:

 

http://www.indiedb.com/mods/the-dark-mod

 

(Yeah, shameless promotion... but traffic is traffic folks...)

Link to comment
Share on other sites

Make sure Spybot's "Tea Timer" is not protecting either the Windows\System32 directory or the opengl32.dll. I believe a vendor version replaces this one.

 

Try placing NVOGLNT.DLL in your Doom 3 install directory as a workaround.

 

 

i will try that file in the main directory

 

When i use driver sweeper in safe mode the Spybot isn't running could it be still active even if i don't see the process ?

Link to comment
Share on other sites

Windows has a habit of leaving processes alive after their Service has been shut-down so anything's possible... You might see an SDbot or TeaTimer process in Task Manager that you can kill... :unsure:

 

Edit:

 

Oh I see a problem. If you have Spybot set to auto-start with Windows any changes you make to protected areas in Safemode will be regressed by Spybot when Windows starts in Normal mode. It may be best to temporarily uninstall Spybot if you can't disable the file/registry/directory change protections...

Edited by nbohr1more

Please visit TDM's IndieDB site and help promote the mod:

 

http://www.indiedb.com/mods/the-dark-mod

 

(Yeah, shameless promotion... but traffic is traffic folks...)

Link to comment
Share on other sites

Windows has a habit of leaving processes alive after their Service has been shut-down so anything's possible... You might see an SDbot or TeaTimer process in Task Manager that you can kill... unsure.gif

 

yes there are process you can kill but not in safe mode , so i guess its not running in safe mode

but i killed it in normal boot to re-install the driver or should i install the drivers in safe mode too ?

Link to comment
Share on other sites

Kill Spybot in Normal mode and Install the drivers in Normal Mode. XP SP3 is terrible at driver installs in Safemode. They added something called the "Windows Installer Service" and pretty-much destroyed the utility of Safemode.

 

(It was a horrible decision and I think they did it so XP would be a little worse so folks would jump to Vista or Win7...)

Please visit TDM's IndieDB site and help promote the mod:

 

http://www.indiedb.com/mods/the-dark-mod

 

(Yeah, shameless promotion... but traffic is traffic folks...)

Link to comment
Share on other sites

yes there are process you can kill but not in safe mode , so i guess its not running in safe mode

but i killed it in normal boot to re-install the driver or should i install the drivers in safe mode too ?

 

 

i've been a fan of thief since the dark project i really wanna play this ...

i don't even care for doom

Link to comment
Share on other sites

i've been a fan of thief since the dark project i really wanna play this ...

i don't even care for doom

 

I'd say that is the opinion of a good number of folks here. ^_^

Please visit TDM's IndieDB site and help promote the mod:

 

http://www.indiedb.com/mods/the-dark-mod

 

(Yeah, shameless promotion... but traffic is traffic folks...)

Link to comment
Share on other sites

Windows has a habit of leaving processes alive after their Service has been shut-down so anything's possible... You might see an SDbot or TeaTimer process in Task Manager that you can kill... unsure.gif

 

Edit:

 

Oh I see a problem. If you have Spybot set to auto-start with Windows any changes you make to protected areas in Safemode will be regressed by Spybot when Windows starts in Normal mode. It may be best to temporarily uninstall Spybot if you can't disable the file/registry/directory change protections...

 

i uninstalled spybot

it still doesn't work i really don't know what to try next ... i always get the same errors

Link to comment
Share on other sites

Sounds like the Motherboard might have onboard ATI graphics?

 

If your monitor cable connected directly to the Video Card instead of a port built into the Motherboard?

 

Yes, the original drivers might have the correct INF data if the generic nVidia drivers don't... That is a valid option.

Please visit TDM's IndieDB site and help promote the mod:

 

http://www.indiedb.com/mods/the-dark-mod

 

(Yeah, shameless promotion... but traffic is traffic folks...)

Link to comment
Share on other sites

Sounds like the Motherboard might have onboard ATI graphics?

 

If your monitor cable connected directly to the Video Card instead of a port built into the Motherboard?

 

Yes, the original drivers might have the correct INF data if the generic nVidia drivers don't... That is a valid option.

 

 

well it has ATI cross fire multi gpu feature but i only have one card installed

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recent Status Updates

    • Petike the Taffer  »  DeTeEff

      I've updated the articles for your FMs and your author category at the wiki. Your newer nickname (DeTeEff) now comes first, and the one in parentheses is your older nickname (Fieldmedic). Just to avoid confusing people who played your FMs years ago and remember your older nickname. I've added a wiki article for your latest FM, Who Watches the Watcher?, as part of my current updating efforts. Unless I overlooked something, you have five different FMs so far.
      · 0 replies
    • Petike the Taffer

      I've finally managed to log in to The Dark Mod Wiki. I'm back in the saddle and before the holidays start in full, I'll be adding a few new FM articles and doing other updates. Written in Stone is already done.
      · 4 replies
    • nbohr1more

      TDM 15th Anniversary Contest is now active! Please declare your participation: https://forums.thedarkmod.com/index.php?/topic/22413-the-dark-mod-15th-anniversary-contest-entry-thread/
       
      · 0 replies
    • JackFarmer

      @TheUnbeholden
      You cannot receive PMs. Could you please be so kind and check your mailbox if it is full (or maybe you switched off the function)?
      · 1 reply
    • OrbWeaver

      I like the new frob highlight but it would nice if it was less "flickery" while moving over objects (especially barred metal doors).
      · 4 replies
×
×
  • Create New...