Difference between revisions of "Orcs Must Die!"
(removed OnLive details) |
Marioysikax (talk | contribs) (Major cleanup. Moved DLC to seriesbox. Modding -> Other as not essential at all. Explaining creating file like for 5-y-o... Removed WSGF copy-paste and linked instead. Localization.) |
||
Line 30: | Line 30: | ||
}} | }} | ||
{{ii}} All versions require [[Steam]]. | {{ii}} All versions require [[Steam]]. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==Game data== | ==Game data== | ||
===Configuration file(s) location=== | ===Configuration file(s) location=== | ||
{{Game data| | {{Game data| | ||
− | {{Game data/row|Windows|{{p|game}}\Data\startup\user.cfg}} | + | {{Game data/row|Windows|{{p|game}}\Data\startup\user.cfg<br/>{{p|userprofile}}\Documents\Orcs Must Die\VideoSettings.xml}} |
}} | }} | ||
− | + | {{ii}} <code>VideoSettings.xml</code> includes resolution, vsync and MSAA. <code>user.cfg</code> has to be created by user. | |
− | |||
===Save game data location=== | ===Save game data location=== | ||
Line 78: | Line 64: | ||
|4k ultra hd wsgf award = incomplete | |4k ultra hd wsgf award = incomplete | ||
|widescreen resolution = true | |widescreen resolution = true | ||
− | |widescreen resolution notes= | + | |widescreen resolution notes= |
|multimonitor = hackable | |multimonitor = hackable | ||
− | |multimonitor notes = | + | |multimonitor notes = Refer to [http://www.wsgf.org/dr/orcs-must-die/en WSGF article]. |
|ultrawidescreen = unknown | |ultrawidescreen = unknown | ||
|ultrawidescreen notes = | |ultrawidescreen notes = | ||
Line 104: | Line 90: | ||
|color blind notes = | |color blind notes = | ||
}} | }} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
===Overheating Graphics Card=== | ===Overheating Graphics Card=== | ||
− | + | {{ii}} There's reports game overheating GPU. Vsync seems to help but some users may prefer not to use it. | |
− | + | {{Fixbox|1= | |
− | + | {{Fixbox/fix|Cap the frame rate|ref=<ref>[http://support.robotentertainment.com/customer/portal/articles/339825-my-graphics-card-is-running-very-hot-or-overheating- Robot Entertainment | My graphics card is running very hot or ...]</ref>}} | |
− | < | + | # Open created <code>user.cfg</code> in [[#Game data|configuration file location]]. |
− | + | # Add new line <code>Forcefps=XX</code> and replace <code>XX</code> with desired value. | |
+ | }} | ||
===[[Glossary:Borderless fullscreen windowed|Windowed]]=== | ===[[Glossary:Borderless fullscreen windowed|Windowed]]=== | ||
− | + | {{Fixbox|1= | |
− | + | {{Fixbox/fix|Edit user.cfg}} | |
− | + | # Open created <code>user.cfg</code> in [[#Game data|configuration file location]]. | |
− | < | + | # Add new line <code>Window</code> |
− | + | }} | |
==Input settings== | ==Input settings== | ||
Line 184: | Line 131: | ||
===[[Glossary:Remapping|Remapping]]=== | ===[[Glossary:Remapping|Remapping]]=== | ||
− | + | {{Fixbox|1= | |
− | + | {{Fixbox/fix|Edit user.cfg|ref=<ref>[http://forums.steampowered.com/forums/showthread.php?t=2199997 Custom Keybinding using user.cfg - Steam Users' Forums]</ref>}} | |
− | + | # Open created <code>user.cfg</code> in [[#Game data|configuration file location]]. | |
+ | # Copy and paste the following to <code>user.cfg</code>, uncomment key you want to rebind and change key to desired one. | ||
<pre>// Sample Key Bindings | <pre>// Sample Key Bindings | ||
// Uncomment and remap to your liking. (delete the // marks at the beginning of the line) | // Uncomment and remap to your liking. (delete the // marks at the beginning of the line) | ||
Line 254: | Line 202: | ||
// kp_8 Keypad 8 | // kp_8 Keypad 8 | ||
// kp_9 Keypad 9 </pre> | // kp_9 Keypad 9 </pre> | ||
+ | }} | ||
====Alternative Keyboard Layouts==== | ====Alternative Keyboard Layouts==== | ||
− | + | {{Fixbox|1= | |
− | + | {{Fixbox/fix|Edit user.cfg}} | |
− | # | + | # Open created <code>user.cfg</code> in [[#Game data|configuration file location]]. |
− | < | + | # Add new line <code>Keyboardlayout="XXXXX"</code> and replace <code>XXXXX</code> with either <code>azerty</code>, <code>qwerty</code> or <code>qwertz</code> to force said keyboard layout. |
− | + | }} | |
− | |||
− | |||
− | |||
==Audio settings== | ==Audio settings== | ||
Line 279: | Line 225: | ||
|eax support = | |eax support = | ||
|eax support notes = | |eax support notes = | ||
+ | }} | ||
+ | |||
+ | {{L10n|content= | ||
+ | {{L10n/switch | ||
+ | |language = English | ||
+ | |interface = true | ||
+ | |audio = true | ||
+ | |subtitles = false | ||
+ | |notes = | ||
+ | |fan = | ||
+ | |fan notes = | ||
+ | }} | ||
+ | {{L10n/switch | ||
+ | |language = French | ||
+ | |interface = true | ||
+ | |audio = unknown | ||
+ | |subtitles = false | ||
+ | |notes = | ||
+ | |fan = | ||
+ | |fan notes = | ||
+ | }} | ||
+ | {{L10n/switch | ||
+ | |language = German | ||
+ | |interface = true | ||
+ | |audio = unknown | ||
+ | |subtitles = false | ||
+ | |notes = | ||
+ | |fan = | ||
+ | |fan notes = | ||
+ | }} | ||
+ | {{L10n/switch | ||
+ | |language = Italian | ||
+ | |interface = true | ||
+ | |audio = unknown | ||
+ | |subtitles = false | ||
+ | |notes = | ||
+ | |fan = | ||
+ | |fan notes = | ||
+ | }} | ||
+ | {{L10n/switch | ||
+ | |language = Spanish | ||
+ | |interface = true | ||
+ | |audio = unknown | ||
+ | |subtitles = false | ||
+ | |notes = | ||
+ | |fan = | ||
+ | |fan notes = | ||
+ | }} | ||
+ | {{L10n/switch | ||
+ | |language = Russian | ||
+ | |interface = true | ||
+ | |audio = unknown | ||
+ | |subtitles = false | ||
+ | |notes = | ||
+ | |fan = | ||
+ | |fan notes = | ||
+ | }} | ||
+ | {{L10n/switch | ||
+ | |language = Japanese | ||
+ | |interface = true | ||
+ | |audio = unknown | ||
+ | |subtitles = false | ||
+ | |notes = | ||
+ | |fan = | ||
+ | |fan notes = | ||
+ | }} | ||
+ | {{L10n/switch | ||
+ | |language = Polish | ||
+ | |interface = true | ||
+ | |audio = unknown | ||
+ | |subtitles = false | ||
+ | |notes = | ||
+ | |fan = | ||
+ | |fan notes = | ||
+ | }} | ||
+ | {{L10n/switch | ||
+ | |language = Brazilian Portuguese | ||
+ | |interface = true | ||
+ | |audio = unknown | ||
+ | |subtitles = false | ||
+ | |notes = | ||
+ | |fan = | ||
+ | |fan notes = | ||
+ | }} | ||
}} | }} | ||
==Issues fixed== | ==Issues fixed== | ||
===Black Boxes On Flaming Arrows=== | ===Black Boxes On Flaming Arrows=== | ||
− | This issue is most likely caused by incompatibility with certain graphics cards. You can avoid this by lowering the graphics detail slider in the games options. | + | {{ii}} This issue is most likely caused by incompatibility with certain graphics cards. You can avoid this by lowering the graphics detail slider in the games options. |
===Bladestaff Alt-fire Crash=== | ===Bladestaff Alt-fire Crash=== | ||
− | + | {{ii}} Most recent game patches should have addressed this issue. If you are still experiencing this with Nvidia SLI setup try following fix. | |
+ | {{Fixbox|1= | ||
+ | {{Fixbox/fix|Nvidia Control Panel}} | ||
# Open the NVIDIA Control Panel and click 'Manage 3D Settings'. | # Open the NVIDIA Control Panel and click 'Manage 3D Settings'. | ||
− | # Click on the 'Program Settings' tab and click Add, before selecting <code>orcsmustdie.exe</code> | + | # Click on the 'Program Settings' tab and click Add, before selecting <code>orcsmustdie.exe</code> located in <code>{{p|game}}\Build\release</code>. |
# Scroll through the 'Feature' list until you find 'SLI Rendering Mode' and set this to 'Force alternate frame rendering 1', accepting the warning box which will appear. | # Scroll through the 'Feature' list until you find 'SLI Rendering Mode' and set this to 'Force alternate frame rendering 1', accepting the warning box which will appear. | ||
# Finally, click apply. | # Finally, click apply. | ||
+ | }} | ||
− | ===Failed To Correctly Load Data Files | + | ==="Failed To Correctly Load Data Files", "Failed To Initialise Engine"=== |
− | + | {{ii}} Most recent game patches should have addressed this issue. | |
− | + | {{Fixbox|1= | |
− | + | {{Fixbox/fix|Make sure you meet minimum requirements}} | |
− | + | }} | |
− | + | {{Fixbox|1= | |
− | + | {{Fixbox/fix|Verify game cache with steam}} | |
− | + | }} | |
− | + | {{Fixbox|1= | |
− | + | {{Fixbox/fix|Reinstall game}} | |
− | + | }} | |
− | + | {{Fixbox|1= | |
+ | {{Fixbox/fix|Install redistributed DirectX and MSCV Runtime}} | ||
+ | * <code>dxsetup.exe</code> and <code>vcredist_x86.exe</code> located in <code>{{p|game}}\Installer</code>. | ||
+ | }} | ||
===Missing Knight of the Order DLC=== | ===Missing Knight of the Order DLC=== | ||
Line 312: | Line 348: | ||
If your computer has a dual or quad-core processor and you are still encountering this issue, you should check that the game is not being forced to run on a single core. To do this, minimise the game whilst it is running and open the task manager using the keyboard shortcut <code>Ctrl+Alt+Del</code> and go to the 'Processes' tab. Here, find <code>OrcsMustDie.exe</code> in the list of processes and right click it before selecting 'Set Affinity...'. If you are on a dual core system, a box will appear with two processor cores listed - most likely <code>CPU 0</code> and <code>CPU 1</code>. On quad core systems, this list will most likely also include <code>CPU 2</code> and <code>CPU 3</code>. Tick the 'All Processors' box and press OK - the game will now correctly distribute processes amongst all processor cores. | If your computer has a dual or quad-core processor and you are still encountering this issue, you should check that the game is not being forced to run on a single core. To do this, minimise the game whilst it is running and open the task manager using the keyboard shortcut <code>Ctrl+Alt+Del</code> and go to the 'Processes' tab. Here, find <code>OrcsMustDie.exe</code> in the list of processes and right click it before selecting 'Set Affinity...'. If you are on a dual core system, a box will appear with two processor cores listed - most likely <code>CPU 0</code> and <code>CPU 1</code>. On quad core systems, this list will most likely also include <code>CPU 2</code> and <code>CPU 3</code>. Tick the 'All Processors' box and press OK - the game will now correctly distribute processes amongst all processor cores. | ||
+ | |||
+ | ==Other information== | ||
+ | ===Customize orc content of excisting levels=== | ||
+ | Orcs Must Die! has a limited capacity for modding; the developers implemented the ability to be able to customise the content of orc waves for existing levels. To do this, navigate to <code>...\Steam\steamapps\common\orcs must die!\Data\</code>. From here you will need to create a new folder called 'mod', and another folder within it named 'onslaughts'. | ||
+ | |||
+ | By editing the default onslaught files ([http://assets.robotentertainment.com/Orcs-Must-Die/modding/Onslaughts.zip downloadable here]) and putting them in this folder, you can use your custom levels essentially as an override so that the game will load your levels. Note that you should not rename levels when editing them as the game will no longer recognise them. Also of importance is the fact that using these overrides disables leaderboard scoring and statistics for as long as you are using the modified onslaughts. To return the game to its original state after modification, simply delete the contents of the onslaughts folder. | ||
==System requirements== | ==System requirements== |
Revision as of 16:24, 1 June 2014
Developers | |
---|---|
Robot Entertainment | |
Publishers | |
Microsoft Studios | |
Engines | |
Vision | |
Release dates | |
Windows | October 12, 2011 |
Orcs Must Die! | |
---|---|
Orcs Must Die! | 2011 |
Orcs Must Die! 2 | 2012 |
Orcs Must Die! Unchained | 2017 |
Orcs Must Die! 3 | 2021 |
Key points
- Reported to run well even on older machines.[citation needed]
General information
- Orcs Must Die! Wiki - A small wiki for the Orcs Must Die! series
- Official Forums
- Steam Community Discussions
- Steam Users' Forums - For the series
Availability
- All versions require Steam.
Game data
Configuration file(s) location
System | Location |
---|---|
Steam Play (Linux) | <SteamLibrary-folder>/steamapps/compatdata/102600/pfx/[Note 1] |
-
VideoSettings.xml
includes resolution, vsync and MSAA.user.cfg
has to be created by user.
Save game data location
System | Location |
---|---|
Steam Play (Linux) | <SteamLibrary-folder>/steamapps/compatdata/102600/pfx/[Note 1] |
Save game cloud syncing
System | Native | Notes |
---|---|---|
Steam Cloud |
Video settings
Overheating Graphics Card
- There's reports game overheating GPU. Vsync seems to help but some users may prefer not to use it.
Instructions |
---|
Windowed
Instructions |
---|
Input settings
Remapping
Instructions |
---|
Alternative Keyboard Layouts
Instructions |
---|
Audio settings
Localizations
Language | UI | Audio | Sub | Notes |
---|---|---|---|---|
English | ||||
French | ||||
German | ||||
Italian | ||||
Spanish | ||||
Russian | ||||
Japanese | ||||
Polish | ||||
Brazilian Portuguese |
Issues fixed
Black Boxes On Flaming Arrows
- This issue is most likely caused by incompatibility with certain graphics cards. You can avoid this by lowering the graphics detail slider in the games options.
Bladestaff Alt-fire Crash
- Most recent game patches should have addressed this issue. If you are still experiencing this with Nvidia SLI setup try following fix.
Instructions |
---|
"Failed To Correctly Load Data Files", "Failed To Initialise Engine"
- Most recent game patches should have addressed this issue.
Instructions |
---|
Instructions |
---|
Instructions |
---|
Instructions |
---|
Missing Knight of the Order DLC
This issue is most likely to occur with pre-ordered versions of the game, and results in the Knight of the Order DLC not appearing in game. To fix this, go to ...\Steam\appcache\appinfo.vdf
and delete this file before restarting Steam. This file will then automatically be recreated and the DLC should appear in-game.
Object/Unit Placement Glitch
If a machine is below the minimum requirements to run the game then this issue may occur; involving incorrect positioning of many character models and equipment. Often orcs may appear stuck in the ground and their heads will be colliding with the floor mesh. This is most likely to occur on PCs with single-core processors, as the game itself is optimized to distribute animation-related processes to a second core. Without this core the game will not properly render most enemy units, meaning the game is essentially unplayable on single-core systems. The only solution to this is to run the game on a computer which utilises a multi-core processor.
If your computer has a dual or quad-core processor and you are still encountering this issue, you should check that the game is not being forced to run on a single core. To do this, minimise the game whilst it is running and open the task manager using the keyboard shortcut Ctrl+Alt+Del
and go to the 'Processes' tab. Here, find OrcsMustDie.exe
in the list of processes and right click it before selecting 'Set Affinity...'. If you are on a dual core system, a box will appear with two processor cores listed - most likely CPU 0
and CPU 1
. On quad core systems, this list will most likely also include CPU 2
and CPU 3
. Tick the 'All Processors' box and press OK - the game will now correctly distribute processes amongst all processor cores.
Other information
Customize orc content of excisting levels
Orcs Must Die! has a limited capacity for modding; the developers implemented the ability to be able to customise the content of orc waves for existing levels. To do this, navigate to ...\Steam\steamapps\common\orcs must die!\Data\
. From here you will need to create a new folder called 'mod', and another folder within it named 'onslaughts'.
By editing the default onslaught files (downloadable here) and putting them in this folder, you can use your custom levels essentially as an override so that the game will load your levels. Note that you should not rename levels when editing them as the game will no longer recognise them. Also of importance is the fact that using these overrides disables leaderboard scoring and statistics for as long as you are using the modified onslaughts. To return the game to its original state after modification, simply delete the contents of the onslaughts folder.
System requirements
Windows | ||
---|---|---|
Minimum | ||
Operating system (OS) | XP | |
Processor (CPU) | 2 GHz dual core | |
System memory (RAM) | ||
Hard disk drive (HDD) | 5 GB | |
Video card (GPU) | Nvidia Geforce 6800 ATI Radeon x1950 256 MB of VRAM |
Notes
- ↑ 1.0 1.1 Notes regarding Steam Play (Linux) data:
- File/folder structure within this directory reflects the path(s) listed for Windows and/or Steam game data.
- Games with Steam Cloud support may also store data in
~/.steam/steam/userdata/<user-id>/102600/
. - Use Wine's registry editor to access any Windows registry paths.
- The app ID (102600) may differ in some cases.
- Treat backslashes as forward slashes.
- See the glossary page for details on Windows data paths.