Difference between revisions of "Blade of Darkness"
From PCGamingWiki, the wiki about fixing PC games
m (→Availability: replaced: http://www.gog.com → https://www.gog.com) |
m (updated template usage) |
||
Line 12: | Line 12: | ||
|steam appid = | |steam appid = | ||
|gogcom page = blade_of_darkness | |gogcom page = blade_of_darkness | ||
+ | |strategywiki = | ||
|wikipedia = Severance: Blade of Darkness | |wikipedia = Severance: Blade of Darkness | ||
|winehq = 4347 | |winehq = 4347 | ||
Line 123: | Line 124: | ||
==Issues fixed== | ==Issues fixed== | ||
===Crash upon launch=== | ===Crash upon launch=== | ||
− | Often this is due to video codec issues such as installed third party codec packs,{{CN|date=September 2015}} and the error for this is often MEM_RESIZE_FAILED. | + | {{ii}} Often this is due to video codec issues such as installed third party codec packs,{{CN|date=September 2015}} and the error for this is often MEM_RESIZE_FAILED. |
+ | |||
{{Fixbox|1= | {{Fixbox|1= | ||
{{Fixbox/fix|Rename the "video" directory contained in the "Data" directory|ref={{CN|date=September 2015}}}} | {{Fixbox/fix|Rename the "video" directory contained in the "Data" directory|ref={{CN|date=September 2015}}}} | ||
Line 132: | Line 134: | ||
===Crash after introduction video=== | ===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. | + | {{ii}} 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. |
+ | |||
{{Fixbox|1= | {{Fixbox|1= | ||
{{Fixbox/fix|Install [[Microsoft Windows#Older games refuse to start on Windows 8 and later|DirectPlay]]}} | {{Fixbox/fix|Install [[Microsoft Windows#Older games refuse to start on Windows 8 and later|DirectPlay]]}} | ||
}} | }} | ||
+ | |||
===Blank screen when using rOpenGL for video output=== | ===Blank screen when using rOpenGL for video output=== | ||
{{Fixbox|1= | {{Fixbox|1= | ||
{{Fixbox/fix|Alt-Tab out of the application then go back to it}} | {{Fixbox/fix|Alt-Tab out of the application then go back to it}} | ||
}} | }} | ||
+ | |||
===Mouse behaves erratically=== | ===Mouse behaves erratically=== | ||
− | This generally happens using Direct3D or rOpenGL for video output. | + | {{ii}} This generally happens using Direct3D or rOpenGL for video output. |
+ | |||
{{Fixbox|1= | {{Fixbox|1= | ||
{{Fixbox/fix|Force VSync through the GPU control panel}} | {{Fixbox/fix|Force VSync through the GPU control panel}} | ||
}} | }} | ||
+ | |||
===Game runs too fast=== | ===Game runs too fast=== | ||
− | This typically happens in videos modes other than 3dfx and is due to the game not handling multiple processors properly. | + | {{ii}} This typically happens in videos modes other than 3dfx and is due to the game not handling multiple processors properly. |
+ | |||
{{Fixbox|1= | {{Fixbox|1= | ||
{{Fixbox/fix|Lock the game to a single processor}} | {{Fixbox/fix|Lock the game to a single processor}} | ||
Line 155: | Line 163: | ||
or | or | ||
− | psexec -a 0 Blade.exe}} | + | psexec -a 0 Blade.exe |
+ | }} | ||
+ | |||
===Cursor is missing/Black text=== | ===Cursor is missing/Black text=== | ||
− | Generally caused by using Direct3D for output with modern graphics hardware. | + | {{ii}} Generally caused by using Direct3D for output with modern graphics hardware. |
+ | |||
{{Fixbox|1= | {{Fixbox|1= | ||
{{Fixbox/fix|Use rOpenGL or 3dfx for video output}} | {{Fixbox/fix|Use rOpenGL or 3dfx for video output}} | ||
}} | }} | ||
+ | |||
==System requirements== | ==System requirements== | ||
{{System requirements | {{System requirements |
Revision as of 07:26, 20 July 2016
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.
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
Template:Game data/row
System | Location |
---|
Save game data location
Template:Game data/row
System | Location |
---|
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.
Instructions |
---|
Instructions |
---|
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.
Instructions |
---|
Blank screen when using rOpenGL for video output
Instructions |
---|
Mouse behaves erratically
- This generally happens using Direct3D or rOpenGL for video output.
Instructions |
---|
Game runs too fast
- This typically happens in videos modes other than 3dfx and is due to the game not handling multiple processors properly.
Instructions |
---|
Cursor is missing/Black text
- Generally caused by using Direct3D for output with modern graphics hardware.
Instructions |
---|
System requirements
Windows | ||
---|---|---|
Minimum | ||
Operating system (OS) | ||
Processor (CPU) | ||
System memory (RAM) | ||
Hard disk drive (HDD) |