mQ | Modem Quake Setup Guide
Version 0.9 | By ænima | 12/21/97
Introduction
Quake was written with the intention of
being a revolutionary multi-player experience. Even a year after
its release, it is still a multi-player phenomenon on the Internet.
Quakeworld came along a few short months after Quake's release and made
finding and joining Quake servers a snap. Quakeworld's game play
was also vastly improved over net Quake's.
The modem code of the original game was
simply a variant on the games network code. Instead of a peer-networking
protocol seen in Doom and Duke Nukem 3D, the game shared the Client/Server
approach of the IPX/TCP components. This resulted in modem games
where one player had the advantage of being the server and enjoyed lag-free
play. The client often had to deal with choppy gameplay and lags
between 150-200ms.
It was discovered that one could reduce
the lag of modem-to-modem play using Windows 95's Dial-Up-Networking (DUN).
Simulating an IPX network over a modem connection, it first allowed GLQuake
players modem play. Because subsequent versions of Quake (WinQuake,
GLQuake) lacked modem support altogether, this became the only solution
for dual-player modem games.
Quake 2 hit the store shelves December
9th 1997, and Quake fans everywhere rejoiced. A much improved graphics
engine and more balanced deathmatch experience were promised right out
of the box. We knew id was going to leave out modem connections from
Quake 2, but there was no cause for alarm because we had our DUN hack.
Conspicuously absent: IPX network support.
Now we had to go back and rework our DUN
connections to operate with TCP/IP connections instead. Unsure of
how to do this at first, there was a thrust to get it done. Quake
2 included client-side prediction, and we were eager to play smoother modem
games. Learning from the network boys, we got a hack working.
Reports of sub-100 millisecond connections promise great, lag-free modem
games.
This guide was setup with the average user
in mind. My goal is to help all of those who have good friends with
a copy of the game deathmatch without having to connect to the internet.
It results in more reliable connections and smoother overall gameplay.
I hope you can benefit from this experience.
Setting up the Dial-Up-Server
The Dial-Up-Server is an add-on from Microsoft
that enables your computer to answer modem calls and connect them to your
Local Area Network (LAN). This allows remote-access users to use
their modems to connect directly to a remote network. This is sort
of like your connection to the public internet.
This add-on can be obtained for free as
a download from Microsoft. For our purposes of setting up a virtual
network to play Quake, it is also very easy to configure.
Getting the Dial-Up-Server
Configuring the
Dial-Up-Server
The interface for the Dial-Up-Server can
be found in the Dial-Up-Networking folder under the "Connections" menu.
Open up the Dial-Up-Server and click on
"Server Types" and configure them as follows:
The Dial-Up-Server is now configured to
host our virtual network.
Setting up Network
Properties
Now that we have the Dial-Up-Server installed
and configured, we must now check to see if you have the appropriate clients/protocols
installed in Windows.
Installing
Network Resources
From the "Start" menu, select "Settings"
and open the "Control Panel." From this window, select "Network."
This window is what we will refer to as the "Network Properties" window:
As in the image shown, we must have the
"Client for Microsoft Networks", the "Dial-Up Adapter" and "TCP/IP" protocol
(the IPX protocol, for Quake 2, is optional). If you don't have one
or more of these installed, click "Add" and add them. To be reading
this on the internet, you should already have the Dial-Up Adapter intsalled
along with TCP/IP installed, so you would likely just have to add the "Client
for Microsoft Networks".
Configuring
TCP/IP Properties
Warning: Read this part carefully.
If you skip ahead, it might make your internet connection unusable.
Open TCP/IP properties and select the "IP
Address" tab. For the purposes of our network, we must make up an
IP address and assign different ones to each computer. The Subnet
Mask must be identical on both machines.
For the purposes of our connection, set
the IP on one as 192.0.0.1 and the other to 192.0.0.2. The numbers
don't have any real meaning, but they seem to be the most popular.
For the subnet mask, set EACH to 255.255.255.0
as shown above. These MUST be identical on both machines in order
for the network to work.
Note: If your ISP has dynamic
addressing, set these back to "Server Assigned" after your Quake session
or you may be unable to connect to the internet. If you're unsure,
set it back anyway.
Remember the IP addresses you chose.
You'll need them later.
Setting up Dial-Up-Networking
Configuring Dial-Up-Networking is akin
to configuring the connection you have to the internet. With just
a few short clicks, its done.
Open up Dial-Up-Network and click on "Make
New Connection." Simply enter your friends name for the name and
then his/her phone number. Done.
Right-click on the new connection and select
"Properties." Set up as follows: Under the "Server Types" tab,
the type should be PPP and all of the boxes should be unchecked.
Click "TCP/IP Settings..." and keep IP and DNS as server assigned and the
rest of the options unchecked.
Now both the server and client for Windows
DUN are setup.
Modems and Dialing
Now that we have both DUN and DAS setup,
its up to you to choose who between you will be the server. I'm NOT
talking about the server for the game, but for the Windows connection.
To set up the server, simply open up DAS
from the DUN menu, click "Allow Caller Access" and "Apply." A small
icon should apper in the system tray indicating that it's waiting for a
call.
For the caller, open up DUN, and double-click
on the connection icon. You can specify a username if you want, but
it's not necessary. Verify that the phone number is correct, and
click "Connect." Note: A password is NOT necessary, so don't enter
one.
Before dialing, make sure to decide who
will host the Quake game. This is independent of who calls who in
Windows.
If you don't connect successfully, go back
and make sure everything is properly configured. You might have accidentally
overlooked something.
Setting up Quake/2
Now that you're connected, you can start
Quake/2.
Starting TCP/IP
Server
From the multiplayer menu, click "Start
a Server" if you're going to host the game. Set all of the desired
options and select begin.
Joining TCP/IP Server
From the multiplayer menu, click "Join
a Server." You'll have to add your buddy's IP address into the address
book (I told you to remember it!). Select his IP and press enter
to connect.
Performance
Considerations
Now that you've successfully connected
and spent hours fragging away, you might have noticed that your connection
might not be quite as good as you would have had expected. Fortunately,
there are a few measures you can take to improve it.
First of all, you should try all combinations
of who calls who in Windows and who hosts the game. You might not
think that your connection could be affected by it, but it could spell
the difference between a 100ms client ping or one of 250ms! Make
sure to try them all, you could find one that'll play great.
Also, the client can enable client-side
prediction (a Quakeworld enhancement) by simply typing "cl_predict 1" at
the console before joining the server. It results, usually, in better
gameplay.
This is the section of the guide that will
undergo the most updating. I encourage people to contact me with
their comments/suggestions for this part of the guide. I would love
to know what kind of connections most people are getting. I might
even set up an bulletin board for that purpose.
Contacting ænima
Please direct all suggestions/comments/flames
to me. All
feedback is not only welcome, but appreciated as well.
Back
to mQ Home