December 26, 20223 yr I have installed MASO 1_07_b04 and when I start it I get the following error message: "Error when reading config file:< C:Users\.....\Conten.xml> There is an error in XML document (2,2) . init. It is strongly advised not to continue with MASO. The content of the Content.xml is as follows: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <Priorities> <Package name="fs-base-nav" priority="1"/> <Package name="navigraph-navdata-base" priority="2"/> <Package name="navigraph-navdata" priority="3"/> </Priorities> What should I do to be able to use MASO? Thanks for the help Stefan Liebe regards Stefan Liebe
December 26, 20223 yr Commercial Member This seems to be a new version of the Content.xml. I don't have the "Priorities" group. In fact, isn't the content.xml supposed to be gone by now? I thought that it hasn't been in use since SU10? LORBY-SI
December 27, 20223 yr Author Thanks for the answer. As it looks the content.xml was generated by the Navigraph Navadate Center. I don't know if it is still necessary. Can I start MASO and ignore the warning if I make a copy of the content.xml to be on the safe side ? regards Stefan Liebe
December 27, 20223 yr Commercial Member At the moment I'm not sure what to make of that file. MSFS will create one too when you change the package order with the MSFS internal experimental reordering tool. But the contents of the file are really weird, it looks like the packages are arranged at relative priorities, which, at least to me, doesn't make a lot of sense. I don't understand the reasoning behind this, because from my perspective, when new packages are added or existing packages removed, these relative values can become invalid. IMHO all packages should be in there with a priority value attached to them - just like it always was with the MS sims. I need to find out more before making changes to the app. With the current version of MSAO you would have to rename the content.xml when you want to use the app. Afterwards delete the copy that MSAO creates and rename it back. Edited December 27, 20223 yr by Lorby_SI LORBY-SI
December 27, 20223 yr Author Thanks for the tip. I renamed the content.xml and then started MASO. Unfortunately no addon is displayed. All displays are empty. I guess that's because my installation folder is on "D:\MSFS" and the community folder is "D:\MSFS\Community". The content.xml is in the folder "C:\Users\myname \AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache". Can I adjust this in an ini file of MASO? Edited December 27, 20223 yr by Stefan01 regards Stefan Liebe
December 27, 20223 yr Commercial Member 3 hours ago, Stefan01 said: Can I adjust this in an ini file of MASO? The app doesn't have an ini file. It reads what it can find on your disk(s). It tries to find the community folder by looking into your UserCfg.opt file, provided that the file can be found. That is where the actual path to the Packages folder should be, and it expects Community to be a sub set of that. But to me this sounds more like with one of the latest MSFS updates the MSAO app is simply no longer compatible and has to be re-done or scrapped entirely. Edited December 27, 20223 yr by Lorby_SI LORBY-SI
December 28, 20223 yr Author The userCfg.opt has the following last line: InstalledPackagesPath "D:\MSFS" regards Stefan Liebe
December 28, 20223 yr Commercial Member I've pulled the plug on this app for the time being, the download has been removed. Once it becomes clearer how MSFS actually works regarding the content.xml I will potentially revisit the app and then decide if it is worth adapting it - or just putting it to rest. LORBY-SI
Archived
This topic is now archived and is closed to further replies.