Warnings
- SafeDisc DRM does not work on Windows Vista and later (see Availability for affected releases).
- GameSpy online services have been shut down (see Network for solutions).
General information
- Official website (4D Rulers)
- Official website (DreamCatcher Interactive, archived)
- Gore fansite (archived)
Availability
- SafeDisc DRM does not work on Windows Vista and later (see above for affected releases).
Demo
- A demo is available here (Alt-link.
Essential improvements
Patches
- Patch 1.48 with bonus-pack containing extra maps.
- Patch 1.50 is the latest game's patch.
- Gorespy patch is a fix to replace not working Gamespy's master with fan created Gorespy.com master server.
Game data
Configuration file(s) location
Save game data location
Video
| Graphics feature |
State |
Notes |
| Widescreen resolution |
|
Vert-, increase FOV to compensate. |
| Multi-monitor |
|
See Widescreen resolution. |
| Ultra-widescreen |
|
See Widescreen resolution. |
| 4K Ultra HD |
|
See Widescreen resolution. |
| Field of view (FOV) |
|
90° by default, see Field of view (FOV). |
| Windowed |
|
|
| Borderless fullscreen windowed |
|
|
| Anisotropic filtering (AF) |
|
1x, 2x, 4x, 6x, 8x. |
| Anti-aliasing (AA) |
|
FSAA 1x, 2x, 4x, 6x, 8x, 16x. |
| High-fidelity upscaling |
|
See the glossary page for potential workarounds. |
| Vertical sync (Vsync) |
|
|
| 60 FPS and 120+ FPS |
|
Extremely high FPS (in the high hundreds) significantly reduces jumping height and may make certain sections (such as climbing the rope net in the first level) impossible to progress past. Turning on Vsync should prevent this. |
| High dynamic range display (HDR) |
|
See the glossary page for potential alternatives. |
| Color blind mode |
|
See the glossary page for potential workarounds. |
- Image is Vert- and FOV should be increased to compensate.
|
Set custom resolution
|
- Go to
<path-to-game>\settings\.
- Open
client_system.cfg.
- Change
res 1024x768 to your desired resolution.
Notes
- To change resolution on Windows 10, set Gore compatibility mode to Windows XP SP2.
- In game you can also change resolution by entering command
res 1024x768 and apply command reset_renderer.
|
- The game supports from 80 to 90 FOV natively through the
autoclient.cfg file and the console.
Hex edit Gore.exe and change the field of view
|
- Open
Gore.exe with a hex editor such as HxD.
- Press Ctrl+F, change the data type to hex values, search for
00 00 B4 42 and change it to 00 00 F0 42.
- Now do either of the following:
- Start the game, press ~ to open the console and type
fov up to 120.
- Go to
<path-to-game>\settings\, open autoclient.cfg, change fov up to 120, save the file and launch the game.
Notes
- For other values, consult the Floating Point to Hex Converter (Make sure to tick the box Swap to use big-endian at the top before converting the float value to hexadecimal).
|
Input
Audio
| Audio feature |
State |
Notes |
| Separate volume controls |
|
|
| Surround sound |
|
|
| Subtitles |
|
|
| Closed captions |
|
|
| Mute on focus lost |
|
|
| Royalty free audio |
|
|
Localizations
| Language |
UI |
Audio |
Sub |
Notes |
| English |
|
|
|
|
| Czech |
|
|
|
Fan - 1 |
| French |
|
|
|
|
| German |
|
|
|
|
| Polish |
|
|
|
Fan translation, download. |
| Russian |
|
|
|
Game was released in Russia under name "Gore: Первая кровь". |
Network
Multiplayer types
Connection types
Issues unresolved
|
Workaround: Force anti-aliasing in the GPU control panel[citation needed]
|
Issues fixed
|
Change Windows compatibility mode[citation needed]
|
- Right-click
Gore.exe and select Properties.
- Go to the Compatibility tab.
- Make sure Run this program in compatibility mode for is checked and set to Windows XP (Service Pack 2).
|
Game zoomed in at high resolutions (DPI issues)
|
Change high DPI settings[citation needed]
|
- Right-click
Gore.exe and select Properties.
- Go to the Compatibility tab.
- Near the bottom of the window, select Change high DPI settings.
- Make sure Override high DPI scaling behaviour is set to Application in the drop down list.
- Click on Apply and launch the game.
|
Rocket Bug (Jumping bug)
When player have more than ~495 FPS, he might me unavailable to perform jumps (also, jump boosts from ladders) and firing with Rocket Launcher might fire unexpected all the loaded rockets. To fix this the game needs to be FPS limited due to monitor's refresh rate or it can be less than ~495 FPS.
|
Change Windows compatibility mode[citation needed]
|
- Force FPS Limit in the GPU control panel.
- (Second way) Use Vsync option in game's Video options.
|
Other information
API
| Technical specs |
Supported |
Notes |
| OpenGL |
|
|
| Executable |
32-bit |
64-bit |
Notes |
| Windows |
|
|
|
Middleware
|
Middleware |
Notes |
| Multiplayer |
GameSpy |
|
System requirements
| Windows |
|
Minimum | Recommended |
| Operating system (OS) |
95 | 98, 2000, NT4, ME, XP |
| Processor (CPU) |
Intel Pentium II 350 MHz | 600 MHz |
| System memory (RAM) |
64 MB | 128 MB |
| Storage drive (HDD/SSD) |
700 MB | |
| Video card (GPU) |
OpenGL compatible 16 MB of VRAM DirectX 8.1 compatible | 32 MB of VRAM |
| Other |
4x CD-ROM Drive | |
Notes
- ↑ This version of SafeDisc DRM does not work on Windows 10[1] or Windows 11 and is disabled by default on Windows Vista, Windows 7, Windows 8, and Windows 8.1 when the KB3086255 update is installed.[2]
- ↑ 2.0 2.1 When running this game without elevated privileges (Run as administrator option), write operations against a location below
%PROGRAMFILES%, %PROGRAMDATA%, or %WINDIR% might be redirected to %LOCALAPPDATA%\VirtualStore on Windows Vista and later (more details).
References