October 5, 20232 yr Jeepers! Downloaded from Lorby site. Windows 11. Extracted to folder. Clicked on the MSFS install .exe. "This app can't run on your PC". Man alive this kinda stuff just shouldn't happen. Maybe I'll just go to SPAD.
October 5, 20232 yr Since the most recent update, A&O has been acting a bit strange for me. Of course, one never knows if it was due to SU13. Anyway, the app no longer connects to simconnect the first time the sim starts. I always need to restart to get my buttons and axis recognized.
October 5, 20232 yr Commercial Member 3 hours ago, n116dh said: Jeepers! Downloaded from Lorby site. Windows 11. Extracted to folder. Clicked on the MSFS install .exe. "This app can't run on your PC". Man alive this kinda stuff just shouldn't happen. Maybe I'll just go to SPAD. Windows 11 Pro 22 H2 Build 22621.2283 Downloaded the ZIP from the axisandohs.com website Pulled out the MSFS Installer onto my Desktop <- this is a necessary step - you cannot doubleclick a file inside of an encrypted ZIP typed in the password LORBY when being asked to Doubleclicked the installer on the desktop, persuaded Defender that I really want to run it - it installed just fine. Edited October 5, 20232 yr by Lorby_SI LORBY-SI
October 5, 20232 yr Commercial Member 1 hour ago, flyforever said: Since the most recent update, A&O has been acting a bit strange for me. Of course, one never knows if it was due to SU13. Anyway, the app no longer connects to simconnect the first time the sim starts. I always need to restart to get my buttons and axis recognized. Sounds strange. I always start the sim from AAO, not the other way round, but it always connects when it is supposed to - not a single issue. Nor has any been reported by the testers. Edited October 5, 20232 yr by Lorby_SI LORBY-SI
October 5, 20232 yr I understand. I've had a&o for a very long time, so this latest "strange" behavior is based on experience with the app. Nevertheless, my experience is unique: no matter what I do, start a&o first, or msfs first nothing works as expected. The only way for the app to work is to first click the button " simconnect" off, and then turn it on again. This said, I am not complaining; I am simply describing my situation. This "strange behavior" began to happen only after upgrading to su13 as well as upgrading to the latest a&o version, which were done practically at the same time. A&O is a fantastic application and the author is the best in terms of service and upgrades. My issues are a minor incovenience, since I can still proceed with flying successfully. I highly recommend this app, and am confident that the issue will eventually resolve itself.
October 5, 20232 yr Commercial Member 1 hour ago, flyforever said: The only way for the app to work is to first click the button " simconnect" off, and then turn it on again. With MSFS it is very hard for an app to figure out when an aircraft has actually been loaded and is ready to fly (that being said, it works for most people all the time, so this seems to be a local problem). The safest way is probably to connect the app manually when you are sitting in the cockpit. Leave autoconnect off entirely. Also, make sure that the first camera that is loaded is the internal cockpit camera, not an external view(!). In any case, an issue like this cannot be solved in a forum. Please send an email with your proof of purchase to the support address. LORBY-SI
October 6, 20232 yr Author Thanks to all for you input. After yet another uninstall/install cycle; I got it working.
Archived
This topic is now archived and is closed to further replies.