1. +mlook in autoexec.cfg. make this file in id1
2. cfg doesn't define the resolution. Follow the instructions in video options and set -width and -height in the shortcut.
3. Multitexturing and less flipped sprite problems.
Also as you're using an nvidia (shudder) you'll want to add -dibonly to any WinQuake shortcut you use, otherwise it's performance/stability issues ahead

Going by your questions, I take it you might not very experienced with the Quake engine, or at least earlier versions of it. Are you aware that GLQuake has some issues/differences wrt lighting ("overbrights")? Read about it here. Later maps/mods started being made with GLQuake's lighting in mind, but the original game wasn't - so if it's your first time playing through that, you might want to revert back to a non-GL version for a better experience, since that's the one the maps were lit for/look best in.

There seems to be thread redundancy....
Quake 1 on newer Windows 9x PC with 3D card

leileilol wrote on 2025-11-26, 02:19:

1. +mlook in autoexec.cfg. make this file in id1 2. cfg doesn't define the resolution. Follow the instructions in video options […]
Show full quote

1. +mlook in autoexec.cfg. make this file in id1
2. cfg doesn't define the resolution. Follow the instructions in video options and set -width and -height in the shortcut.
3. Multitexturing and less flipped sprite problems.
Also as you're using an nvidia (shudder) you'll want to add -dibonly to any WinQuake shortcut you use, otherwise it's performance/stability issues ahead

I will try those suggestions. I'm not using WinQuake.exe, it has a bug with Nvidia card. Maybe you meant to create a shortcut based on WinQuake.exe with -dibonly key?

elszgensa wrote on 2025-11-26, 04:07:

Going by your questions, I take it you might not very experienced with the Quake engine, or at least earlier versions of it. Are you aware that GLQuake has some issues/differences wrt lighting ("overbrights")? Read about it here. Later maps/mods started being made with GLQuake's lighting in mind, but the original game wasn't - so if it's your first time playing through that, you might want to revert back to a non-GL version for a better experience, since that's the one the maps were lit for/look best in.

Yes, I never played Q1, my first ever Quake game was Q2. With this PC I built based on Nvidia the WinQuake has issues with freezing/black screen. Only two modes worked for me so far: GLQuake and software render. So, my choice is GLQuake as it uses GPU and relatively trouble-free. Software render is low-res and too much FPS. So for purists original Quake is a must but for me I just want to play on relatively period correct hardware.

leileilol wrote on 2025-11-26, 04:38:

There seems to be thread redundancy....
Quake 1 on newer Windows 9x PC with 3D card

Not quite. I was asking if it was possible to play on newer hardware like mine. I just got the disks few months back and have some spare time during the holidays .

well... i still have the quake folder from 90s 😁 , always used glquake because 3dfx voodoo
i think you can adjust resolution on config.cfg on id1 folder

my glq.bat:

1glquake -heapsize 30000 -width 1024 -height 768 -sspeed 22050 %1 %2

autoexec.cfg

1echo Loading Some Stuff...
2+mlook
3exec nick.cfg
4alias rj "impulse 7;cl_pitchspeed 90000;+lookdown;+jump;wait;+attack;wait;-lookdown;-jump;-attack;centerview;cl_pitchspeed 150"
5gl_flashblend "0"
6r_wateralpha "0.3"
7r_mirroralpha "0.3"
8r_shadows "1"
9gl_polyblend "0"
10m_filter "1"
11gl_playermip "0"
12gl_keeptjunctions "1"
13fov 110

LoStSOul wrote on 2025-11-27, 22:42:

well... i still have the quake folder from 90s :D , always used glquake because 3dfx voodoo i think you can adjust resolution on […]
Show full quote

well... i still have the quake folder from 90s 😁 , always used glquake because 3dfx voodoo
i think you can adjust resolution on config.cfg on id1 folder

my glq.bat:

Copy code to clipboard

1glquake -heapsize 30000 -width 1024 -height 768 -sspeed 22050 %1 %2

autoexec.cfg

Copy code to clipboard

1echo Loading Some Stuff...
2+mlook
3exec nick.cfg
4alias rj "impulse 7;cl_pitchspeed 90000;+lookdown;+jump;wait;+attack;wait;-lookdown;-jump;-attack;centerview;cl_pitchspeed 150"
5gl_flashblend "0"
6r_wateralpha "0.3"
7r_mirroralpha "0.3"
8r_shadows "1"
9gl_polyblend "0"
10m_filter "1"
11gl_playermip "0"
12gl_keeptjunctions "1"
13fov 110

Thanks for the script! However, I GOT it working today with GLQuake 0.98 + shortcut resolution values. It's smooth, high res. and mouse always works now.
Script-wise, mine only contains +mlook. What does it bring aside form the mouse?

exec nick.cfg are fancy nickname on multiplayer

r_ and gl_ are some tweaks that used on multiplayer (with quakeworld), like 90% transparent water.. others i don't remember now

rj was a trick to do Rocket Jump (multiplayer too), need assign mouse right button to rj

LoStSOul wrote on 2025-11-28, 17:47:

exec nick.cfg are fancy nickname on multiplayer

r_ and gl_ are some tweaks that used on multiplayer (with quakeworld), like 90% transparent water.. others i don't remember now

rj was a trick to do Rocket Jump (multiplayer too), need assign mouse right button to rj

Interesting, I thought maps water is not transparent by design!