Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.

Blade of Darkness

From PCGamingWiki, the wiki about fixing PC games
Revision as of 00:18, 12 April 2018 by Garrbot (talk | contribs) (→‎Input settings: updated template usage)
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 of Darkness
Blade of Darkness cover
Developers
Rebel Act Studios
Publishers
Codemasters
Engines
Blade
Release dates
Windows February 21, 2001
Blade of Darkness on Wikipedia

General information

GOG.com Community Discussions
GOG.com Support Page

Availability

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

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

No save game cloud syncing information; you can edit this page to add it.

Video settings

Template:Video settings

Input settings

Template:Input settings

Audio settings

Template: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 the 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.

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

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
Processor (CPU) Intel Pentium II 400 MHz
System memory (RAM) 64 MB
Hard disk drive (HDD) 750 MB
Video card (GPU) 8 MB of VRAM

Notes

  1. 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).

References