November 14, 20232 yr Hello, I've been doing some maintenance on my PC, reinstalled MSFS last month, and as I had an issue with AAO (I might come back to this in another thread, but I have now a more seriours issue), I decided to reinstall it. So I backuped my config files, uninstalled AAO, cleaned the data directories (C:\Users\Haddock\AppData\Local\LORBY_SI and the stuff under "My Documents"). I then downloaded and installed AAO 3.60 (latest from Simmarket). It went Ok, but I noticed that it did not create any xml config files in C:\Users\Haddock\AppData\Local\LORBY_SI\LorbyAxisAndOhsMSFS\. Ok I thought, AAO might create them when run for the first time. So I launched it (admin mode), modified a parameter (deselected "Connect Automatically"), closed AAO then went to C:\Users\Haddock\AppData\Local\LORBY_SI\LorbyAxisAndOhsMSFS\ : still no xml files ! This dir contains only : FipGauges_MSFS (dir) LorbyGauges_MSFS (dir) LAAO_log_20231114213938.txt LAAO_Startup_log.txt "LAAO_Startup_log.txt" reported no issue but "LAAO_log_20231114213938.txt" contained this message : Quote The app encountered an error while shutting down: Échec de l'initialisation du système de configuration (the last half being french for "Config system initalization failure") Another test : launched AAO, went to Scripts Editor, create a test script, and AAO closed (crash to desktop) when I hit the "Save as new" button. My PC hasn't changed in months, it's a Z690/i9 12900K box, Windows 11 on a SSD. Any clue to what's happening ? Thanks for your help ! Haddock Edited November 14, 20232 yr by Haddock69 typo
November 15, 20232 yr Author I tried a couple more times to deinstall / resinstall 3.60 (in admin mode or not) to the same lack of success. But I had a backup of the AAO 3.51b08 installer, so I tried this version instead, and ... all the XMLs are back in the config directory, and the "create new script" test also went fine. I fear there is something wrong with the way 3.60 installs on a system with no older AAO version. Now I'm gonna try to see of the original issues I had are also gone with 3.51 ... and then update to 3.60. I'll be back. 🙂 Haddock.
November 15, 20232 yr Author Ok so the initial issues I had with 3.60, which prompted me to reinstall, were : B: vars no longer working selecting in AAO's menus "Gauges/Web FIPs" led to a small windows opening then closing again immediately, too fast to see if there was anything on it. entering my Simbrief username in the Extras menus and clicking "Test" gave me a "Webservice failed!" message And here are the results of my last batch of tests : With 3.51b08, all 3 issues above are gone. If I then upgrade by installing 3.60, all 3 issues are back. Plus of course the "install as a first AAO version" issue I described in the top post. One last test : I tried to see if 3.60 worked better with Win 11 safety tools off (firewall and Defender anti-virus) in case Win 11 had falsely flagged the 3.60 AAO exe as dangerous or something like that, but no change. So 3.60 is a no go on my system, I have no idea why. Haddock. Edited November 15, 20232 yr by Haddock69
November 15, 20232 yr Commercial Member 6 hours ago, Haddock69 said: So 3.60 is a no go on my system, I have no idea why. Sorry, no idea on my end either. This has never happened before to anyone (that I know of). The problem is, that you did so many things that normally are a no-go for this app, that it is impossible to tell what is or was wrong. For example: when you forcibly remove the database files, then install a new version, then put back the database files of the older version, you potentially deprive AAO of the chance to update the database from the old to the new version. The update process expects all files to be there - otherwise it assumes that it is dealing with a completely new install. 19 hours ago, Haddock69 said: (the last half being french for "Config system initalization failure") That is usually a problem with the Config files that Windows creates for an app of this type. They are in AppData\Local\LWR. You can delete all of those. Edited November 15, 20232 yr by Lorby_SI LORBY-SI
November 15, 20232 yr Author 1 hour ago, Lorby_SI said: That is usually a problem with the Config files that Windows creates for an app of this type. They are in AppData\Local\LWR. You can delete all of those. Oooooh I just looked at the user.config file in the 3.60.32.0 subdirectory of AppData\Local\LWR and it contains corrupted characters ! I'll be back in two seconds... So I deleted this file, reinstalled 3.60 over my 3.51 and the first test (clicking the Simbrief Test button) is Ok ! Testing with MSFS now ... Confirmed, everything is fine now. Thanks a lot ! Haddock. Edited November 15, 20232 yr by Haddock69 added test result
Archived
This topic is now archived and is closed to further replies.