Send me a PM as a reminder please. When I get home I can send you my Quake benchmark folder with shortcuts for all the resolutions (512 x something up to 1600 x 200).

Just did. Thanks!

Are you accidentally leaving in the opengl32.dll for 3dfx and piping through a Glide wrapper all this time?

Shoot. I put in the specs for my main retro computer. I'll edit the first post in a sec. Here is the system I'm using for Glide:

Win98SE / 466 MHz Celeron / Voodoo 3 AGP / 192MB / SB AWE64 Gold

Still having this problem.

Yeah, don't use the included opengl32.dll with GLQuake with Voodoo3. That's a reaaaaally early MiniGL intended for Voodoo1. Delete it to use the system ICD or you could grab a newer MiniGL that may support the V3's wide amount of resolutions

leileilol wrote:

Yeah, don't use the included opengl32.dll with GLQuake with Voodoo3. That's a reaaaaally early MiniGL intended for Voodoo1. Delete it to use the system ICD or you could grab a newer MiniGL that may support the V3's wide amount of resolutions

That was the problem! I'm glad the solution was so simple. I just renamed opengl.dll to opengl.old.

I'm now running GLQuake at 1600x1200 (16 bpp) with a 30.9 framerate on this modest system. I understand that GLQuake has its critics, but I really like the look of it. I never played it before, so it is like a brand new game to me.

leileilol wrote:

Yeah, don't use the included opengl32.dll with GLQuake with Voodoo3. That's a reaaaaally early MiniGL intended for Voodoo1. Delete it to use the system ICD or you could grab a newer MiniGL that may support the V3's wide amount of resolutions

All the 3dfx MiniGL's are also on VOGONSDrivers 😁
http://www.vogonsdrivers.com/index.php?catid=12

Thanks. I downloaded 1.49 for my V3 (hope that was the right one).

The old MiniGL that would not do higher resolutions is 1.1.

Some more questions:

1. Once I renamed it to opengl.old, I assumed that GLQuake would use the opengl.dll in Windows/System. Is this correct?
2. The version in Windows/System must have come from Quake 2 or another game on my system. It is version 4.0. Is this different from a MiniGL (is it full-blown OpenGL)?
3. Is it always better to use the MiniGL (when available) over the full-blown OpenGL?
4. Will Quake look for opengl.dll in its own directory first before going to Windows/System?

Thanks again to all for the help,

1. Yes.
2. Voodoo3 officially has an OpenGL ICD of its own in Windows/System. It does not come from Quake2 (that's just another MiniGL for V1/V2)
3. There's cases where the MiniGL is faster on slower CPUs due to less overhead than the full ICD as well as specialized optimizations (like those 3dnow! variants for example) however for all intents and purposes it should only be used with id Tech 2 and Goldsrc games. Also it may be handy that some MiniGLs force the gamma correction level up to 1.7 as the games they are for don't have proper functioning brightness controls.
4. Yes. This is general behavior of many games in fact. It's rare to find one that doesn't (like MDK2)

Hello all,
I am having issue with changing the resolution, while using the GLQuake (v. 0.95). I am using a Creative Labs Monster 3DII Voodoo2 card with the default drivers.

When trying to change the resolution, the game says:
Video Modes must be set from the command line with -width (width) and -bpp (pits-per-pixel)

When I add these lines to my PIF shortcut icon: -width 800 height 600 -32, I get an "Illegal Operation" error message: GlQuake caused a stack fault in module GLQAUKE.EXE at 017f:0043634d.

Please help!

PIII-800E
768 SD-133
Abit BH-6 Mobo

You need to add the - before height and -bpp before the color depth.

Also, a Voodoo 2 can't do 32-bit color in 3D games, so you'll need to use 16-bit.

-width 800 -height 600 -bpp 16

also don't make .pif files for windows games. PIFs are for launching DOS stuff with more parameters for memory, etc

Update

I just patched the game to GLQuake v.097, and the command line work properly!

(although I still love the pixallated (and un-washed out color theme) of the vanilla version!)

Question:
Is there anyway to make the mouselook *automatic* (ie.: like modern FPS games, that it is on by default), as with the latest v.1.09 WinQuake (original CD) running on my Win98SE PIII system, I have to press the mouse wheel in order to *activate* mouselook option.

Thanks!

Edit:
Found the answer!

https://steamcommunity.com/sharedfiles/filede … s/?id=118773632

I suggest to set in id1/autoexec.cfg
+mlook
v_centermove 10
sv_aim 1

v_centermove = avoids auto-centering when moving forward/backward
sv_aim 1 = no auto-aim help

Hello...

It's a little bit old topic.. but I encounter similar problems with glquake. The -width -height and -bpp command line only makes it until 1024x768x32... The max res is 1600x1200. It is also shown in the options menu in quake. But every time I try this I get an error. It says: could not initialize GL. wglCreateContext failed.
I have the newest glquake 0.97 and I believe a new minigl (1.49). I am using nglide 2.10 with a Firegl X3.

Edit:
In the meantime I tried a 9800xt... But that was almost as bad.. so back to the x3... from what I can see, image quality improves when I set a certain resolution in nglide configuration. But the hud doesn't seem to change with another res... I have less experiences with glquake - does it have to be that way?

PhilsComputerLab wrote on 2015-06-10, 05:07:

Send me a PM as a reminder please. When I get home I can send you my Quake benchmark folder with shortcuts for all the resolutions (512 x something up to 1600 x 200).

Can you make it public download or can you dm me?
thanks
p.s. kudos for making that dos menu 😉

Closed.
Open your own thread for your own issue.
Phil doesn't visit vogons anymore