Jump to content

PCGamingWiki will use a Single Sign On (SSO) system to bridge wiki and forum accounts which is ready for testing. You may login using the 'Login with PCGamingWiki' button on both the wiki and the forum, which will soon be the only option. If you have any issues please message Andytizer on Discord.

Gamepad Files (Republic Commando) 1.00


About This File

In this zip folder, will have the files and the instructions on how to get Star Wars: Republic Commando (mostly) working with a Xbox 360 controller (note: Xinput Plus was used for some of these files). It also includes a control guide for Republic Commando on a Xbox 360 controller.

 

 

---------From the Readme---------

 

Readme by: Coates87 (on PC Gaming Wiki)

 

How to enable Xbox 360 controller for Republic Commando-

 

 

1) Editing User.ini

 

To enable joystick support for Republic Commando, first open up the User (joysitck).ini file (in notepad, preferably Notepad++) that is in the same directory as this readme file and copy all of the text. Then create a user profile (example: John) in the game and exit. After that, go to the game's save file directory (<path-to-game>\GameData\Save) and open your profile folder (example: Profile_John). Then open the User.ini file in that folder and paste the text from the User (joysitck).ini file to this file and save it.

 

For more information on how the User.ini reads your joystick, scroll to "3) User.ini Details"

 

2) Final Touches

 

After all of that, make sure to go into this directory (<path-to-game>\GameData\System) and open up System.ini and do a text search for "UseJoystick" and make sure it is equal to "True" and save the file. Place the files that is in the "Xinput Plus Files" folder (but not the folder itself) in same directory that has the game's executable (<path-to-game>\GameData\System).

 

Close those ini files and enjoy.

 

3) User.ini Details (optional)

 

Here are the lines in the User.ini that is being add to the added (This applies to all Unreal 2 engine games, including UT 2004):

 

--Gamepad Axes

JoyX=Axis aStrafe Speed=950 DeadZone=9500.0 ; Left Stick Left/Right

JoyY=Axis aBaseY Speed=-900 DeadZone=49.9 ; Left Stick Up/Down

JoyZ= (Represents LT & RT for Xinput controllers)

JoyR=Axis aBaseX Speed=690 DeadZone=9500.0 ; Right Stick Left/Right (for Xinput controllers)

JoyV=

JoyU=Axis aLookUp Speed=560 DeadZone=9500.0 ; Right Stick Up/Down (for Xinput controllers) (Put Invert=-1 to remove inversion)

 

For this game only, the DeadZone doesn't for some reason, but for most other Unreal 2 engine games (here on known as U2e) the deadzone portion of the joystick is where no action is recorded. The larger the deadzone, the further you have to push an analog stick's axis to do something. Speed just controls how sensitive that action is to the analog stick's axis.

 

--Explaination of Axis Types

"Axis aStrafe" controls analog-based Strafing (moving left and right)

"Axis aBaseY" controls analog-based Moving Forward and Backward

"Axis aBaseX" controls analog-based Horizontal Looking (sometimes called aTurn)

"Axis aLookUp" controls analog-based Vertical Looking

"Axis aUp" controls analog-based Z motions (postive for Jumping / negative for crouching)

 

--Gamepad Buttons (for some reason Rupublic Commando only listens to these buttons in this .ini file)

GameRStick=SwitchWeapon 2

GameLStick=SwitchWeapon 5

GameBack=SwitchWeapon 3

GameStart=SwitchWeapon 1

GameDRight=Fire | onrelease StopFire

GameDLeft=ThrowGrenade

GameDDown=AltFire

GameDUp=Toggle bDuck

GameRTrig=ShowMenu

GameLTrig=ShowGameStats

GameWhite=SwitchGrenade 6

GameBlack=ToggleHeadlamp

GameY=Jump

GameX=ForceReload

GameB=fov 0

GameA=Use | CommandFormUp | CommandSearchDestroy | CommandRecall | CommandSecurePosition | onrelease StopUse

 

You probably notice that there are several other mapped to "GameA". A neat feature of the Unreal 1 & 2 engine is that you can bind several actions and aliases (more on that below) to a single button or key, provided that each action is separated by a "|".

 

--Gamepad Aliases (custom commands)

Aliases[29]=(Command="set input GameLStick Recall | onrelease set input GameLStick SwitchWeapon 5",Alias="CommandRecall")

Aliases[30]=(Command="set input GameRStick Search & Destroy | onrelease set input GameLStick SwitchWeapon 2",Alias="CommandSearchDestroy")

Aliases[31]=(Command="set input GameBack Form Up | onrelease set input GameBack SwitchWeapon 3",Alias="CommandFormUp")

Aliases[32]=(Command="set input GameStart Secure Position | onrelease set input GameStart SwitchWeapon 1",Alias="CommandSecurePosition")

 

Now here is are some aliases (custom made commands) that I've made which will the user (when called from an assigned button like above) to do very differnt things than what you normally can do in the game. In the Gamepad Aliases for Alias # 29, I've created an alias that, when active, will set "DPad Down" (for some is read as "GameLStick" in the file) to issue the Recall command. Then I place a divider (|) and have DPad Down set back to "SwitchWeapon 5" which is the Secondary weapon and named the alias "CommandRecall".

 

So to put in laymen's terms, pressing the down dpad button will have me equip the Secondary Weapon, but when I hold the A button (GameA), I can tell my comrades to retreat with the Recall command.




User Feedback

Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Who's Online   1 Member, 0 Anonymous, 286 Guests (See full list)

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Member Statistics

    4,574
    Total Members
    3,870
    Most Online
    nclok1405
    Newest Member
    nclok1405
    Joined
×