I’m doing the same, just start 2040 to see if by chance they have actually done something about it with a quick fix….. I can dream
For me the worst thing is the calibration of the throttle levers, it is impossible to fly when the idle is at maximum lever reverse. As easy as the 2020 was
That’s where the issue comes in with the slow control settings, you need 1 axis for Fenix/PMDG and another for inibuilds/Asobo. Hence why it can take an age to get the right setting. I thought I would test it… to swap from one build to another can take over 5 minutes waiting for the ■■■■ refresh circle to finish spinning at each setting.
Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes
Provide extra information to complete the original description of the issue:
•
If relevant, provide additional screenshots/video:
•
As in FS2020, we urgently need to be able to save our profiles on our computers. This will free us from the instability and failures of Microsoft servers.
3 Likes
Still anoying AF. Bug cane for me witn the introduction of su2. Before that and in all the betas not problems.
Even configuring a new plan with standard settings takes about 5 min. Time i coukd be flying.
1 Like
Yeah, this whole philosophy from osabo about the control setup is the worst i ever encountered. Its so complicated. Even after all these hours (lv370) still not clear to me. And i learn a new fms or navigation system in a few hours 
3 Likes
I’ve got my profiles back.
Cloud backup?
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 have the same issue if you follow the OP’s steps to reproduce it?
•
Yes, happened after SU2 loading
Provide extra information to complete the original description of the issue:
Impossible to move from one control to another whitout mini 3 minuts wait
Locker appear on, aircraft controls selection, Don’t know why!
•
If relevant, provide additional screenshots/video:
•
Still excruciatingly slow. Please fix for SU3 update. Please also fix honeycomb bindings reliably or get aerosoft to update this please.
Oh yes, please fix it please. It is getting worse and worse. 
I have a ton of USB devices and it takes me almost half an hour when switching aircraft. Even using SPAD.neXt and setting empty default profiles for all aircraft in MSFS. But the profiles have to be reapplied every time I change aircraft or add a new one. 
Please help! 
An almost acceptable solution is to keep only one yoke, one throttle, and one rudder pedal connected. It still takes 30 seconds per profile change for all devices and all categories. So minimum 3 devices x 2 profile changes x 2 categories = 6 minutes! (EDIT: forgot the keyboard and the mouse)
Since MSFS keeps memory of old devices (which is good, but should be editable when no more needed), this should still slow down processing even if they are disconnected.
The other solution is to avoid changing aircraft models. This is very sad.
This is made even worse by the fact that you have to click through to select a profile, rather than it being a drop-down list.
Asobo are so short-sighted they only imagine people having 2 or 3 profiles per controller. Even without this delay it’s a very poor UI decision.
8 Likes
I would make a backup of my wgs folder, clear the cloud data and restore the profiles step by step until you find the bad one. Takes even for 20 or more profiles less than 30 Minutes and solves the problem for sure.
I really wish they would fix this.
I’m pretty sure there’s nothing left to fix.
The bug isn’t the long switching time we see today. Previously, the bug occurred when the control profiles were mixed up. Once this has happened, it is too late and you will see these long switching times.
The root cause of the bug, i.e. the mixing up of the control profiles, seems to have been fixed in SU3. At least nobody has complained about this problem occurring with SU3 if it wasn’t there before. For those affected, the problem started with SU2.
If you are affected, the only way to solve the problem is to clean up your control profiles. Many users have confirmed that this solves the problem immediately. Cleaning the cloud data will, of course, cause you to generate all control profiles again. Therefore, I recommend working with a backup and restoring the control profiles step by step until you identify the ‘bad one’. You have to create this one newly, but you can restore all the others from the backup.
Theoretically, in this cleanup process, would we only see the slowdown if the device with the affected profile(s) were connected? Could that be a good process-of-elimination step before blindly deleting things?
Also - does anyone know what the parenthetical number is after “General controls” and “Airplane controls” is? It seems to be changing every time I change presets, but it’s not the same number when I go back to the same preset.
I believe that’s the number of / duplicates of General controls and Airplane controls .
Best not to try too much until SU3 is released and hopefully some sort of fix in included!
Yikes - so the idea is that it’s saying I have 99 General controls profiles for that device? And the number was increasing each time I changed profile. 
Yes possibly, but I’m sure somebody with better knowledge than me will come along and confirm / correct me!