[Driver issue]Can't switch to GL mode

Post by **Graf Zahl** » Sat Sep 03, 2005 14:03

Ok. I just uploaded a test version. Please tell me what it does and even if it is working post its console startup log.

Get it here: http://grafzahl.drdteam.org/gzdoom/nmtest.zip

NiGHTMARE · Post by **NiGHTMARE** » Sat Sep 03, 2005 14:47

Unfortunately, the log is the same as before, except for the addition of "ZGL: OpenGL driver not accelerated! Retrying in compatibility mode".

I'm going to try to find and install Catalyst 5.7, and see what happens...

Post by **Graf Zahl** » Sat Sep 03, 2005 15:14

Could you please still post the console log? I added some status output code and I'd like to see what exactly it printed.

NiGHTMARE · Post by **NiGHTMARE** » Sat Sep 03, 2005 16:08

Log started: Sat Sep 03 16:07:39 2005

adding zdoom.wad (140 lumps)
adding ./doom2.wad (2919 lumps)
CPU Speed: 2412.069951 MHz
CPU Vendor ID: AuthenticAMD
Name: AMD Athlon(tm) 64 Processor 3400+
Family 15 (15), Model 12, Stepping 0
Features: MMX MMX+ SSE SSE2 3DNow! 3DNow!+
I_InitSound: Initializing FMOD
Setting DirectSound output succeeded
Setting driver 0 succeeded
Initialization succeeded
GL_VENDOR: Microsoft Corporation
GL_RENDERER: GDI Generic
GL_VERSION: 1.1.0
GL_EXTENSIONS: GL_WIN_swap_hint GL_EXT_bgra GL_EXT_paletted_texture
ZGL: OpenGL driver not accelerated! Retrying in compatibility mode
ZGL: OpenGL driver not accelerated! Falling back to software renderer.
ZGL: Reverting to software mode...
Resolution: 1600 x 1200
Init DOOM refresh subsystem.
2660 textures created
Init miscellaneous info.
Init Playloop state.
Setting up sound.
S_Init
Checking network game status.
player 1 of 1 (1 nodes)
GL_VENDOR: Microsoft Corporation
GL_RENDERER: GDI Generic
GL_VERSION: 1.1.0
GL_EXTENSIONS: GL_WIN_swap_hint GL_EXT_bgra GL_EXT_paletted_texture
ZGL: OpenGL driver not accelerated! Retrying in compatibility mode
Switching to software renderer...
ZGL: OpenGL driver not accelerated! Falling back to software renderer.
ZGL: Reverting to software mode...
Switching to software renderer...

No luck with the 5.7 drivers.

Post by **Graf Zahl** » Sat Sep 03, 2005 16:53

Something's not right at all there. You don't even get an accelerated context upon first launch - and that one asks for pretty generic features every graphics card should support.

One last question. Do you run your desktop in 16 bit or 32 bit?

NiGHTMARE · Post by **NiGHTMARE** » Sat Sep 03, 2005 17:13

32 bit.

NiGHTMARE · Post by **NiGHTMARE** » Tue Dec 27, 2005 5:08

The old Radeon 9700 has now been replaced by a Radeon X850XT PE, and guess what? I've still got exactly the same problem!

Could the cause actually be something other than the graphics card (hardware or drivers)? That would certainly explain the problem's persistence, since the only other major change to my system is a new motherboard (neccessary as the old card was AGP, and the new one is PCI-Express).

A couple of ideas spring to mind:

1) I've no idea how or why, but could GZDoom somehow be trying to use the built-in 3D graphics capability of the motherboards, rather than the graphic card? Both motherboards have extremely crappy 3D graphics processors, so I can imagine GZDoom wouldn't especially like them.

2) Maybe the issue lies with the operating system, Windows 2000 SP4. This can easily be ruled out if anyone else is using this OS and is running GZDoom in GL without issue.

3) Could it be something to do with the monitor? For reference, I have an Iiyama 22" Vision Master Pro (not sure of the exact model number, but I could probably look it up).

Post by **wildweasel** » Tue Dec 27, 2005 5:32

Can you disable the on-board video on your motherboard through the BIOS?

NiGHTMARE · Post by **NiGHTMARE** » Tue Dec 27, 2005 5:51

Already have done. However, I also disabled the on-board sound, but that didn't stop Windows from recognizing it was there

.

Deathlike2 · Post by **Deathlike2** » Tue Dec 27, 2005 8:00

This sounds like you are having problems installing your video card driver. Please try to follow the following steps:

1) Download and run ATI's uninstaller (downloadable from ATI's website).
2) Download the install the latest ATI drivers (5.13 is out and working fine for me)
3) Install the mobo drivers (probably not necessary for PCI-Express video cards, but definately important for AGP video cards)

Could the cause actually be something other than the graphics card (hardware or drivers)? That would certainly explain the problem's persistence, since the only other major change to my system is a new motherboard (neccessary as the old card was AGP, and the new one is PCI-Express).

It is clearly the drivers (bad installation) because it is not able to detect the OpenGL client driver...

If you have changed mobos, it is best you reinstall Windows... most of the time, shit happens when you don't.

1) I've no idea how or why, but could GZDoom somehow be trying to use the built-in 3D graphics capability of the motherboards, rather than the graphic card? Both motherboards have extremely crappy 3D graphics processors, so I can imagine GZDoom wouldn't especially like them.

2) Maybe the issue lies with the operating system, Windows 2000 SP4. This can easily be ruled out if anyone else is using this OS and is running GZDoom in GL without issue.

3) Could it be something to do with the monitor? For reference, I have an Iiyama 22" Vision Master Pro (not sure of the exact model number, but I could probably look it up).

1) Mmm.. no.. it uses the OpenGL client driver as found by the system.. and if it cannot find it, it uses the crappy Windows one that basically does nothing.

2) It is more likely to lie with your installation of the driver. But, it is more a problem with the OS ONLY because you changed your mobo. I'm running Win2K w/SP4 installed and have these problems with GZDoom.

3) The monitor is really a non-factor in any of this.

Example of what my 9800 Pro shows as a logfile:

Log started: Tue Dec 27 02:03:40 2005

adding gzdoom.pk3
adding ./doom2.wad (2919 lumps)
CPU Speed: 1001.282579 MHz
CPU Vendor ID: AuthenticAMD
Name: AMD Athlon(tm) 64 Processor 3200+
Family 15 (15), Model 4, Stepping 10
Features: MMX MMX+ SSE SSE2 3DNow! 3DNow!+
I_InitSound: Initializing FMOD
Setting DirectSound output succeeded
Setting driver 0 succeeded
Initialization succeeded
GL_VENDOR: ATI Technologies Inc.
GL_RENDERER: RADEON 9800 Pro x86/MMX/3DNow!/SSE2
GL_VERSION: 2.0.5525 Win2000 Release
GL_EXTENSIONS: GL_ARB_multitexture GL_EXT_texture_env_add GL_EXT_compiled_vertex_array GL_S3_s3tc GL_ARB_depth_texture GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_multisample GL_ARB_occlusion_query GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_shader_objects GL_ARB_shading_language_100 GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_mirrored_repeat GL_ARB_transpose_matrix GL_ARB_vertex_blend GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_ARB_draw_buffers GL_ATI_draw_buffers GL_ATI_element_array GL_ATI_envmap_bumpmap GL_ATI_fragment_shader GL_ATI_map_object_buffer GL_ATI_separate_stencil GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_ATI_texture_mirror_once GL_ATI_vertex_array_object GL_ATI_vertex_attrib_array_object GL_ATI_vertex_streams GL_ATIX_texture_env_combine3 GL_ATIX_texture_env_route GL_ATIX_vertex_shader_output_point_size GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_clip_volume_hint GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_object GL_EXT_multi_draw_arrays GL_EXT_packed_pixels GL_EXT_point_parameters GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_EXT_texgen_reflection GL_EXT_texture3D GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_rectangle GL_EXT_vertex_array GL_EXT_vertex_shader GL_HP_occlusion_test GL_NV_blend_square GL_NV_occlusion_query GL_NV_texgen_reflection GL_SGI_color_matrix GL_SGIS_generate_mipmap GL_SGIS_multitexture GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_SUN_multi_draw_arrays GL_WIN_swap_hint WGL_EXT_extensions_string WGL_EXT_swap_control
Occlusion query enabled.
Init Shaders: Link successful. The GLSL vertex shader will run in hardware. The GLSL fragment shader will run in hardware.
Resolution: 1280 x 1024
Init DOOM refresh subsystem.

Note: In your previous logfiles, it says "Microsoft Corporation" which shows that you have not installed your drivers properly. If your other OpenGL games are running poorly/crappy, it is simply because of this fact.

NiGHTMARE · Post by **NiGHTMARE** » Tue Dec 27, 2005 16:18

I did re-install Windows (neccessary for it to put on the new hard drive controller driver, amongst other things).

With the old card, I tried five different drivers for it, including a couple of versions of the unofficial Omega drivers (and yes, I did use the ATI uninstall utility). Since all you basically need to do to install a driver is run the .exe, tell it where to install, and then just let it get on with it, I don't see how they could not have been installed "properly". There's also the fact that something like five dozen other 3D games (including GL Quake) worked and still work absolutely fine; it's only GZDoom which is refusing to work in GL mode.

Deathlike2 · Post by **Deathlike2** » Tue Dec 27, 2005 16:28

Well, I still think you are doing something wrong as I'm not affected at all. Alternatively, you could try finding the OpenGL .dll (atioglxx.dll) and copying it to the GZDoom directory (I'm not sure if you need to rename the dll file to OpenGL32.dll). I presume most, if not all OpenGL programs check for the OpenGL client file in the same folder as the executable and attempt to use it.

Post by **Graf Zahl** » Tue Dec 27, 2005 16:38

Deathlike2 wrote: Alternatively, you could try finding the OpenGL .dll (atioglxx.dll) and copying it to the GZDoom directory (I'm not sure if you need to rename the dll file to OpenGL32.dll). I presume most, if not all OpenGL programs check for the OpenGL client file in the same folder as the executable and attempt to use it.

Never, ever do that! There is no better method to screw up an application's behavior more thoroughly. The ATIOGLXX.DLL is the GL ICD which is not the same as OpenGL.DLL, OPenGL.DLL uses this DLL and they are not interchangeable.

NiGHTMARE · Post by **NiGHTMARE** » Tue Dec 27, 2005 16:40

Interesting you say that Graf, because there was already an OpenGL32.dll in the GZDoom directory, and so what you just said is most likely exactly the cause of the problem with the X850: . D'oh!

The file was probably a left over from when I was trying to get the 9700 to work, I remember trying all sorts of things

. But anyway, deleting it seems to have solved the problem. Hooray!

EDIT: in fact, the OpenGL32.dll file dates from the beginning of 2004, so most likely it was the cause of the 9700 not working, too. I'm guessing it came from either JDoom or ZDoomGL.

Deathlike2 · Post by **Deathlike2** » Tue Dec 27, 2005 16:52

Graf Zahl wrote:Never, ever do that! There is no better method to screw up an application's behavior more thoroughly. The ATIOGLXX.DLL is the GL ICD which is not the same as OpenGL.DLL, OPenGL.DLL uses this DLL and they are not interchangeable.

Well, that's how it has worked in other OpenGL apps... but if it works that much differently in GZDoom.. go figure (it wasn't obvious to me)

NiGHTMARE wrote:I think this was probably a left over from when I was trying to get the previous card to work. But anyway, deleting it seems to have solved the problem. Hooray!

A thought.. I didn't think too much about a "clean install" of GZDoom... but sometimes these are the kinds of things that need to be done to isolate a problem. An old/stray file could affect how a program works at times... I mean.. I didn't notice during a new revision of GZDoom that there was a gzdoom.wad file and a gzdoom.pk3 file in the GZDoom directory... (I got rid of the .wad file and fortunately nothing screwy happened with GZDoom when both were in the GZDoom directory)