Content.xml duplicates entries on every start!

Bug Reporting Hub Miscellaneous
, ,
22

I need the original file or if you have a hex editor, open the file and see if there are weird characters. Like mentioned here. Content.xml duplicates entries on every start! - #11 by Cygnifick

Those weird characters wont show in a normal text editor.

23

For me the tool forced me to reinstall everything that was in the community folder.
So it causes more trouble, at least for me, then it prevents

24

Just opened the pre edited json and post edited json seems nothing is highlighted on the hex editor nor is there any syntax issue.

I think i’ll just reinstate the original json for now and opt to manually remove duplicated entries on the content xml.

25

Can you try one more thing? and add this line "builder": "Microsoft Flight Simulator 2024", above “release_notes” instead?


  "builder": "Microsoft Flight Simulator 2024",
  "release_notes": {
26

Just confirmed didnt work, same bug.

Have a feeling its a scenery issue.

27

so… we are reverting back to versions that ends up duplicating?
I used the tool for my addons, and it could explain why the airport was going invisible unless I moved close. I figured It was just a another new fs24 bug.

28

Works fine here, so no idea what is happening. And I dont have that airport so can’t test it.

Maybe the builder: indicates a different usage of LODS, 2020 version could use the old LOD way and this tells MSFS to use 20 or 24 system. (a big guess but looks plausible)

29

I think it was one of the reason why Asobo had to delay marketplace. Technically a period for scenery makers to recompile their fs20 scenery properly for fs24.

Another scenery i tested with the added builder line, i had terminal buildings and everything but it was missing flood lights so the whole airport apron was pitch black dark and my aircraft landing lights somehow could not illuminate the ground.

30

First of all thank you for finding this bug and to the author of the very useful editing tool.

However, just a word of caution here using this on scenery that was made for MSFS2020 and not updated.

Setting this marker may cause display issues.

I had FlyTampa CYYZ working perfectly in MSFS2024, simply copied the 2020 version over to my addons folder.
However once I set the builder 2024 marker in the manifest.json I noticed that I was getting severe LOD pop in on buildings and jetways, such that they would not appear until almost on top of them. There was also severe issues with the underlying ground image bleeding through the ground poly causing double markings everywhere.
Removing the builder 2024 marker fixed all the issues and the airport is displaying normally again.

I also noticed at other airports there was issues with LOD’s and pop in and I also experienced loss of airport apron lighting. YMMV of course but for me on the airports I tested I found major display problems.

I would not recommend adding this marker to airport scenery, which is a real pain because it now means I’ve got to continually edit my content.xml

31

Thanks for reporting another issue. So we can almost be sure that builder: is a indicator to use the new LOD system.

The bug is escalated and we need to wait for Asobo to fix it.

32

(post deleted by author)

33

Trying to use builder: “”; now

Edit: Okay, that doesn’t work with the duplication. :confused:

It’s becoming a bit of a mess (Asobo probably thinks the same) :rofl:

34

The problem now, some scenery/airplanes have been build with 2024 SDK. ^^

35

sure…, some minutes… it makes sense what has been said … i also got eddm’s apron dark without lights …
im thinking about "builder: “… 2020” … if there is an existing entry, e.g. by the dev it wont add a second … anyone tried with 2020 ?

36

(post deleted by author)

37

There is no other entry to use, I’ve checked a bit around in debug but the only other thing used was builder:“” by Asobo itself on some addons, but they are not community packages and Navigraph used it’s own string and that doesn’t work either.

38

Ive updated the tool

  • EDIT: Added 2020 builder tag instead of 2024… but it has no effect at all … dont prevent duplicates but also dont have negative side effects as the 2024 tag has

  • added a remove function to remove “builder” (only “builder 2020’s”)

  • Option to force removal off all… use with caution as it also removes the valid 2024 builder tags for native 2024 packages (like iniBuilds LEIB etc)

39

my bad … builder 2020 tag dont prevent duplicates…
i gave it up … i will live with a 2340GB xml file in the near future :slight_smile:

40

(post deleted by author)

41

nice … its all about a walkaround ^^

.i thinking about just replace it with my almost disabled everything file… i disabled all vintage, action planes and other action stuff like landingchallanges, sightseeing i never use :slight_smile: