Tired of having to go to the control settings to change your controllers (joystick, throttle, etc) pre-set for each aircraft? Released now:
EasyControls for MSFS
A simple freeware application that allows you to setup all your controllers through 1 app, and configure them all with 1 simple dropdown menu for a different aircraft. Think of it as a very light FSUIPC, spad.next or AAO tool, but only for controllers recognized as such in Windows (visible in joy.cpl).
It allows you to bind buttons and axis to any event you want. In combination with the Mobiflight wasm module, also LVARs can be used.
Wow this looks really awesome!! Thanks for creating this tool.
I do have a question please.
Would it be possible to add keyboard modifiers to joystick buttons? Like joystick button 1 does some action, but Shift + button 1 does some other action?
Does this read what aircraft is loaded in the sim? Or do you have to switch to your app and change the profile?
Will there be âgenericâ profile settings, based on type of craft? for example pretty much all the GA prop planes i fly have the same joystick profile, the helis have another, and then i have a few very specific ones.
It doesnât read what is in the sim, that could be on the feature list, but with so many liveries, it could become quite difficult. At this moment, you select the aircraft in the app, and then all connected controllers will load the profiles for that aircraft.
Generic profiles are certainly possible, as you can name them yourself. So you could easily make a profile âGAâ and just select that when flying any GA aircraft in which you use the same settings.
That is an interesting question. I would need to think about that one. It would be a very specific request as Iâm not sure many people would use that.
I might find that useful. For instance (in VR) I have as much as possible assigned to my T16000M joystick (16 buttons plus hat and throttle). Would be great if I could assign mixture and/or prop pitch to the throttle by using CTR or Shift. Maybe right and left brakes to other buttons. Also, comms button could be used for VATSIM and pressing CTR would change it to TeamSpeak or Discord.
It would need this feature before I was interested. Liveries shouldnât come into the equation itâs the aircraft type that obviously matters. You can read that using the simvar âTITLEâ.
Iâve never seen that. Why would a livery change the title of an aircraft. Even if it added the livery name to the end you just need to look for some specific text in the longer string. If the livery changes it completely with no signs of the original title remaining then that is really naughty.
I have another solution in mind where I give you the ability to map the TITLE read through Simconnect to one of the profiles/aircraft you have defined.
I can then easily make it to start automatically when the program launches, by detecting the aircraft loaded and mapping it to the right profile to be used to send events.
That would work but if the title can vary as much as you say it would be good if a users selected title string just had to be present somewhere in the actual title rather than match it exactly.
Can it wash my dishes? No, so sorry, would it include the various sensitivy settings for the axes? I didnât notice that in your cool screen shots (nice touch, BTW). Thanks.
Would it be possible to import existing controls from already in game existing profiles after selecting an aircraft from the drop-down instead of entering each and every controll setting again?
That would certainly be great. It is not that easy though.
The MSFS control profiles are saved as xml files (Anyone know where your controller config is stored on disk? - #5 by snwkill) , and for EasyControls as well (the controls.xml file), so you could also just manually edit the controls.xml file for my program based on the MSFS control profiles. I would be nice to do this automatically for every control that can be converted to SimConnect, but I wonât be able to do that any time soon.
Note that the in sim events are not all 1-on-1 translatable to Simconnect events. E.g. for the condition lever, there is actually no simconnect event defined (yet I hope). However, a lot of events will be easily translatable to Simconnect events.
