March 15, 20233 yr Hi. Is there a solution to start the lorby's axis and ohs with the "start atomatically with the sim" ? set all to admin rights but everytime i must start the lorby extra. what i'm doing wrong? is there a exe.xml entry or something else ?? please help. thx Simon
March 15, 20233 yr Commercial Member 3 minutes ago, panamericana said: Hi. Is there a solution to start the lorby's axis and ohs with the "start atomatically with the sim" ? set all to admin rights but everytime i must start the lorby extra. what i'm doing wrong? is there a exe.xml entry or something else ?? please help. thx Simon AAO does the exe.xml entry for you. Unless that file is broken, which happens quite often, then the sim should try to start AAO. But for this to work in Admin mode, you have to start the simulator itself with the "As Administrator" option too. Otherwise Windows will prevent the sim from starting AAO. Maybe do it the other way around and let AAO start the sim? There is an option for that in the Application menu too. LORBY-SI
March 15, 20233 yr Author no, both Applications are set with admin rights. my Settings are ticked by "start atomatically with the sim", so i checked this and it is all correct. how is the entry in the xml ? I saw that the Program does not save the "start automatically with sim", after i closed the Program its unticked again Edited March 15, 20233 yr by panamericana
March 16, 20233 yr Commercial Member When I activate "Start automatically with the sim" the entry immediately appears in \Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\exe.xml. And the checkmark doesn't just go away either. I have no idea what is going on on your computer. Maybe check your virus scanner logs. Are you sure that 1. it is really the MSFS version of AAO, installed with the "_MSFS" installer and 2. that no other program is managing your exe.xml? Some kind of addon/config management app? Also, as mentioned earlier, exe.xml files are often broken (by manual interference or by other addons). So the most likely scenario is, that your exe.xml is defective, and AAO cannot read nor change it. Maybe post the contents of that file here? This is the AAO launch entry in the exe.xml, provided that you installed the program into its default path. Quote <Launch.Addon> <Name>LorbyAxisAndOhs</Name> <Path>C:\Program Files\LorbyAxisAndOhs_MSFS\LorbyAxisAndOhs_MSFS.exe</Path> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <CommandLine /> <NewConsole>False</NewConsole> </Launch.Addon> Edited March 16, 20233 yr by Lorby_SI LORBY-SI
March 16, 20233 yr Author <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="SimConnect" version="1,0"> <Descr>SimConnect</Descr> <Filename>SimConnect.xml</Filename> <Disabled>False</Disabled> <Launch.Addon /> <Launch.Addon> <Name>noolaero-module-vdgs</Name> <Disabled>False</Disabled> <Path>D:\MSFS2020\Community\noolaero-module-vdgs\Binaries\vdgs-util.exe</Path> </Launch.Addon> <Launch.Addon> <Name>FenixA320</Name> <Disabled>False</Disabled> <Path>C:\Program Files\FenixSim A320\deps\FenixBootstrapper.exe</Path> </Launch.Addon> <Launch.Addon> <Name>Aerosoft VDGS Driver</Name> <Disabled>False</Disabled> <Path>D:\MSFS2020\Community\aerosoft-vdgs-driver\aerosoft-vdgs-driver.exe</Path> </Launch.Addon> <Launch.Addon> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Name>FSUIPC7</Name> <Path>C:\FSUIPC7\FSUIPC7.exe</Path> <CommandLine>-auto</CommandLine> <NewConsole>False</NewConsole> </Launch.Addon> <Launch.Addon> <Name>Couatl</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe</Path> </Launch.Addon> </SimBase.Document> But i find that i not have the folder Microsoft.FlightSimulator_8wekyb3d8bbwe\ the its name is Flight Simulator and its under User/Appdata/Local/ Flight Simulator..... under Local/packages there is nothing... Edited March 16, 20233 yr by panamericana
March 16, 20233 yr Commercial Member Steam or MS Shop version? Mine is the store version, Steam is in a different location. The file above is not a correct exe.xml. I know that even Asobo posted this code, but it is actually a definition file for SimConnect. Why would a file called "exe.xml" have "simconnect.xml" in the Filename tag??? A proper exe.xml looks different. But that doesn't matter. I already posted the launch code for AAO above, just add it to the others in your file: Quote <?xml version="1.0" encoding="Windows-1252"?><SimBase.Document Type="SimConnect" version="1,0"> <Descr>SimConnect</Descr> <Filename>SimConnect.xml</Filename> <Disabled>False</Disabled> <Launch.Addon> <Name>noolaero-module-vdgs</Name> <Disabled>False</Disabled> <Path>D:\MSFS2020\Community\noolaero-module-vdgs\Binaries\vdgs-util.exe</Path> </Launch.Addon> <Launch.Addon> <Name>FenixA320</Name> <Disabled>False</Disabled> <Path>C:\Program Files\FenixSim A320\deps\FenixBootstrapper.exe</Path> </Launch.Addon> <Launch.Addon> <Name>Aerosoft VDGS Driver</Name> <Disabled>False</Disabled> <Path>D:\MSFS2020\Community\aerosoft-vdgs-driver\aerosoft-vdgs-driver.exe</Path> </Launch.Addon> <Launch.Addon> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Name>FSUIPC7</Name> <Path>C:\FSUIPC7\FSUIPC7.exe</Path> <CommandLine>-auto</CommandLine> <NewConsole>False</NewConsole> </Launch.Addon> <Launch.Addon> <Name>Couatl</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe</Path> </Launch.Addon> <Launch.Addon> <Name>LorbyAxisAndOhs</Name> <Path>C:\Program Files\LorbyAxisAndOhs_MSFS\LorbyAxisAndOhs_MSFS.exe</Path> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <CommandLine /> <NewConsole>False</NewConsole> </Launch.Addon></SimBase.Document> LORBY-SI
March 17, 20233 yr I also have this same issue, but it's not just AAO. It's also FSRealistic and Pop Out Panel Manager. All applications (including MSFS) are set to run as admin. I do open/close the sim through steam, I wouldn't think that would make a difference....
March 17, 20233 yr Commercial Member 5 hours ago, skytation said: I also have this same issue, but it's not just AAO. It's also FSRealistic and Pop Out Panel Manager. All applications (including MSFS) are set to run as admin. I do open/close the sim through steam, I wouldn't think that would make a difference.... Most likely a broken exe.xml. LORBY-SI
Archived
This topic is now archived and is closed to further replies.