Ok, I got lazy! 
āOne macro to rule them allā¦ā
5 minutes fiddling and works like a charmā¦
Does anyone know what file these assistance settings (if any) would be stored in? At this point I kind of want to back it up after I fix the settings and replace it before booting. Having to do it in sim on every single startup is driving me bonkers.
For me, I am holding off on the beta until at least this one is fixed. Seems to be a very annoying bug!
Same, but because of this AND the spinning circle. Tired of having to deal with both these bugs all the time.
Itās not an addon, i did a clean windows re-install today and installed MSFS straight into SU14. After my first load my assistance settings were reset. After that every time i run the sim it happens.
One interesting thing: I tried to install an addon after i closed the sim and it was telling me the sim was still running. Could it be that the settings are not saved because the sim doesnāt exit properly?
That s by design of the Fenix team. They are not meant to be changed. When you override those dummy settings you are overriding the custom design logic of the Fenix.
With this, implore Asobo to fix this with the next BETA build. I personally have stopped simming for the moment, and do not plan to try again until there is a fix.
Sounds silly I know, but the thing is I am paranoid about backing out of the BETA based on past experience of losing all my control settings and logbook recordings when going back to a release build. At the same time, I donāt have the patience to set up assistance customization every time I start MSFS.
I suspect there are other simmers that feel the same as I do, and that might affect the amount of feedback generated from the next BETA.
Just my thoughts.
Interesting, did not know that. Thanks! (Flew the FBW for a few weeks, just bought the Fenix)
Another ātemporaryā way around having to set all your Assistance settings up each time you start MSFS, is to remember to turn OFF Online Functionality, before you shut down MSFS.
Then next time you start MSFS, it will not be online, and therefore not try to download and set the Assistance Options, and they will remain the same as they were when you last had MSFS running.
Of course, you will need to turn ON Online Functionality, if you want Bing data, MP, AI traffic etc etc
You will also NOT get any updates, so if you want updates and know they have been released, you will need to make sure Online Functionality is set back ON again, before closing MSFS, so next time it runs, it gets those updates.
Maybe a little easier & quicker, that setting a complex Custom Assistance set of options each time you run the sim ..
Just a thought ā seems to work for me
Thanks for sharing. I did not know MSFS could start without an online connection.
Off to try this right now.
The problem with such annoying bugs is that there will be less beta testers or people will fly less with beta SU14. I wonāt opt out but I will fly less
Im so glad I didnāt join this time around due to this bug even though Iām really wanting to test the snow change.
But things like these are bad because now instead of focusing on the intended changes evryone users and devs have to chase down this bug instead. 1 step forward, 2 to the side, 1 back and now nobody moves forward.
The good news is, thst according to the last development update they already identified the issue and will fix it with one of the future builts of the Beta.
So thos shouldnt consume too much time of the team anymore.
But i agree, even though the game is actually still playable l, this bug is gamebreaking for me.
I tried to do some flying but ran into other issues like CTD while zooing on the world map or CTD while in flight and loss of ATC audio.
All well known issues, of course. But this new āreset of assisitance optionsā bug is now simply killing all motivation to start the sim and all i do now is waiting for an update instead of flying on my week off.
Iāve joined a lot of Betaās. What i donāt get is, that OBVIOUS bugs get past QC of Microsoft and Asobo. Frequently.
This SHOULD not happen !!
Again, talking about obvious bugs !
So, I use on my Sim something called FSLTL (Traffic Injector) and GSX PRO (FSDreamTeam). Turns out that getting both of them out of Community it resolved my issue. Got my Assistance Options back to normal. Have no idea why but it resolved the issue for me. Will keep on trying restarting the Sim to see of anything changes, but after 10/12 starts IĀ“m finally happy. The only thing now with the Beta 14 is the drop on FPSĀ“s.
Also, the fact that I click on a friends plane at the World Map and by doing that the Sim crashes, it does not help at all.
Keep on flying..!
I tried also : empty Community Folder and as for you, my settings were back. Thatās very strange indeed. Before that, it was back to easy at every FS starts
I should have released this a while back , but didnāt get any interest: Assistance Manager - Preview
I guess theyāll release a new beta to fix it soon anyway.
I am āASSumingā that since it is recommended to test for native MSFS Bugs, with an empty Community folder, that if Asobo QA is testing that way, the Assistance Bug does not present itself, so slipped by them.
When one has got use to the extra features offered by Community Mods, and the extra planes & improved airports, not to mention additional tools, its very difficult to go back to a vanilla MSFS without all these extra āGoodiesā.
If you are Asobo QA, what do you include in your Community folder when testing ? and how do you ensure that what you do include, does not cause an issue, as opposed to the base MSFS code.
As a developer, I am finding that if I only include the plane I am working on, in Community, that is NOT enough to cause the Assistance Bug.
The ENORMOUS benefit of 1000ās of false errors no longer appearing in the Dev Console error logging, and better error verbose logging, more than makes up for this short term (I Hope) Assistance bug.
MAYBE other PAYWARE Devs can now start looking at the Logs, and fix their āCarelessā errors-- as they are far more visible now, without the 1000ās of false errors cluttering up the error log.
No names mentioned, but certain Planes are RIDDLED with āerrorsā, that while not stopping the plane for running are clearly stopping some of their functionality to work.
**
This includes some Asobo assets as well , that have been hiding among the former 1000ās of errors, but no are now very obvious.
**
That is not correct. As I and at least a few others have posted, even with totally empty Community folders, this bug still presents itself in some circumstances (mine, for instance).
I hadnāt realized this. Where did you find this recommendation?
Also, Iāve had the problem both with and without an empty Community folder.
Itās a weird problem, but Iām glad Asobo has a fix for it.