[section=General Information] [big][big]Introduction[/big][/big] Getting Up recognizes very few controllers automatically, if you have a controller that it won't get recognized by the game then this guide will aid you to add support for your controller in order to work with the game.
The file you need to edit is in this location: [small]%Getting_Up_Installation%\engine\binds_pc.cfg[/small]
[small]%Getting_Up_Installion%[/small] = the location of your game installed. The default is at [small]"C:\Program Files (x86)\Atari\Marc Ecko's Getting Up - Contents Under Pressure"[/small].
The files contents are splitted into 3 sections:
- 1. Keyboard input binding
- 2. Controller input binding
- 3. Input description
[big][big]1. Keyboard input binding[/big][/big] The first section begins at the start of the file with the comment lines: [quote]# --------------------------------------------------
KEYBOARD CONFIG
--------------------------------------------------[/quote]
You can change the input here if you want some better alternative for keyboard input, but it's probably unnecessary.
[big][big]2. Controller input binding[/big][/big] The second section is splitted into many parts for each controller configuration. Each part is for each controller configuration. You can change the mapping of the first one:
CONTROLLER 0 (inputstream 0) Updated: 6/14/04[/quote]
Each line is having something like this: [quote]addbind 0 COMMAND_FORWARD CONTROLLER 0 AXIS_Y 0 1 #-- MOVEMENT -- LA[/quote] Explanation:[quote]addbind: There is setbind and addbind, the 1st one sets the bind for first time and 2nd is used in binding the same command into multiple inputs. Because we use the inputstream 0 we have already set the binds for the first time at the keyboard binding section, so we use addbind to add the controller's input too. 0: Which inputstream to use, not sure what it actually affects, leave it unaltered. COMMAND_FORWARD: Here goes which game's input to bind with the controller (COMMAND_FORWARD binds the player's forward input). CONTROLLER: Here is what type of input it should receive, it can receive KEYBOARD, MOUSE, and CONTROLLER. 0: Which controller to bind, on this case the first one. AXIS_Y: Which button to bind from the controller, on this case it's the Y Axis of the controller or the "up-down" axis from the joystick. 0 1: When using axis to bind input you need to specify which is the range of the axis's is bound to the command. #-- MOVEMENT -- LA: Anything following a # symbol is a comment, and it doesn't affect the configuration. You can edit it, remove it, it doesn't matter.[/quote]
[big][big]3. Input description[/big][/big] This section is optional. It describes which the controller's inputs are.
[section=Preconfigured files] Here are some ready to apply binds_pc.cfg files configured for the most known controllers.
