Difference between revisions of "Troubleshooting: Games"

From Emperor's Hammer Encyclopaedia Imperia
(update TIE music information, and some cleanup)
(add EHBL information)
 
Line 90: Line 90:
  
 
Nothing to report currently.
 
Nothing to report currently.
 +
 +
==EH Battle Launcher (EHBL)==
 +
 +
===Fails to install battle/file permission issues===
 +
 +
It is recommended to run EHBL with administrative privileges by right clicking the icon and selecting 'Run as administrator'. Although EHBL makes no changes to your system outside of installing your battle files, EHBL writes files to its own installation directory (typically 'C:\Program Files\Darkhill Unlimited\EH Battle Launcher') as well as your game directory which may both be protected locations in modern versions of Windows. (Knowledgeable users can mitigate this by installing both EHBL and the games to non-protected locations in which case EHBL requires no special permissions to function.)
 +
 +
Refer to [[Tactical Manual: Playing custom battles and missions]] for complete EHBL information.
  
 
[[Category:Guides]]
 
[[Category:Guides]]

Latest revision as of 09:26, 24 March 2024

Overview[edit]

This article is to give specific troubleshooting tips for the TC's games. Currently it's focused on the older flight sim games, specifically TIE Fighter, X-Wing vs TIE Fighter, and X-Wing Alliance. It may be expanded to other TC games in the future. NOTE: This article assumes that you have read the TIE Corps New Member Guide's section on Custom Missions and that you're looking for specific troubleshooting tips for the games.

Applicable to XW, TIE, XvT, and XWA[edit]

Game Directories[edit]

Many of the instructions below reference your game directory. The typical directory paths for your games are as follows:

Steam

TIE DOS - C:\Program Files (x86)\Steam\steamapps\common\STAR WARS Tie Fighter\classic
TIE 1995/Collector's CD - C:\Program Files (x86)\Steam\steamapps\common\STAR WARS Tie Fighter\collectors_cd
TIE 1998/Remastered - C:\Program Files (x86)\Steam\steamapps\common\STAR WARS Tie Fighter\remastered
XvT - C:\Program Files (x86)\Steam\steamapps\common\STAR WARS X-Wing vs TIE Fighter
XvT BoP - C:\Program Files (x86)\Steam\steamapps\common\STAR WARS X-Wing vs TIE Fighter\BalanceOfPower
XWA - C:\Program Files (x86)\Steam\steamapps\common\Star Wars X-Wing Alliance
XW - C:\Program Files (x86)\Steam\steamapps\common\STAR WARS X-Wing
GOG

TIE DOS - C:\Program Files (x86)\GOG Galaxy\Games\Star Wars - TIE Fighter (1994)
TIE 1995/Collector's CD - C:\Program Files (x86)\GOG Galaxy\Games\Star Wars - TIE Fighter (1998)
TIE 1998/Remastered - C:\Program Files (x86)\GOG Galaxy\Games\Star Wars - TIE Fighter CD (1995)
XvT - C:\Program Files (x86)\GOG Galaxy\Games\Star Wars - XvT
XvT BoP - C:\Program Files (x86)\GOG Galaxy\Games\Star Wars - XvT\BalanceOfPower
XWA - C:\Program Files (x86)\GOG Galaxy\Games\Star Wars - X-Wing Alliance
XW - C:\Program Files (x86)\GOG Galaxy\Games\Star Wars - X-Wing (haven't personally confirmed this one)

Replace DDraw file[edit]

TIE Fighter with and without updated ddraw.dll. View at full size and inspect the differences on the cargo container.

The flight sims were created a long time ago in a galaxy far, far away and struggle to use newer versions of Direct3D. By replacing these files, you tend to fix a lot of weird issues that the games have. You can install these files using the instructions below:

  1. Click the appropriate link below (see the notes next to the links):
  2. Click the Releases button on the right side of the page. Download the .zip file of the newest version released.
  3. Extract the ddraw.cfg, ddraw.dll, and nopowervr.txt to your game directory and allow them to overwrite any existing files.
  4. You need to repeat this process for every game that you are using, including any different versions you're playing. TIE has three different directories: TIE95, Collector's CD, and Remastered (1998). XvT has two different directions: one for XvT and one for BoP. You would need to repeat these instructions in each, individual game directory for this to take effect.

NOTE: The ddraw.cfg can be opened in a text editor and has multiple options/enhancements that you may find useful. Please read the documentation on the Github page(s) for more information.

TIE Fighter[edit]

Random crashes related to music[edit]

Some members have experienced random crashes in some editions of TIE Fighter that seem to be related to in-game music. If you are experiencing crashes, disabling the music may resolve them. Once you have the game open, hit Esc and turn the Music volume to 0.

X-Wing vs TIE Fighter[edit]

Crash after mission victory[edit]

Missions might crash immediately after you complete a mission and the voice over says "Primary Mission Objectives Complete". This is caused by a bug when playing the mission victory music. To resolve it, disable the in-game music by navigating to the game's directory and opening the Config.cfg file in a text editor like Notepad. Change the value for music and datapad_music to 0, then save your changes.

XvT Disable Music.png

X-Wing Alliance[edit]

Patches Fail to Install[edit]

The ship patches for XWA do not use the EHSP and, instead, install via .bat file. There are a couple of different issues that can occur.

Incorrect Directory[edit]

If you experience the error below when trying to install the patch, this likely means that your patch is in the wrong location. The patches must exist in a specific folder in your game directory to work properly.

XWA Patch Error.PNG

The patches must exist inside the EHPatch folder inside of your game directory. The typical paths used on modern operating systems are listed below:

Steam - C:\Program Files (x86)\Steam\steamapps\common\Star Wars X-Wing Alliance\EHPatch
GOG - C:\Program Files (x86)\GOG Galaxy\Games\Star Wars - X-Wing Alliance\EHPatch

Modify Ship Patch[edit]

Older versions of the patch files had a problem on modern versions of Windows where the Command Prompt window flashed for a second and disappeared without any text showing. If you experience this problem, please ensure that you are using the most recent version of the patch from the Patch Archive.

XWAU/TFTC Custom Mission Too Dark[edit]

In case you are playing any custom missions with XWAU or TFTC installed, it might occur that you can see only very little. Some custom missions have set the RGB backdrop brightness level either to very low values (even 0) or erroneously used this field as descriptor field.

Xwau custom mission backdrop lighting.png

In the example above (screenshot from YOGEME) the backdrop lighting value for red (R) is set 50% (0.5), green (g) is 0% (0.0) and blue is 100% (1.0). If this field is set to very low values (e.g. 0.0 0.0 0.0) or even erroneously is used as a descriptor (e.g. "Fancy Galaxy Backdrop") you can change these values to higher values and you will be able to see.

X-Wing[edit]

Nothing to report currently.

EH Battle Launcher (EHBL)[edit]

Fails to install battle/file permission issues[edit]

It is recommended to run EHBL with administrative privileges by right clicking the icon and selecting 'Run as administrator'. Although EHBL makes no changes to your system outside of installing your battle files, EHBL writes files to its own installation directory (typically 'C:\Program Files\Darkhill Unlimited\EH Battle Launcher') as well as your game directory which may both be protected locations in modern versions of Windows. (Knowledgeable users can mitigate this by installing both EHBL and the games to non-protected locations in which case EHBL requires no special permissions to function.)

Refer to Tactical Manual: Playing custom battles and missions for complete EHBL information.