Blade: The Edge of Darkness

From PCGamingWiki, the wiki about fixing PC games
This page is a stub: it lacks content and/or basic article components. You can help to expand this page by adding an image or additional information.
Blade: The Edge of Darkness
Blade: The Edge of Darkness cover
Developers
Rebel Act Studios
Publishers
Codemasters
Engines
Blade
Release dates
Windows February 21, 2001
Blade: The Edge of Darkness at Wikipedia

General information

GOG.com Community Discussions
GOG.com Support Page

Availability[edit]

Source DRM Notes Keys OS
Retail
DRM details are not known
Windows
No longer available digitally due to issues with distribution rights.[1]

Game data[edit]

Configuration file(s) location[edit]

System Location
Windows <path-to-game>\Config

Save game data location[edit]

System Location
Windows <path-to-game>\Save

Save game cloud syncing[edit]

System Native Notes
GOG Galaxy

Video settings[edit]

Graphics option Option WSGF Notes
Widescreen resolution
Stretched
Multi-monitor
Ultra-widescreen
4K Ultra HD
2048x1536 is the highest supported resolution
Field of view (FOV)
Camera can be zoomed in/out in 3 presets
Windowed
Available only for some renderers
Borderless fullscreen windowed
Anisotropic filtering (AF)
Must be forced through Nvidia/AMD control panel
Anti-aliasing (AA)
Must be forced through Nvidia/AMD control panel
Vertical sync (Vsync)
Enabled by default on most renderers. Disabling can cause cutscenes not to play properly. Leaving enabled may cause main menu text to become transparent and hard to see.
60 FPS and 120+ FPS
Going above 60 FPS may cause some cutscenes not to play properly.
Color blind mode

Input settings[edit]

Keyboard and mouse Native Notes
Remapping
Up to 3 possible binds per action
Mouse acceleration
No mouse acceleration present
Mouse sensitivity
Mouse input in menus
Mouse Y-axis inversion
Controller
Controller support
See the glossary page for potential workarounds.

Audio settings[edit]

Audio options Native Notes
Separate volume controls
Music and sound effects
Surround sound
Up to 7.0 with Creative ALchemy.
Subtitles
Can not be disabled
Closed captions
Mute on focus lost
EAX support
A3D 1.0[2] and EAX 2[3]

Issues fixed[edit]

Crash upon launch[edit]

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[edit]

The game doesn't properly handle failure states for when DirectPlay is not installed. Not having DirectPlay also significantly slows the down the opening of the initial game launcher as well.
Install DirectPlay[citation needed]

Blank screen when using rOpenGL for video output[edit]

Alt-Tab out of the application then go back to it[citation needed]

Mouse behaves erratically[edit]

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[edit]

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.

Try using different audio renderers. For me the best was "RAD RSX 3D"[citation needed]
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[edit]

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[edit]

Generally caused by using Direct3D for output with modern graphics hardware.
Use rOpenGL or 3dfx for video output[citation needed]

Other information[edit]

API[edit]

Technical specs Supported Notes
64-bit executable

System requirements[edit]

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

References