Difference between revisions of "Blade of Darkness"
m (→top: updated GOG.com ID format) |
|||
Line 11: | Line 11: | ||
{{Infobox game/row/date|Windows|February 21, 2001}} | {{Infobox game/row/date|Windows|February 21, 2001}} | ||
|steam appid = | |steam appid = | ||
− | |gogcom | + | |gogcom id = 1207659184 |
|strategywiki = | |strategywiki = | ||
|wikipedia = Severance: Blade of Darkness | |wikipedia = Severance: Blade of Darkness |
Revision as of 07:03, 14 December 2018
Developers | |
---|---|
Rebel Act Studios | |
Publishers | |
Codemasters | |
Engines | |
Blade | |
Release dates | |
Windows | February 21, 2001 |
General information
Availability
Source | DRM | Notes | Keys | OS |
---|---|---|---|---|
Retail |
- No longer available digitally due to issues with distribution rights.[1]
Game data
Configuration file(s) location
System | Location |
---|---|
Windows | <path-to-game>\Config[Note 1] |
Save game data location
System | Location |
---|---|
Windows | <path-to-game>\Save[Note 1] |
Save game cloud syncing
System | Native | Notes |
---|---|---|
GOG Galaxy |
Video settings
Input settings
Audio settings
Issues fixed
Crash upon launch
- Often this is due to video codec issues such as installed third party codec packs,[citation needed] and the error for this is often MEM_RESIZE_FAILED.
Rename the "video" directory contained in the "Data" directory[citation needed] |
---|
Convert the .mpg videos in the "video" directory and subdirectories to raw .avi while retaining the name to retain playback capability[citation needed] |
---|
Crash after introduction video
- The game doesn't properly handle failure states for when DirectPlay is not installed. Not having DirectPlay also significantly slows down the opening of the initial game launcher as well.
Install DirectPlay[citation needed] |
---|
Blank screen when using rOpenGL for video output
Alt-Tab out of the application then go back to it[citation needed] |
---|
Mouse behaves erratically
- This generally happens using Direct3D or rOpenGL for video output.
Force VSync through the GPU control panel[citation needed] |
---|
Camera/view moves choppily and unpredictably
The mouse-camera control granularity is linked somehow to the framerate. Higher framerates lead to smoother and slower mouse-camera control. Lower framerates lead to choppy control that is "quantized", too fast and jumpy. I've encountered such problems on both old and new hardware. Besides framerate, part of the problem seems to be related to the audio renderer, of all things.
The game is most controllable when framerate is as consistent as possible. Improve framerate by disabling fancy driver-forced settings, such as anti-aliasing. Cap framerate by forcing v-sync[citation needed] |
---|
Game runs too fast
- This typically happens in videos modes other than 3dfx and is due to the game not handling multiple processors properly.
Lock the game to a single processor[citation needed] |
---|
A popular way to automate this process is to create a .bat file, go to the game app's directory (using the cd command), then use either StartAffinity Blade.exe 0 or psexec -a 0 Blade.exe |
Cursor is missing/Black text
- Generally caused by using Direct3D for output with modern graphics hardware.
Use rOpenGL or 3dfx for video output[citation needed] |
---|
Other information
API
Executable | 32-bit | 64-bit | Notes |
---|---|---|---|
Windows |
System requirements
Windows | ||
---|---|---|
Minimum | Recommended | |
Operating system (OS) | 95 | 98, ME, 2000 |
Processor (CPU) | Intel Pentium II 400 MHz | Intel Pentium III 500 MHz |
System memory (RAM) | 64 MB | 128 MB |
Hard disk drive (HDD) | 750 MB | |
Video card (GPU) | 8 MB of VRAM | 32 MB of VRAM |
Notes
- ↑ 1.0 1.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).