
There are
two ways to host a race using iGOR - Locally and Remotely. To
host locally is explained on this page. Remote hosting is
explained here, but is
essentially the same as local hosting, with the added process of
connecting to the remote host to send/receive information.
When you click on Host, this dialog is
shown. Choose 'Host a race Locally' to have the race run on your
machine. See Remote Hosting
for the other two options.
Hosting Dialog
Load Settings... - if you have
previously saved some host settings, load them here.
Save
Settings... - to save settings for different hostings, press
this button!
Host -
click to host the race.
Close - click
to close the dialog and remember what you changed.
Cancel
- click to close the dialog, forgetting any changes made.

Hosting Dialog Tab 1 - Host Settings
Host GPL Settings
GPL Mod:
choose the mod to use for this hosting. Only one mod can be
chosen for the host (additional mods for connecting clients are
specified on the Security tab), for each hosting.
Note: You cannot host an e.g. '65
Monza followed by a '67 Silverstone without restarting the host.
Auto-export
replay: check this to have GPL save the replay for the
whole event when it has finished.
Replay memory
override: check this and set the amount of memory in
kilobytes if you wish to override the setting in your core.ini file.
Log in-game
chat: check this to save the in-game chat between players.
Auto-export
standings: check this to automatically export the
standings file when each event finishes.
Full-Screen:
On some machines you might want to host
GPL in a window. Some graphics cards will need to be in 16-bit
mode for this to work properly.
Max. Players:
Set the maximum number of players that are allowed to connect to the
race here.
AI Cars:
If you want any AI cars to be in the
race, set the number here.
Host Driver Settings
- note that these settings will be changed when you
change the GPL Mod choice. iGOR remembers your settings per-Mod, for quick setup of a
different mod hosting.
Host Player: Choose the player for the host.
Only needed if the server is non-dedicated and you wish to drive as
well as host.
Host Car: Choose the
car for the host player. The host will have free choice of cars,
unlike clients who must adhere to any chassis restrictions imposed by
the host.
Helmet Colour: Select
the helmet colour for the host player. Note that many of the
updated graphical cars do not follow the GPL helmet colours - this
option only works properly for original 2D style helmets.
GP/F2/F3: ('67 only)
choose the driver class for the host player.
Steering Hack: set your
preference for steering hackiness.
Override FF Settings:
set your force-feedback override choice. If you choose to
override your core.ini settings, go into the force-feedback dialog to
specify the values.
Server
Information
Host comments: any comments you wish to be
shown in the racelist comments column, enter here.
Connection
type: give the people viewing the racelist
some idea of your bandwidth.
Server
location: connections are generally of a
better quality when geographical close. State/Country is usually
enough for people to go on.


Host
Dialog Tab 2 - Network/Server settings
Bandwidth Settings
Specify the
bandwidth parameters that you wish to use here. If you don't
override core.ini, and core.ini is different to the default 3/84/3/84,
anyone connecting with parameters that don't match will either time-out
on the GPL connection screen, or receive a bandwidth mismatch error.
It is assumed that if you're changing these parameters, you are also
using the bandwidth patch by Bart Westra, and that you know what you're
doing! Make a note in the Server Comments field so that
clients know if your host is bandwidth patched!
Enforce
maximum latency: clients attempting to join a race when
their ping is higher than this setting will be stopped.
BEWARE! If you set a value that is too small and/or you prevent
clients from pinging your server, you might not get many people
joining. 50 is too small for Internet play, 400 is perhaps too
high, but not if the drivers are careful ;-)
Prevent
Clients from pinging this Server: There may be times that
you do not wish your hosting machine to be pinged during racelist
updates. If you really really don't want to be pinged, check this
box, otherwise leave it unchecked.
Server Settings
Allow direct (IPX) connections: Only check
this if you need to join your race from over a LAN connection.
Allow serial-port connections: Only check
this for direct serial-serial connections.
Ignore net send errors: Recommended - ignore
network send errors.
Ignore net read errors: Recommended - ignore
network read errors.
Log network errors: Check this to write out
a log file of any network errors.
Disable Checkpoints: Recommended - some
tracks have checkpoints that must be driven through correctly, else the
driver will be black flagged. Sometimes drivers will be
blackflagged even if they did drive through a checkpoint, because their
connection went warpy at the wrong moment.
Network LQS Meters: Not generally needed for
hosts, this option shows the LatencyQualitySkew meters.
Use different join port: By default GPL uses
port 32766-32786 for connections. Change this if you want a
different base port (32766 is default).
Run \scripts\prerace.vbs -
included at request by Bart Westra, this allows for the prerace.vbs
file to be run just before GPL is booted. I'm no server admin,
but I can see where this will have uses
Run
\scripts\postrace.vbs - this script is executed after GPL has
closed down, and iGOR is just starting. I am informed that
scripts are in development for GPL Ladder and GPLRank, amongst other
things :-)


Host Dialog
Tab 3 - Security Settings
Permissions
Password: check this box and type in a password if you
want your race to be passworded.
Boss Password: check this box and type in a password if
you want a boss password for the race. Doing this allows racers
to join the race as boss, so they can use the !eject and !shutdown
commands.
Client Authentication: check this box to enable the
authentication settings
Allow different mods: check
this if you want to let
drivers use mods different to the host mod - e.g. a race that allows
'67 drivers to compete against '65 drivers.
-All Mods:
choosing
this option will allow any mod to be driven. In effect
this makes the server a free-for-all, with no physics checking.
-Specified Mods:
choosing
this option allows you to specify which mods can be taken to
the track by joining drivers. The specified mods are in addition to the host mod as
specified on the first tab.
Allowed Chassis: if you want to restrict the cars that can
be driven, check the appropriate boxes.
Allowed Classes: ('67 only) - check the boxes to restrict
the class of cars that can be driven.
|
|
|
|