Hehe, as I said. There is only one usable tag. The others like builder:“”; where you would assume it is used for old packages isn’t working (in Community folder).
I didn’t notice before, because i’ve used scenery that mostly use LODS in their addon.
I’ve just set my content.xml to read only. It doesn’t seem to affect the startup of the sim in any way (maybe a bit faster?)
If you need to reorder or disable/enable packages you can reset the read only attribute once the sim has finished loading to allow the changes to be written. And before you relaunch next time remember to set it back to read only.
New packages will still load up with content.xml set to read only. You just wont be able to set the load order.
2 Likes
Blew away the duplicates and file size is now… 88k. 
What an absolute joke that Asobo has created this mess of a sim. We have community members trying to edit program files to make this deeply-flawed product work. Just a joke.
4 Likes
Unfortunately not fixed in 1.2.8.0. Back to the read only ‘hotfix’.
setting the file to read only stops the duplicating happening? with no negative side effects?
might do that myself then
Sure. Just delete the file. MSFS will build a new one next start. And when this is done, just set the file to read only. Don’t forget to resetting it in case new sceneries or airports are added.
1 Like
I have to keep an original file, and copy it to replace the one in 2024, everytime before start.
Need Asobo fix it.
Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes
Provide extra information to complete the original description of the issue:
• It’s making the priority not available since everytime the entry will be generated and priority been ignored.
If relevant, provide additional screenshots/video:
•
What about 2020 sceneries?
It seems weird to put a line saying a 2020 package was built by the 2024 Scenery Editor. I’ve been using my 2020 sceneries in 2024 without issue for the most part (a missing building, some weird but not really noticeable texture issues on aprons).
whats worrying is that this isnt bug logged. in other words they cant reproduce it.
so i guess either its just us, or most people are just oblivious to whats happening in their content.xml, including the devs.
That or they haven’t even bothered to acknowledge this and hand it off to the developers — I’m going with the latter.
The tag system is only as good as the people assigned to put the tags there.
1 Like
I’ve never once looked at my content.xml file. But, I do think this is an important issue and voted for it.
I’m checking out the definitions of the manifest.json in the samples, but, I’m not sure how that’s going to define how 2020 packages should be formatted. I’m assuming no changes from 2020… Which would not have this new line.
Seems to me saying a 2020 package was built by 2024 will cause further issues?
The problem is, that if you disable something and there are multiple entries already that are enabled what does the sim use or do…
My guess is that 2020 packages work in compatibility mode, same for some airplanes that use compatibility mode. No idea if implementing that feature was such a good idea from Asobo, it invalidates the whole point of 24 being made. (Faster, modular, less overhead) now it still needs old code from 2020 for that feature.
1 Like
Just a housekeeping tip for anybody that wants to quickly remove the duplicate entries from the content.xml file. If you are using Addons Linker, under the “Tools” section there is a Content.xml editor. If you open your content.xml using this feature and then save the content.xml without making any changes, it will remove all of the duplicate entries and leave everything else untouched.
Obviously the duplicates will begin to return after you restart MSFS, but it only takes a second to clear every couple of days or so, until it is fixed.
4 Likes
Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes, every start the contents of the community folder gets another added line to the content.xml file.
Provide extra information to complete the original description of the issue:
Have content in your community folder, restart a couple of times. And you will see the lines being added from each restart.
If relevant, provide additional screenshots/video:
The same for me, I can confirm the content.xml issue. It is mpossible to use community items yet.
But even official entries (beginning with “fs-20”) will be duplicated by the bug. So the workaround is unfortunately not helping and the bug must be resolved by Microsoft/Asobo as soon as possible because it makes it impossible to use community items (no matter if from the community nor from other stores than the Microsoft Marketplace)
Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.
2 tags are required - add them in the tag section next to the title above:
Feel free to delete this quote section after adding your appropriate tags.
ISSUE DESCRIPTION
Description of the issue:
It is impossible to activate Community-folder items inside “my library”, they remain in the status “installed” and “not available/unavailable”. The item names are not displayed next to the items. Taking a look into the Content.xml shows, that each entry is duplicated with each restart of the sim, not only the “community”-entries but also the “fs-20” entries. The workaround described in content-xml-duplicates-entries-on-every-start does not solve the problem.
[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
The issue concerns especially the use of the community folder, I tried it by reducing all items except a few officially bought from other stores and described as “MSFS2024 compatible”. The Content.xml corruption occurs even in that case.
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every time I restart the sim, Content.xml gets more corrupted.
Additional Information: I choosed to change the Community folder location using the Sim-settings menu.
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
- (Sim not yet running) Add one scenery or aircraft to the community folder, (no matter if from other stores and compatible or from the community)
- Start the sim and try to activate the item
- Stop the sim
- Start the sim - item ist still not activated
- Take a look to Content.xml
YOUR SETTINGS
If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
What peripherals are you using, if relevant:
not relevant
[PC Only] Are you using Developer Mode or have you made any changes to it? No Developer mode
[PC, MSFS 2020 Only] Are you using DX11 or DX12?
MSFS 2024
[PC Only] Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version:
Not relevant, NVidia RTX 2060, newest driver
[PC Only] What other relevant PC specs can you share?
Intel I7-9600, 64GB Ram, Windows 11.
MEDIA
Please add a screenshot or video of the issue occurring.
[END OF FIRST USER REPORT]
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
•
Provide extra information to complete the original description of the issue:
•
If relevant, provide additional screenshots/video:
•
Anyone can verify if todays small patch fixed this?
One thing you could add to check if the addon is a 100% MSFS24 build package (and not a compatibility mode version) is add this "package_order_hint": "", string to compare if "builder": "Microsoft Flight Simulator 2024", should be removed or not.
Or, if you are bored a white/blacklist. 