Great! Thanks.
I’ve just had an idea… I think it could be really useful to have one key or axis do something different depending on whether flight assist was on or off. This could be specified by another attribute in the XML.
Eg:
<Input Event = "ShipZ" Keys = "Joystick0Axis6" Type = "Axis" FlightAssist="off" />
<Input Event = "TargetSpeed" Keys = "Joystick0Axis6" Type = "Axis" FlightAssist="on" />
I can imagine plenty of other uses, eg the W and S keys.
What do you think @INovaeFlavien?
It starts to get pretty complicated, first of all because the input / mapper doesn’t know anything that is game-specific ( it’s part of the engine, not the game ), and secondly because it’ll make the GUI menu / window ( when we’ll implement it ) pretty complicated. I’m afraid it’ll scare first time users…
Interesting. So the game registers events with the engine, and the engine maps the inputs onto the events? Or something like that?
I imagine the easiest to implement would be having the game listen for two more events for each existing one: ShipZ_FAon and ShipZ_FAoff, TargetSpeed_FAon, etc.
However, it sounds like the most consistent with your current architecture might be to have alternate input modes handled by the engine that the game doesn’t even have to know about.
<CycleInputScheme Keys = "Space" />
<InputSchemes>
<InputScheme Id="A">
<Input Event = "ShipZ" Keys = "Joystick0Axis6" Type = "Axis" />
<Input Event = "ShipForward" />
<Input Event = "ShipBackward" />
<Input Event = "ShipX" />
<Input Event = "ShipLeft" Keys="Joystick0Button11" />
<Input Event = "ShipRight" Keys="Joystick0Button13" />
<Input Event = "ShipY" />
<Input Event = "TargetSpeed" />
<Input Event = "ToggleFlightAssist" Keys = "Space" />
etc
etc
</InputScheme>
<InputScheme Id="B">
<Input Event = "ShipZ"/>
<Input Event = "ShipForward" Keys = "W" />
<Input Event = "ShipBackward" Keys = "S" />
<Input Event = "ShipX" />
<Input Event = "ShipLeft" Keys="Joystick0Button11" />
<Input Event = "ShipRight" Keys="Joystick0Button13" />
<Input Event = "ShipY" />
<Input Event = "TargetSpeed" Keys = "Joystick0Axis6" Type = "Axis" />
<Input Event = "ToggleFlightAssist" Keys = "Space" />
etc
etc
</InputScheme>
</InputSchemes>
I’ve intentionally used Space to toggle input scheme as well as toggle flight assist so that they switch at the same time, however you could obviously use different keys.
I’m sure an intuitive GUI can be designed, just ask your community!
It may be worth it to have the GUI simple but add support for those who know how to make further changes directly in the xml files.
I tried with a X-box one controller and a Logitech Extreme 3D Pro. They were both detected they both
did not seem to work exactly right. Now my key bindings and mouse do not seem to be correct.
[Q] and [A] have switched.
How do you go in and set the key binds for key board and the HOTAS and please make an example so that
even I can follow what to do. And not mess it up !
Xbox controllers are supported by default, just use the gamepad settings or use this profile which I very like:
To change keybindings you have to edit your custom keybindings xml file with a text editor, the values are self explainatory. You can also use the detect input tool which is now somewhere in the games folder. I hope that helps.
thanks ill give it a try.
Is this workaround still required or does it work now? The program mentioned in this thread - Universal Joystick Remapper - is no longer available.
Speaking of joysticks, we’ve detected a conflict bug between multiple devices that was introduced a couple patches ago. It’ll be fixed in the next patch ( in a week and a half ).
Its not necessary anymore. Works fine without it.
Here is a working profile for it:
Just put that in your “C:\Users\Username\Documents\I-Novae Studios\Infinity Battlescape\Profiles” folder and choose it in the launcher. The profile is made for the T.Flight Hotas X when it is connected in PS3 mode to pc.
Just toggle the switch on the backside from “PC” to “PS3” and connect it to the pc.(was easier to configure, but you can also make your own profile in PC mode)
Here is a short list:
escape - toggle keymapping screen
F1 - cockpit camera
F2 - outside camera
SE Button - Leaderboard
ST button - game menu
Stick:
stick - yaw and pitch
twist and shoulder whip - roll
hat stick - up and down and strafe movement
fire key R1 - primary fire
fire key L1 - secondary fire
L3 Stick key - missile fire
R3 Stick key - chaff fire
Throttle Stick:
throttle - throttle
twist and shoulder whip - roll
Backside R2 button - target center
Backside L2 button - target none (holding the button and moving the right stick also lets you change your view)
Thumb button 8 - boost
Thumb button 5 - system menu
Thumb button 6 - weapons menu
Thumb button 7 - comms menu
So does it support rudder pedals?
You can have up to 4 devices. I have a Thrustmaster Warthog Joystick, Warthog Throttle, Saitek Rudder Pedals, and a vjoy device linked to TrackIR. I use VoiceAttack to manage weapons and systems.
This setup works in I:B Direct Mode. It works with all ship types.
Does anyone have an XML file to share for the Thrustmaster Hotas 16000M? (joystick and throttle)
Your help would be greatly appreciated
Isn’t that one of the default profiles?
Might have been outdated and thus removed lately. Maybe.
All HOTAS profiles are partially out of date. I’ll probably have a go at redoing the T16000M myself right before the release, but other than that the only “reliable” profiles so far are azerty, qwerty and gamepads. And even gamepads still need a couple of tweaks.
An nice feature in the long run would be some sort of marketplace were people can submit game control profiles that other people can rank and maybe donate ingame credits to the author. The community could then maintain the profiles and add new ones.
I made a new setup for the xbox controller including a keybindings screen.
While doing this I noticed several issues I would like to discuss here.
First the profile:
Here the profile if anybody wants to try it:
Goes into:
C:\Users\Username\Documents\I-Novae Studios\Infinity Battlescape\Profiles
And here the Mapping Screen to download:
Goes into:
C:\Program Files… …\steamapps\common\Infinity Battlescape\Dev\Client\GUI\Screens
.
.
.
I will list the current problems I encountered:
Possible solutions:
Radial menus
Hi Playbenni !
A lot thank from my side for your support !!!
Now Im able to use the T.Flight Hotas One from Thrustmaster with the “Dual rowing system” cause you made a special XML Data ! Wooow.
In fightactions im able to use my HOTAS like i do it in ELITE ! VERY NICE ! Some settings are not abel to use but thats the problem from the Devs.
For example:
In Elite moste every long holden button on the throttle makes very other button to have a second option. So i hope some one of the Devs using the ONE in ELITE like me and knows what i mean !
There we just have a plug an play XD - BUT I LOVE YOUR GAME !
Das alleine gebührt nur dir Playbenni - THANK YOU SO MUCH !!
That alone is only yours Playbenni
First time with Hotas at 15:12 
in PVP like i do it in Elite with the same HOTAS and mostly with the same guns too XD - https://www.youtube.com/watch?v=YceNKrOR6Ko
I spend a while creating some generic profiles. Need some testing. They don’t need to fit perfectly but errors like flipped axis and such should be looked for.
Buttons will be at weird positions and at most one axis is allowed to not work. (Probably RotZ as I suspect different vendors to have bound it differently)
That’s pretty much the goal of these generic ones.
QWERTY is set as SecKeys as backup. With these Generic Layouts where the exact button position or even ammount of buttons is unknown it pretty much is required to have all the events that are bound by default as backups.
(Edit: Noticed, due to being too tired, that before sharing them I removed my joystick ID incorrectly which makes the files fail to load during game start. Fixed. Has to be “” for empty not “”) 
Fixed.
(Edit 2: Learned that default for throttle is actually axis2 for some backwards reason … also switched roll with yaw because airplanes and people are used to airplanes … shrug)
