This document provides complementary or late-breaking information to supplement the documentation. It contains important information you may need to know to run the program correctly.
It is important to remember that Gore is a work in progress and this version is classed as a test of networking, hardware and gameplay issues. Full compatibility, optimization, and stability work is not completed. In general, this version of Gore should provide fun gameplay when used with fairly modern machines, connected via a reliable network connection that supports TCP/IP protocol, and utilizing the proper OpenGL compliant 3D acceleration hardware and drivers (see below). Performance may vary depending on the speed of the machine and video card, the number of players in the game, and whether or not a stand-alone server is being used.
For further information read the Gore Multi-Player Test Documentation.html in the Docs directory.
Bug Reporting Procedure
Your help in reporting bugs is extremely appreciated. The better your description, the better chance we have fixing problems for the final release for you and others to enjoy.
To report a bug, write a description of the exact problem you have and the circumstances that surrounded it. If the program crashes it will attempt to write out an "exit.log" file to the main gore directory.
If there was no exit.log created, then the crash was not in gore and could likely be a video driver problem, or hardware lockup.
Email the description and attached exit.log (if appropriate) to gorebugs@4drulers.com.
Remove the exit.log from your gore directory to ensure you have a fresh exit.log the next time the program crashes.
Fixes in the Gore 1.25 patch
1) Server stability greatly improved. Specifically, fixed a crash with large games.
2) Fixed problem with clients randomly disconnecting.
3) Fixed binding for left ctrl and shift keys.
Known Issues
* Limited video card compatibility testing has been performed, please see the Video Card Compatibility section for details.
* Check the Gore F.A.Q. at www.4drulers.com web site for problems and workarounds.
* The voodoo5500 would not initialise in 800x600 resolution, but succeeded in 640x480.
Video Card Compatibility
We recommend the use of the video chipset manufacturers latest released drivers. Please note, only 100% OpenGL compliant video cards are supported, please refer to the videocard compatibility chart for more information.
If the Gore client is crashing on startup or if you suspect that you have video card incompatibilities Gore can be forced to start in windowed mode using the --windowed command line option.
Video Card Drivers
In general, any OpenGL driver for the supported video cards should work. If you have any problems running the program on your video card, we recommend you get the latest OpenGL compliant drivers from the manufactures website.
Voodoo Video Card Users
*Very Important*
Open the client_system.cfg file in the Settings directory, and alter the driver setting to:
driver 3dfxogl
This specifies that gore will utilise the 3dfxoGL.dll for rendering rather than the standard OpenGL.DLL
Desktop Settings
For best performance, ensure that you're desktop color palette is set to 16-bit (65535) Colors. If you have 32-bit (True Color) set, the game will still run, however it will have decreased performance.
System Requirements
Processor: Pentium II 200Mhz or better.
Operating System: Windows NT 4
Windows 98
Windows 95
Windows 2000
RAM: 64mb
Disk Space: 200mb
Video Card: 100% OpenGL Compliant Card
Command Converter
The Gore Command Converter program has been included in the installation to assist you setting up Gore for your key binding preferences. This version of the program supports the following configuration types:
* Quake III Arena
* Unreal Tournament
* Soldier Of Fortune
* Half-Life
The program can scan your system for installations of these program types, automatically import their settings into Gore, or provide an Advanced interface to find and convert the config files yourself.
If you don't have any configuration files to import or you would prefer not to, you still have the option of setting your key binding preferences in the Gore game itself through the menu system.
Standalone Server
Gore automatically starts in client mode and creates a second process to run in server mode when you click on the "Create" button, then load a map by clicking on the "Create Game" button. For large games, it is recommended that the server be run on its own machine.
To run Gore in Standalone Server Mode, start Gore from a DOS command prompt with the following arguments:
Gore --server --map dm1.ss
Where,
Gore = The name of the application
--server = Directs the application to start in Server Mode
--map = Directs the application to load a level/map
dm1.ss = The name of the level to load (dm1.ss,dm11.ss or dm18.ss)
You can also initialize the server with appropriate commands kept in a config file, by loading with the -load command. Eg:
Gore --server --map dm1.ss --load standalone.cfg
Where,
--load = Directs the application to load a config file
standalone.cfg = A custom made config file which contains gore commands
Default Server Port
The default server port is 10051. When connecting to a server running the default port you do not need to append the port number to the host value.
Change Server Port
In order to change the port that the server listens on, you need to change the gore value of "host". To set the port to 10060, at the server console type:
Host *:10060
Where,
* = The ip address of the server (this could be specified explicitly such as 123.456.789.123)
:10060 = The port number the server will listen for connections, prefixed by a colon.
This will save the value to the autoserver.cfg, and the next time you start the server the new port will take effect.
Server Browser Port
The server listens on a port which is one more than the host port for server browsers. So in the above example the server will attempt to listen on port 10061. If this port is unavailable, it will incrementally attempt the 100 ports above the one specified.
Multiple Servers
To run multiple servers on a single box, you will need to load a custom config file for each server instance. Specify a different port number for the host value for each server instance, ensuring to leave the browser port above each server's port free. The custom config will also be the place to set the different server names. An example config:
Host *:10060
Servername Mantis Manhole
Maxconnect 8
Where,
Host *:10060 = The port the server will listen on
Servername Mantis Manhole = Specifies the name of the server that will appear in browser lists.
Maxconnect 8 = Specifies on 8 players can connect at any point in time
Custom config files that are loaded from the command line, must be placed in the Settings sub folder of the main Gore directory.
Maxconnect
It is recommended that server operators limit maxconnect to a value of 12 or less for the demo version.
Contact Information
Feel free to contact the support staff at 4DRulers if you have any technical difficulties:
