AquilaeAFR

OK... everything was well 2 days ago, but the initial issue is back (and I don't know why). AAO works but it needs 10 minutes to start. Here is the new startup log. It seem it's the same problem with one of a HID device. As you can see, all the devices that appear in the "device blacklist" window are in the ignored list. Despite that, I don't know AAO finds others devices. At this point, this solution looks like the best thing to do. How can I do to start the app manually ? With the Windows+R shortcut ? If yes, I just need to write LorbyAxisAndOhs_MSFS2024"-blacklistall" ? Sorry for the dumb question, I never use this menu.

Yes, Clermont Ferrand is the main city in Massif Central. Despite his airport is not very important, It's mostly used for regional flights I think. VKB is a good hardware, I have the Gladiator Next Evo, with a STECS throttle. Virpil was my second choice for the stick, but I've finally change my choice for the VKB. And it's completely different from my old Thrustmaster T Flight Hotas X, when I was on XBox. I heard for the FSReborn Phenom 300, It will surely be a guaranteed purchase. Currently, I'm waiting for the Cessna Citation X+ made by Flight FX, and the Bombardier Global 7500 made by CJ Simulation.

Okay... I don't understand why, but... now it's finally work, the app start within 3-5 secondes. The only thing I did since my last message (after blacklist the devices listed in the menu) was turn off my PC before going to sleep... Here the new start log. It seems the problem with the HID devices is gone. The only remaining issue is now, AAO doesn't start automatically with the sim, I need to start it manually. I have the option activated in the "application" menu. I don't know if it's a problem with my exe.xml file, as I saw on others topics that some people had the same issue with this. Here is my exe.xml (in the Microsoft.Limitless_8wekyb3d8bbwe/LocalCache file)

Thanks for the quick answer. No, I didn't change anything (or at least, I don't remember). I used the sim yesterday, AAO was started with the sim. Then, I closed the sim + AAO, and at the next launch, I had this problem. I did the device blacklist, it's shorter to start, but it's still take many time (10 minutes to launch). I moved everything into the list on the right, including the Streamdeck. Here the new startup log ROG Delta II is my headset, AURA LED seems to be a LED controller with my motherboard. But I don't know what is the three HID Devices (périphérique fournisseur). Maybe something related to my keyboard/mouse. All these devices doesn't appear in the "device blacklist" menu. In game, everything work very well, I tested my streamdeck with a profile for the FSS Embraer 190 wIthout issue. But I don't understand why it take 10 minutes for the "acquiring devices now" stage on the startup log.

Hello, I bought AAO with Simmarket last week (before that, i tested the demo version without issue). I use it for my Stream Deck XL, with MSFS 2024 (store version). It worked very well, until yesterday. Now, when I launch MSFS, the app doesn't autostart now. When I open Task Manager, I can see AAO running in background, but I can't open the user interface. Eventually, it will open by itself after 15-20 minutes I tried uninstall/reinstall the app. Also checked with the demo version, but I still have the same issue. I checked the startup log in Appdata/Local/LORBY_SI I don't know if it's an issue with some hardware listed in the log. Thanks for the help !

Hello everyone ! My name is Taylor, and I live in France. I discovered flight sim with FS 2020 (XBox version). For FS 2024, I bought a new PC and a dedicated hardware setup (Winwing FCU/EFIS/MCDU and VKB joystick and throttle). I mainly fly with airliners, especially Airbus (Fenix A320, Inbuilds A350, FBW A380) and Embraer (FSS E190). I'm also a military aircraft user (Miltech C17 Globemaster) and a beginner with business jets (Flight FX Hondajet et Citation X). I don't have VATSIM or IVAO yet, but I use BeyondATC to train my skills for some more realistic flights.