Skip to content

aboutflash/StarCitizen-WarthogScript

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

65 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

TM Warthog config script for StarCitizen v3.9.0

A simple Warthog HOTAS setup to match the current SC control schema. The goal is to use as much of the SC default keybindings to minimize the controllers setup ordeal between releases.

Prerequisites

  • You need to have the Thrustmaster T.A.R.G.E.T. software version v3.0.18.328 installed

How to run

  • Download latest release .zip and unzip the contents of it.
    Alternatively check out or download the files under ./script. All of it.
    See what's new in the Release notes.
  • Point your T.A.R.G.E.T. software to run the script directly w/o loading the GUI.
    "C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETGUI.exe" -r E:\StarCitizen-WarthogScript\script\StarCitizen_3.9.x_combined.tmc
    Where the latter path is obviously the location where you've copied the scripts to.
  • Copy the keybindings file from ./sc-settings/mappings into your game directory /USER/controls/Mappings.
  • Import the keybindings in-game:
    • Keyboard -> Keyboard
    • Mouse -> Mouse
    • JoyStick -> JoyStick // virtual Warthog HOTAS
      ... and optional ...
    • JoyStick -> JoyStick (1) // optional Rudder Pedals - if you have some
      IGNORE assignment of the second Joystick if you don't have rudder pedals!
      In that case select JoyStick -> None from drop down.

Import key bindings

Usage advice

Since StarCitizen is not yet able to provide status via an API T.A.R.G.E.T. is not able to detect in which state your ship is. This is especially difficult since StarCitizen keybindings still rely on toggle behaviour. This is cool for Mouse/Keyboard players but brings problems with input devices with flip-switches.

To tackle this problem we have to make some assumptions on the ship's state in order to have fun using the HOTAS. Basically this assumption is, that the ship you are entering is spawned without any systems on. When you as a pilot enter your pilot seat you should take a brief pre-flight check to bring your HOTAS in the right configuration.

  1. Flip all switches to their neutral/default state!
  2. Enter your pilotes seat.
  3. Turn on the POWER switch. - Wait for the ship AI confirmation message
  4. Then turn on ENGINES

Action Mapping / Layout

Here's an overview of the currently mapped functions to the HOTAS buttons and axis. Functional Button/Axis Mapping

Here are also some other variants. The dark ones are perfekt as a reference in typical gaming environments. You can also use them as screen background.

Trouble shooting

In this manual I assume, that the Warthog HOTAS is the only controller you have attached to your PC (besides Rudder Pedals, if you have). If you have trouble loading the keybindings into StarCitizen it may be because the game has registered another Joystick type controller to position 1 of your Joystick slots (1-4).

You have 2 options to solve this issue.

  1. Re-sort your controllers in-game.
    • Open your in-game console: ^
    • enter: i_DumpDeviceInformation.
      See to what internal slots your devices are assigned to.
    • resort joysticks, by example: pp_resortdevices joystick 2 1
      This moves stick 2 to position 1 obviously.
      You have to use the correct numbers matching your machines setup!
  2. Import the HOTAS keybindings to a different slot.
    This requires also to adjust the deadzones for that slot! See manual settings)

If you happen to use TeamSpeak 3 on Windows 10 and find your T.A.R.G.E.T. software to hang or crash once you've loaded Teamspeak, then navigate to C:\Program Files (x86)\Thrustmaster\TARGET\x64\DeviceManagementApp.exe and rename or delete it.

Further reading

  1. CIG documentation on keybinding management 'Create, export and import custom profiles'