Tweet
Someone who has been all setup for years or is used to the above problems doesn't think about all the landmines:
Installing Quake
1. If old CD, it won't install on XP. If it does install, quake.exe won't run. If you don't know better, you'll think you'll need DOSBox.
2. Assuming you get it installed, you try to use GLQuake and due to opengl32.dll, it gives you a b.s. error message. You'll think you can't use GLQuake and have to use WinQuake.
3. Let's say you know to delete OpenGL32.dll; GLQuake may or may not run if you have an older Intel display adapter. Due to the widespread sales of those machines, many still exist (think of the dozen or 2 times someone had to use D3D ProQuake in the last year).
Starting GLQuake
4. If you just double-click the GLQuake icon (or WinQuake), it won't run. You'll get a gfx wad error.
5. If you create a Windows shortcut and don't set the "Start In" directory, it won't run. You'll get a gfx wad error.
6. You have to use -width and -height with GLQuake.
7. If you use something other than 640 x 480, the conwidth and conheight make the text look terrible.
8. If you use an FOV other than 90, it might trash the screen with certain video cards.
9. There is no way to adjust the brightness. Except by using -gamma in the command line if you know to do that.
After It Is Running
10. Once you start GLQuake, if you don't know better, you don't know you can use the mouse to look.
11. If you do know better, you'll type +mlook. You'll be typing it every time you start Quake because it doesn't save to your config.
12. If you know what to do, you'll either edit autoexec.cfg or make your config read only.
13. Oh yeah ... half the other cvars in Quake don't save either. Like FOV or cl_bob 0. Unless you are experienced, you might not even know of those things.
14. Certain common actions, like quickly throwing a grenade and switching back to whatever weapon require a script. Chances are, player X or player Y or player Z, doesn't know this is possible.
15. If they do know how to do it, they'll be doing it in step 14.
16. With certain video cards, ALT-TAB in and out of Quake trashes the screen. Quake must be restarted to fix it.
Playing NQ Online
17. If don't know of this site, chances are you might only know of a single server. More than likely, you know of no servers.
18. You look for the server browser. There isn't one.
19. If you have a router or a DSL modem with built-in router capability (most DSL modems today), if you connect it will sit there with a blinking cursor and say "Connection Accepted". Unless you are using ProQuake or something else.
20. Even if you are using ProQuake 3.50, if you are using DSL and have it setup to manually connect or have it setup in less than an ideal way, you will get "Can't connect; server not found".
21. If you are using GLQuake (non-ProQuake), if you do connect and don't have the map, it'll say "model not found" and your client will be disconnected from the server.
22. If you are a #21, you aren't connected to the server long enough get any text from the server, like where to download maps.
===================================
Intermission
Except for 2 of the above items, all of the above hassles and pain in ass items apply to ProQuake 3.50.
=====================================
23. If you are using a client like Qrack or JoeQuake because it looks a lot nicer, be prepared to never to be able to play at a server using cheat-free. It'll let a ProQuake 3.50 client with a hacked opengl32.dll wallhack play ... someone who is cheating, but not you ... someone who is not cheating.
General Stuff
24. Let's say you do get connected, now depending on who is playing, you might get called names for "sucking" because you are new.
25. Or .. you might connect elsewhere (Shmack) and leave believing many players are cheating because 2 or 3 players constantly accuse better players of cheating.
26. On an exceptionally rare occasion, you might actually be playing against someone who is cheating because currently there is no fool-proof way of stopping all botting.
Offline Stuff
27. If you want to start an offline game against bots, prepare for a lot of work.
28. If you want to start a LAN CTF game, prepare for a lot of work.
29. Prepare for most of the things that, say, Quake 3 does easily (different game modes) to be very difficult.
The above list is a major pain.
This glosses over some other less troublesome issues that aren't frequent enough to be a real problem.
Installing Quake
1. If old CD, it won't install on XP. If it does install, quake.exe won't run. If you don't know better, you'll think you'll need DOSBox.
2. Assuming you get it installed, you try to use GLQuake and due to opengl32.dll, it gives you a b.s. error message. You'll think you can't use GLQuake and have to use WinQuake.
3. Let's say you know to delete OpenGL32.dll; GLQuake may or may not run if you have an older Intel display adapter. Due to the widespread sales of those machines, many still exist (think of the dozen or 2 times someone had to use D3D ProQuake in the last year).
Starting GLQuake
4. If you just double-click the GLQuake icon (or WinQuake), it won't run. You'll get a gfx wad error.
5. If you create a Windows shortcut and don't set the "Start In" directory, it won't run. You'll get a gfx wad error.
6. You have to use -width and -height with GLQuake.
7. If you use something other than 640 x 480, the conwidth and conheight make the text look terrible.
8. If you use an FOV other than 90, it might trash the screen with certain video cards.
9. There is no way to adjust the brightness. Except by using -gamma in the command line if you know to do that.
After It Is Running
10. Once you start GLQuake, if you don't know better, you don't know you can use the mouse to look.
11. If you do know better, you'll type +mlook. You'll be typing it every time you start Quake because it doesn't save to your config.
12. If you know what to do, you'll either edit autoexec.cfg or make your config read only.
13. Oh yeah ... half the other cvars in Quake don't save either. Like FOV or cl_bob 0. Unless you are experienced, you might not even know of those things.
14. Certain common actions, like quickly throwing a grenade and switching back to whatever weapon require a script. Chances are, player X or player Y or player Z, doesn't know this is possible.
15. If they do know how to do it, they'll be doing it in step 14.
16. With certain video cards, ALT-TAB in and out of Quake trashes the screen. Quake must be restarted to fix it.
Playing NQ Online
17. If don't know of this site, chances are you might only know of a single server. More than likely, you know of no servers.
18. You look for the server browser. There isn't one.
19. If you have a router or a DSL modem with built-in router capability (most DSL modems today), if you connect it will sit there with a blinking cursor and say "Connection Accepted". Unless you are using ProQuake or something else.
20. Even if you are using ProQuake 3.50, if you are using DSL and have it setup to manually connect or have it setup in less than an ideal way, you will get "Can't connect; server not found".
21. If you are using GLQuake (non-ProQuake), if you do connect and don't have the map, it'll say "model not found" and your client will be disconnected from the server.
22. If you are a #21, you aren't connected to the server long enough get any text from the server, like where to download maps.
===================================
Intermission
Except for 2 of the above items, all of the above hassles and pain in ass items apply to ProQuake 3.50.
=====================================
23. If you are using a client like Qrack or JoeQuake because it looks a lot nicer, be prepared to never to be able to play at a server using cheat-free. It'll let a ProQuake 3.50 client with a hacked opengl32.dll wallhack play ... someone who is cheating, but not you ... someone who is not cheating.
General Stuff
24. Let's say you do get connected, now depending on who is playing, you might get called names for "sucking" because you are new.
25. Or .. you might connect elsewhere (Shmack) and leave believing many players are cheating because 2 or 3 players constantly accuse better players of cheating.
26. On an exceptionally rare occasion, you might actually be playing against someone who is cheating because currently there is no fool-proof way of stopping all botting.
Offline Stuff
27. If you want to start an offline game against bots, prepare for a lot of work.
28. If you want to start a LAN CTF game, prepare for a lot of work.
29. Prepare for most of the things that, say, Quake 3 does easily (different game modes) to be very difficult.
The above list is a major pain.
This glosses over some other less troublesome issues that aren't frequent enough to be a real problem.
uake
ne.com
Comment