Figured it out! Alpha + Bravo switches etc have binding conflicts. Eg switches 34 - 46 on Bravo Quadrant have a few external lights taxi, strobe assigned to them which conflict with the switches on the Alpha yoke. This is ok for commercial aircraft but bad for ga.
Create new profiles then resolve conflicts by using “search by input” function.
All created profiles are called 'default, when loaded to fly.
Simhanger has a great video on youtube to explain all of this. His video also helped me to get my leds to work.
Hope this helps.
I just did a fresh install of Windows 11 and MSFS. Now I can’t save any control profiles. If I create a new one with a custom name and save it, then add key bindings and save them, once I exit the controls menu they’re gone and the only profile available is “default.” It does this both from the main menu and if I try to do it during a flight. It’s really really frustrating. My UserConfig is NOT set to read-only. I’m using a Honeycomb Alpha and Bravo, and Saitek rudder pedals.
the big question is, if i remap every button control one the velocity one since it got al erased. will when the beta goes live , will it make me remap them again..
I’ve recently reinstalled the latest Beta release and this time it copied across my settings okay… I’ve taken screenshots just to be on the safe side, but it looks like things may be working okay now.
I did also install the latest V1 firmware just before the new beta install, so I don’t know if that made a difference or not.
how recently? i updated the V1 yesterday and downloaded the beta last night
I updated mine yesterday as well.
yea.. from what im reading some people have no problems with stuff carrying
over and others do…
I’m having the same problem. I have left the beta to return to the previous version. I’ll try to upgrade again to see if it works for me too. V1F with 1.3.0 version.
I was finally able to fix it by completely reinstalling MSFS2020.
The versions:
MSFS2020 1.27.17.0
V1F 1.3.3
The problem I have now is that if I start MSFS 2020 with the V1F connected, some controls fail. This forces me to restart the game by disconnecting V1F. For it to work well, I always have to boot MSFS2020 without V1F, and when it’s fully booted, I plug it back in.
Same issue for me with both hotas one and the factory original controller.
Profile for hotas one is there but in flight itself does not respond.
My gamepad has its controls reversed despite looking ok in settings.
Rudder does not return to centre. Input a small amount of rudder, release your input and it will stay rudder in until you centre it manually.
Logged via Xbox report a problem
Xbox series S
2 Likes
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons?
Yes
Brief description of the issue:
The controller profile for one of my devices somehow got corrupted, and it shows like some controls are “correctly configured”, but fail to work inside the airplanes. If I create a new profile and assign identical controls, it works. If I return to the “corrupted” profile, it stops working. If I clone the “corrupted” profile, the errors still show on the copied version.
The corruption is such that the controls page shows the input correctly, but the plane no longer reacts to the inputs.
I reported this earlier here: Throttle won't move with HOTAS, but controls show correct input from Hardware device
Unfortunately, someone decided this was a hardware community support issue, which it clearly isn’t. This has nothing to do with the hardware. It is MSFS and the control profile. Please, do not redirect this to the community help, I have resolved the issue for me, but it meant re-creating all my input values.
The BUG is that somehow the profile gets corrupted and, even thought the controls page shows the input as “correct”, the plane is not responding to its feedback.
An interesting pointer is that: Reassigning the failing control also does not resolve the issue. So, apparently, the corruption happens “between” the profile and the actual plane use of the profile.
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
See video
PC specs and/or peripheral set up if relevant:
Ryzen 3700x 3080TI
Build Version # when you first started experiencing this issue:
1.26.5.0
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
Do you still have the corrupted profile? What happens if you assign some other axis to throttle in that profile, e.g. assign one of the levers to throttle axis (the combined throttle axis) or assign the levers to throttle 1/2 axis (0-100%)?
Do all controller and game axes (not just throttle) fail on the throttle unit? It’s buttons work correctly? Axes work fine on the stick?
Hello @RafaPolit ,
thanks for the bug report.
If you are interested, as far as I know, the profiles are locally saved in the wgs folder with cryptic names.
It is two folder back towards your Drive root from your Community folder, in SystemAppData.
If you open the files, can you detect a mismatch between the corrupted and working profiles?
but, as per Tag he own Steam.. in steam the profiles sit on different locations.
Users can see it within the Steam-Cloud and also localy:
This can be used to create e.g. backups..
I still have the corrupted file. I’m 90% sure I tried to assign other knobs to the same axis, but that is very simple to re-do.
I did not check assigning throttle to an axis on the stick, I think it’s a good debugging method.
I do have steam, I’ll locate the files and report back.
Thanks!
Thanks for correcting me.
I assumed steam would have the same folder structure as MSStore. That does not seem to be the case.
1 Like
In steam is the structure much more understandable for “human beans” 
I found also older screenshot from me related to
- Steam-Cloud ,
- and also local file structure
1 Like
Me too. After beta SU10 HOTAS ONE no longer works. Only the home button (the one with the light) works. The joystick is recognized by the game (you can see it in the controller setting menu€ but it doesn’t do anything.
XBOX S
1 Like
Moved to #bugs-and-issues:hardware.
1 Like
Do you have the same issue if you follow the OP’s steps to reproduce it?
Similar
Provide extra information to complete the original description of the issue:
T.FLIGHT HOTAS ONE stopped working too with SU10
If relevant, provide additional screenshots/video:
The USB connection is recognized and the joystick allows to move through the menu (e.g. Xbox buttons “A” and “B” are working) but no flight controls at all work. The “controls options” settings page shows that the joystick has been recognized but the page which usually lists all expandable settings is entirely empty.
1 Like