GTA 5 PC Joystick support?

[Starfire273]

Title says it all, I wonder if GTA 5 will Support a Joystick. I always found flight controls to be natural with a proper Joystick.

I think I might get it done with mouse and Keyboard, but a Joystick would be preferable for me.

And I don't want to use a Gamepad. I have two of those, but still.

[Tsoprano]

I have my x52 working with the x360ce but it refuses to work in the game, i think the problem lies in not being able to tie the keyboard binds to a controller while still using keyboard and mouse settings. I'll experiment further.

[vacuum cleaner]

anyone get any luck with this?

[kurgen]

I have my ol' trusty Sidewinder 2 waiting to be used... come on R*, we know you can do this, why so stubbornly anti-analog?

[Tsoprano]

It seems impossible with the x360ce. It is not because of the emulator, it is because you cannot map the controls to a controller without using an actual controller. Shame because it is very horrible with a mouse, and worse with a keyboard.

[rib]

This is terrible, such a variety of aircraft, with splendid number of ground targets, nice cockpit view and NO JOYSTICK SUPPORT... wow... just wow, it is like giving a blind man a 4k 60fps movie dvd on his birthday

[Tsoprano]

This might be good news on the x360ce front.

Squall-Leonh@rt said: ↑

we will have the combiner settings implemented soonish which will let you combine multiple controller devices into one xinput device.

Which means we can tie in our joysticks along with other devices (for me it is a g27) into one input device. It should be possible anyway.

[Julius]

Wait, what?

Having no problems at all getting a Logitech Driving Force GT to work with x360ce.

If it's an issue with the x360ce configuration tool and 64-bit, they released a new version on the 19th that makes it easy as. Don't see why a joystick wouldn't work.

[kurgen]

Hmmm... must investigate when I get home from work. Fanx.

[Tsoprano]

Originally posted by Sephyrius:

Wait, what?

Having no problems at all getting a Logitech Driving Force GT to work with x360ce.

If it's an issue with the x360ce configuration tool and 64-bit, they released a new version on the 19th that makes it easy as. Don't see why a joystick wouldn't work.

I agree. I have my x52 working perfectly in the x360ce app, programmed and everything just fine. When i go in game, nothing absloutely nothing. And i know the app is loading because i am using my g27 for driving. Got to be something i am missing here, hookmode maybe i dunno.

[Julius]

Originally posted by Tsoprano:

Originally posted by Sephyrius:

Wait, what?

Having no problems at all getting a Logitech Driving Force GT to work with x360ce.

If it's an issue with the x360ce configuration tool and 64-bit, they released a new version on the 19th that makes it easy as. Don't see why a joystick wouldn't work.

I agree. I have my x52 working perfectly in the x360ce app, programmed and everything just fine. When i go in game, nothing absloutely nothing. And i know the app is loading because i am using my g27 for driving. Got to be something i am missing here, hookmode maybe i dunno.

I think that it is able to register m/k + 1 controller, not multiple. So you'd have to choose between the G27 or joystick, not both.

[Tsoprano]

Hmm seems that way. It has slots for 4 controllers though, pad 1-4 etc. If they do incorporate combining, i might be golden!

[-Cactus18kt-]

MIGHT FIX. MIGHT NOT..

Create or edit 'gamepad.xml' to get *some* axis devices detected &/or configured.
[Except YAW ofc wont be analog, by any method. Map an A-D axis in software]

> Backup 'gamepad.xml' before you start, if it exists. Look in the ..docs/rockstar/gta/profiles/controls folder

> Find & use YOUR device's PID and VID numbers in place of XXXX & YYYY respectively, within the template below.

> Paste into. Your gamepad.xml should now look similar to this:

----------------------------------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>

<rage__ControlInput__Gamepad__DefinitionList>
<Devices>
<Item key="XXXXYYYY-0000-0000-0000-504944564944">
<Definitions>
<Item>
<PadParameter>IOM_AXIS_LX_LEFT</PadParameter>
<JoystickParameter>IOM_JOYSTICK_AXIS1</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_AXIS_NEGATIVE</JoystickSource>
</Item>
<Item>
<PadParameter>IOM_AXIS_LX</PadParameter>
<JoystickParameter>IOM_JOYSTICK_AXIS1</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_AXIS</JoystickSource>
</Item>
<Item>
<PadParameter>IOM_AXIS_LX_RIGHT</PadParameter>
<JoystickParameter>IOM_JOYSTICK_AXIS1</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_AXIS_POSITIVE</JoystickSource>
</Item>
<Item>
<PadParameter>IOM_AXIS_LY_DOWN</PadParameter>
<JoystickParameter>IOM_JOYSTICK_AXIS2</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_AXIS_POSITIVE</JoystickSource>
</Item>
<Item>
<PadParameter>IOM_AXIS_LY</PadParameter>
<JoystickParameter>IOM_JOYSTICK_AXIS2</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_AXIS</JoystickSource>
</Item>
<Item>
<PadParameter>IOM_AXIS_LY_UP</PadParameter>
<JoystickParameter>IOM_JOYSTICK_AXIS2</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_AXIS_NEGATIVE</JoystickSource>
</Item>
<Item>
<PadParameter>L2</PadParameter>
<JoystickParameter>IOM_JOYSTICK_AXIS7</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_AXIS_POSITIVE</JoystickSource>
</Item>
<Item>
<PadParameter>R2</PadParameter>
<JoystickParameter>IOM_JOYSTICK_AXIS7</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_AXIS_NEGATIVE</JoystickSource>
</Item>
</Definitions>
</Item>
</Devices>
</rage__ControlInput__Gamepad__DefinitionList>
----------------------------------------------------------------------------------------------------------------------

The template example maps the basic X, Y and THROTTLE axis' to a [Logitech C215046D] flight stick used in testing. Other players' devices may have differing axis/button numbers eg. the 'AXIS7' may be AXIS4 etc, on YOUR device.

Test it ^ before bothering with next section
> Fire up the game and try those three axis'. Buttons will not work yet.
> Make note of any inversions or problems for later edit.

If test worked 100% (which it probably wont unless same Logitech is used), you can add the remaining or desired BUTTON <items> ..which again a recommended layout could differ per device model.
> Shove some of the ITEM entries in the .xml (any function can be omitted, but not duplicated)
> Replace the numbers with ones corresponding to your hardware's buttons, blabla.


Remaining mappings:
----------------------------------------------------------------------------------------------------------------------

<Item>
<PadParameter>RDOWN</PadParameter>
<JoystickParameter>IOM_JOYSTICK_BUTTON1</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_BUTTON</JoystickSource>
</Item>
<Item>
<PadParameter>RRIGHT</PadParameter>
<JoystickParameter>IOM_JOYSTICK_BUTTON8</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_BUTTON</JoystickSource>
</Item>
<Item>
<PadParameter>RLEFT</PadParameter>
<JoystickParameter>IOM_JOYSTICK_BUTTON2</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_BUTTON</JoystickSource>
</Item>
<Item>
<PadParameter>RUP</PadParameter>
<JoystickParameter>IOM_JOYSTICK_BUTTON3</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_BUTTON</JoystickSource>
</Item>
<Item>
<PadParameter>L1</PadParameter>
<JoystickParameter>IOM_JOYSTICK_BUTTON9</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_BUTTON</JoystickSource>
</Item>
<Item>
<PadParameter>R1</PadParameter>
<JoystickParameter>IOM_JOYSTICK_BUTTON10</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_BUTTON</JoystickSource>
</Item>
<Item>
<PadParameter>START</PadParameter>
<JoystickParameter>IOM_JOYSTICK_BUTTON5</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_BUTTON</JoystickSource>
</Item>
<Item>
<PadParameter>SELECT</PadParameter>
<JoystickParameter>IOM_JOYSTICK_BUTTON7</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_BUTTON</JoystickSource>
</Item>
<Item>
<PadParameter>L3</PadParameter>
<JoystickParameter>IOM_JOYSTICK_BUTTON6</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_BUTTON</JoystickSource>
</Item>
<Item>
<PadParameter>R3</PadParameter>
<JoystickParameter>IOM_JOYSTICK_BUTTON12</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_BUTTON</JoystickSource>
</Item>
<Item>
<PadParameter>LUP</PadParameter>
<JoystickParameter>IOM_POV1_UP</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_POV</JoystickSource>
</Item>
<Item>
<PadParameter>LDOWN</PadParameter>
<JoystickParameter>IOM_POV1_DOWN</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_POV</JoystickSource>
</Item>
<Item>
<PadParameter>LLEFT</PadParameter>
<JoystickParameter>IOM_POV1_LEFT</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_POV</JoystickSource>
</Item>
<Item>
<PadParameter>LRIGHT</PadParameter>
<JoystickParameter>IOM_POV1_RIGHT</JoystickParameter>
<JoystickSource>IOMS_JOYSTICK_POV</JoystickSource>
</Item>

----------------------------------------------------------------------------------------------------------------------


<PadParameter> is the native command to be emulated (Xbog controller function)
<JoystickParameter> is where on new device this binds (guess and edit, guess and edit)
<JoystickSource> defines the type of input. (beware Axis vs Sliders. ilold)


The <PadParameter> value refers to:
- DPad functions denoted LLEFT, LRIGHT, LUP, LDOWN
- A, B, X ,Y denoted RDOWN, RRIGHT, RLEFT, RUP respectively

R1, R2, L1, L2, L3, R3, SELECT & START are self explanatory.



Other:
- Many axis settings in the game menu will still be active (inverts etc)
- Check aircraft throttles are in deadzone while on foot etc : s
- Further input devices can be added to the file as..:

------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>

<rage__ControlInput__Gamepad__DefinitionList>
<Devices>
<item key="AAAABBBB-000...">
<Definitions>
<item>
<PadParameter>...................</PadParameter>
<JoystickParameter>.................</JoystickParameter>
<JoystickSource>..................</JoystickSource>
</item>
<Definitions>
</item>
<item key="CCCCDDDD-000...">
<Definitions>
<item>
<PadParameter>...................</PadParameter>
<JoystickParameter>.................</JoystickParameter>
<JoystickSource>..................</JoystickSource>
</item>
<Definitions>
</item>
</Devices>
</rage__ControlInput__Gamepad__DefinitionList>
------------------------------------------------------------------

..but *appear* to be limited to accepting only commands not already emulated on any device. This might or might not, be useful for players with pedals.

[-Cactus18kt-]

kk forum has fkd my meticulous formatting. GL understanding any of that

[Bad 💀 Motha]

Should work; I tried these below in GTAV works fine:
- Xbox 360 Wired Controller (as well as Wireless via MS USB Wireless Receiver)
- XboxOne Controller
- Logitech WingMan Extreme Digital 3D Joystick w/ Throttle
- Microsoft SideWinder Precision Steering Wheel w/ Pedals

[WickedCrispy TTV]

Glad I found this. I was going to run out and get a flight stick just for this game but I guess I'm stuck behind this ♥♥♥♥♥♥ stumbling block. What I don't get is the missions and flight school medals require extreme precision. The controls allow the precision if you use a 360 game pad. The thumbsticks have range the way a joystick would.

The issue is I'm on a PC. If I'm going to be stuck piloting flying vehicles that require extreme precision I should be allowed to use the instrument required, not jailed behind a crappy substitute. I don't play shooters with thumbsticks because auto-aimbotting is for pansies and I feel like a retarded 8 year old. If the flight controls were more arcade-style instead of actually realistically tying each control surface to a keybind I wouldn't care, but this is ♥♥♥♥♥♥♥♥♥.

Honestly, trying to gold medal collecting the 30 flags and the one where you have to stick as close to the ground as possible with a keyboard can suck my anus dry.