June 2, 20242 yr Hi, some days ago I wrote about a problem with AAo not starting in FS2020 under W11, and I solved thank to Lorby_Si installing .net runtime. Now, I started with a new problem, Lorby is very long to start and to became operational, something like two minuts without responding and then it seems to work normally. Initially it seemed to me a conflict between Lorby and IVAO Pilot Core, (prior to IVAO installation seemed working well), but now, also closing the Pilot Core module, Lorby need a so long time to load completely. I tried to change the default port from 9080 to 9090 because on 9080 it doesn't started (apparently), now, as I said i starts but it takes a long time. Do I need to choose another port? There is some known incompatibility? A friend of mine on a very similar system seems to not have this issue. Thanks for the answer. Mauro
June 3, 20242 yr Commercial Member Sound like incompatible USB devices. In AAO go to "Hardware->Device blacklist" and move everything to the right with the "Ignore" button that isn't a game controller that you want to use with AAO. This includes all keyboards, mice and HID devices. Leave only joystick/yoke/TQ/pedals in the list on the left. 10 hours ago, zetato said: tried to change the default port from 9080 to 9090 because on 9080 it doesn't started (apparently), The default ports are 42380, 43380 and 43381. They have zero impact on AAO starting up. Make sure to run the app with the "Run as Administrator" option. There is a setting in the "Application" menu for this too. LORBY-SI
June 3, 20242 yr Author Thanks once again! I moved the usb headset and the keyboard to the blacklist and now Lorby starts well and fast. No need to change the ports. Hope this can help some others in trouble! Bye Mauro
Archived
This topic is now archived and is closed to further replies.