Supported Controllers / How to Help Add New Ones

[TonyDanza]

Supported Controllers

Standard

• Mouse
  
• Keyboard

Gamepads

• All XInput controllers
  
• XBox 360 and One
  
• Logitech F310, F510, and F710
  
• Buffalo Classic
  
• 8Bitdo NES30 Pro, SFC30, and SNES30
  
• Executioner X
  
• GameCube Controller (MAYFLASH Adapter, USB Adapter)
  
• GameStick
  
• Hama Black Force
  
• Level Up Black Hawk
  
• MaxFire Blaze5
  
• Moga Pro
  
• Natec Genesis P44
  
• Nexus Player
  
• NVIDIA Shield
  
• OUYA Controller
  
• PlayStation 2, 3, and 4
  
• Speedlink Strike
  
• SteelSeries Free
  
• Xiaomi Controller

VR

• Oculus Touch
  
• Vive Wands
  
• Vive Cosmos
  
• WMR Controllers
  
• Valve Index
  
• Other Steam VR controllers should work just fine, but you may want to remap the default bindings in the in-game control menu.

Joysticks, Throttles, Pedals, Foot Controls

• 3DRudder
  
• CH Fighterstick
  
• CH Combatstick
  
• CH Pro Throttle
  
• CH Pro Pedals
  
• Logitech WingMan
  
• Logitech Extreme 3D
  
• Microsoft Sidewinder Force Feedback 2 (input only, no force)
  
• MFG Crosswind V2
  
• Saitek AV8R
  
• Saitek X45
  
• Saitek X52 and X52 Pro
  
• Saitek X55 Rhino Stick and Throttle
  
• Saitek X56 Rhino Stick and Throttle
  
• Saitek Pro Flight Rudder Pedals
  
• Saitek Pro Flight Quadrant
  
• Thrustmaster T16000M and TCA Sidestick Airbus
  
• Thrustmaster TWCS Throttle
  
• Thrustmaster T.Flight Hotas X, 4, and One
  
• Thrustmaster Warthog Stick
  
• Thrustmaster Warthog Throttle
  
• Thrustmaster Pendular Rudder
  
• Thrustmaster T-Rudder
  
• VKB Sim Gunfighter Modern Combat Pro joystick
  
• VKB T-Rudders Mk.IV
  
• VKB Gladiator NXT
  
• VPC WarBRD
  
• VPC Mongoos T-50CM2 Throttle
  
• BU0836X Interface

Adding Support for New Controllers

1. Download the Control Test program from our website: http://voxmachinae.com/tools/controltest.zip
   
2. Extract the .zip file to a folder.
   
3. Run ControlTest.exe
   
4. Each controller will be displayed in its own column, with Button0-19 and Analog0-19 listed underneath.
   
5. The first piece of information we need is the exact name of the controller, this will appear in red text like "(Unrecognized) Name of Controller".
   
6. Press each button on the controller and note which button number lights up. For example you might press the trigger on a joystick and "Button0" will light up. Create a list with the button number and a short description of the button, like:
   
   • Button0 = trigger
     
   • Button1 = red button on top
     
   • Button2 = button by pinkie finger
   Note that the game currently only supports the first 20 buttons on each controller.
   
7. Press each analog input and note which analog axis lights up and the value when it is pressed in each direction. Also important is the resting position. Make a list, for example:
   
   • Analog0 = joystick (-1 left, 0 resting, 1 right)
     
   • Analog1 = joystick (-1 forward, 0 resting, 1 back)
     
   • Analog2 = foot pedal (-1 back, -1 resting, 1 forward)
8. It is unusual for a controller to skip a number, for example to have buttons 0 to 5, and 7 to 10, but no number 6. Try clicking down on thumbsticks to find the missing buttons.
   
9. Make a note of any special or strange behaviour of your controller.
   
10. Post your results here and we will get support added as soon as we can!

[Sevrin]

Unrecognized Controller: VPC Stick WarBRD

Button 0 Main trigger stage 1
Button 1 Bomb Release
Button 2 Pinky nose wheel steering
Button 3 Pinky Paddle button
Button 4 Single push button below hat switches
Button 5 Main trigger stage 2
Button 6 Left POV hat up
Button 7 Left POV hat right
Button 8 Left POV hat down
Button 9 Left POV hat left
Button 10 scroll wheel below hat switch - up
Button 11 scroll wheel below hat switch - press
Button 12 scroll wheel below hat switch - down
Button 13 Left POV hat switch - depress
Button 14 DLC thumb switch forward
Button 15 DLC thumb switch right
Button 16 DLC thumb switch down
Button 17 DLC thumb switch left
Button 18 DLC thumb switch - depress
Button 19

Analog 0 Stick roll
Analog 1 Stick pitch
Analog 2 right POV hat switch - left / right
Analog 3 right POV hat switch - up / down
Analog 4
Analog 5
Analog 6
Analog 7
Analog 8
Analog 9
Analog 10
Analog 11
Analog 12
Analog 13
Analog 14
Analog 15
Analog 16
Analog 17
Analog 18
Analog 19


Thanks in advance!

[Brayden]

Nguyên văn bởi Sevrin:

Unrecognized Controller: VPC Stick WarBRD

Button 0 Main trigger stage 1
Button 1 Bomb Release
Button 2 Pinky nose wheel steering
Button 3 Pinky Paddle button
Button 4 Single push button below hat switches
Button 5 Main trigger stage 2
Button 6 Left POV hat up
Button 7 Left POV hat right
Button 8 Left POV hat down
Button 9 Left POV hat left
Button 10 scroll wheel below hat switch - up
Button 11 scroll wheel below hat switch - press
Button 12 scroll wheel below hat switch - down
Button 13 Left POV hat switch - depress
Button 14 DLC thumb switch forward
Button 15 DLC thumb switch right
Button 16 DLC thumb switch down
Button 17 DLC thumb switch left
Button 18 DLC thumb switch - depress
Button 19

Analog 0 Stick roll
Analog 1 Stick pitch
Analog 2 right POV hat switch - left / right
Analog 3 right POV hat switch - up / down
Analog 4
Analog 5
Analog 6
Analog 7
Analog 8
Analog 9
Analog 10
Analog 11
Analog 12
Analog 13
Analog 14
Analog 15
Analog 16
Analog 17
Analog 18
Analog 19


Thanks in advance!

This will be included in the next update thank you for posting!

[Not A Banana]

Nguyên văn bởi TonyDanza:

Nguyên văn bởi Rick Mick:

I see this line when checking the log " VKB-Sim Gladiator NXT R " there seems to be two spaces on either side

We only checked for one space on each side. :(
There will be a small bug patch at some point next week and I'll make sure it includes a check for more spaces.

Did this ever go through? I'm having the same problem, joystick is undetected because of spaces

[Dirkson]

Heyo!

I think I could use support for VPC WarBRD-D. From an electronics perspective, I believe it's identical to the non-D variety. There's just some physical hunks of metal that are different.

But trying to support VPC bases like this doesn't make a lot of sense. Each VPC base could be connected to one of several joysticks, and their configuration software allows users to edit and create arbitrary numbers of axis and buttons that the computer sees. There's actually no way to operate them without using these virtual buttons.

Basically, each VPC base user will probably have their own mapping of what physical button they press to make 'button 1' show up in software.

I'm not 100% sure what you're doing here, but I think it might make sense to just give most VPC bases ( VPC WarBRD, VPC WarBRD-D, VPC MongoosT-50CM3, and VPC MongoosT-50CM2) very boring, generic button/axis names/numbers and let the users figure out the rest. Trust me, we're pretty used to it.

This is less true of other VPC offerings, like the VPC MongoosT-50CM3 Throttle. You can still customize it to have an arbitrary number of buttons, but it does actually have a default layout. (Though it might be good to fall back to a "generic numbered" mode if the throttle has the 'wrong' number of buttons, since users can and do add/remove buttons.)

TL;DR: VPC joysticks are weird. Can we just get numbered buttons and axis instead of trying to map things to POV hats and whatnot?

Cheers!

[Our Lady of Fraudulence]

I'm also having issues with my VKB gladiators (left and right). The button layout is basically the same as the others here, but it's reporting a different name than those listed in the thread. " VKBsim Gladiator EVO L".

VKB often changes names of their devices with different firmware versions. I have to agree with Dirkson that a more general purpose binding mode (even if it's an advanced or unsupported option!) is necessary. My Gladiators have the SCG grips on them, but you can get KG12 and F14 grip modules as well, and they may release more in the future. As it stands, you have to manually add support every few firmware versions and for every grip in the Gladiator family. There's also the Gunfighter family, which has the same grips as the Gladiator plus two more, with similar firmware name change occurrences.

On top of all of that, VKBDevConfig means that no two users will necessarily have identical layouts -- for instance, my SCGs have a "rapid fire trigger" that uses buttons 20 and 21 (from index 0), and I'll need to change those for use in VM, so my layout will be different from most everyone else's layout. This, again, is similar to Dirkson's concern with Virpil controls.

A simple, unsupported, "use at your own risk you heathen" option with no restrictions is the best solution to enthusiast tier controls, and, as a bonus, will support home-built HOTAS/HOSAS systems natively as well (which there are plenty of!)

[Misschief]

VKBsim Gladiator EVO OT L and VKBsim Gladiator EVO OT R are just unrecognized and follow the same pattern as any other Gladiator EVO.

Perhaps implementing the method used in the tester into the game might be the call?

[Not A Banana]

Yeah I don't really understand why support relies on exact match strings for the device name. Why not just let us bind input from any device?

[El Duderino]

Hey SpaceBrayden,

I'm also not able to get the VKB Gladiator EVO R to work, here's the text from the player.log file. Looks like two spaces before and two spaces after.

'Unrecognized Controller: VKBsim Gladiator EVO R '

Any chance you can work it in on the next update?
Thanks!

[El Duderino]

It's the same setup as this comment quoted below, the only difference I see is two spaces before, sorry SB, what a pain!

Tried to simply modify the name in the windows registry, but that doesn't seem to be where the game is grabbing it from.

All inputs register the same except the mini stick digital mode (-1, 1) that was previously on Analog 8 and 9 is now assigned to analog 6 (yaw) and analog 7 (pitch).
The analog mode of the mini-stick is still on Analog 3 & 4 and that's the mode I would expect you would want, so this isn't a super important change.

Nguyên văn bởi Ducks:

Nguyên văn bởi Ducks:

Unrecognized Controller: VKBsim Gladiator EVO R

Button 0 Main trigger stage 1
Button 1 Main trigger stage 2
Button 2 A2 Red Button
Button 3 B1 Upper right side button
Button 4 D1 Pinky button
Button 5 A3 up
Button 6 A3 right
Button 7 A3 Down
Button 8 A3 left
Button 9 A3 click-press
Button 10 A4 up
Button 11 A4 right
Button 12 A4 down
Button 13 A4 left
Button 14 A4 click-press
Button 15 C1 up
Button 16 C1 right
Button 17 C1 down
Button 18 C1 left
Button 19 C1 click

Analog 0 Stick Yaw
Analog 1 Stick pitch
Analog 2 base center rotary
Analog 3 Alt mode mini stick yaw
Analog 4 Alt mode mini stick pitch
Analog 5 Z axis Stick twist
Analog 6
Analog 7
Analog 8 mini stick yaw
Analog 9 mini stick pitch
Analog 10
Analog 11
Analog 12
Analog 13
Analog 14
Analog 15
Analog 16
Analog 17
Analog 18
Analog 19

Unrecognized buttons and analogs: 2nd trigger both forward and back, F1 button, F2 Button, F3 button, Sw 1 base return encoder on the left, En 1 base continious encoder on the right.

Note that pressing mini stick switches between alt mode (red light on) and normal mode.

positive for stick and mini stick are right and negative are left (1, -1)
Forward is negative back is positive on on main stick (-1, 1)
Forward is positive on Mini Stick back is negative (1, -1)

[TwinBeat]

VKB S-TECS MINI PLUS

(Unrecognized) S-TECS MODERN THROTTLE MINI PLUS

Analog 0 - Throttle (has 2 Throttles which can be physically combined. Therefore 0 and 1
Analog 1 - Throttle
Analog 0+1 - 0 to 1 Throttle Forward
Analog 0+1 - 0 to -1 Throttle Backward

Analog 2 - Small Throttle at the Right side low
Analog 2 - +1 Turn Right / -1 Turn Left (0 at Middle Position)

Analog 3 and 4 - ♥♥♥♥♥♥ Hat Right Top
Analog 3 - +1 Push Forward / -1 Push Backwards
Analog 4 - +1 Push Down / -1 Push Up


Button 0 - Button Round White
Button 1 - Button Start Red
Button 2 - Selector White Pos 1
Button 3 - Selector White Pos 2
Button 4 - Selector White Pos 3
Button 5 - Selector White Pos 4
Button 6 - Selector White Pos 5
Button 7 - Round Selector Base - Turn Left
Button 8 - Round Selector Base - Turn Right
Button 9 - Button Safe
Button 10 - Key 1 on Base
Button 11 - Key 2 on Base
Button 12 - Key 3 on Base
Button 13 - Key 4 on Base
Button 14 - Button Armed
Button 15 - Round Selector Base - Push Up
Button 16 - Round Selector Base - Push Down
Button 17 - Round Selector Base - Push Right
Button 18 - Round Selector Base - Push Left
Button 19 - Round Selector Base - Press Selector

[Beegrene]

Just wanted to chime in and say that I bought this game just literally because of the HOTAS support. I just got a fancy new HOTAS and want some games to try it with. Thank you, devs, for implementing HOTAS support.

[Velrisias]

You can remove the index controllers from this list, grip isn't registering in your game