Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

SU10 (beta) abandoned content.xml?

Featured Replies

I've read that SU10 would not use the content.xml anymore. In contrast to this, I have also read that content.xml can now be used for priority settings only. Is this summarized somewhere, does it need a user input? I became aware of this, when I read an add-on description where the developer wrote that the add-on would be placed with "very low priority". I'm wondering how they would do this automatically? I have the current SUI10 beta active but the time stamp of my content.xml is early August - probably a date before I've joined the beta.

Edited by Nemo

- Harry 

9800x3D (Strix x870e-E)  -  64GB RAM (DDR5 6000, CL 30)  -  RTX 5090, 34'' 1440p OLED HDR  -  Windows 11 Pro (1TB M.2)  -  MSFS 2024 (MS Store, 4TB M.2).

They removed the content.xml, that’s all I know. Apparently they manage content in a different way, but I can’t remember where I read it.

7950X3D | RTX 4090 | 64GB DDR5

8 minutes ago, Greazer said:

So will this break any old airports?

I can’t see why it would. Old airports, like?

7950X3D | RTX 4090 | 64GB DDR5

and conflicts between asobo/microsoft airports and 3rd party airports are they managed?

20 minutes ago, Greazer said:

So will this break any old airports?

I flew all the beta without the content xml. Only navigraph needs it for installation method (they will change it when su10 goes alive). 

I have had no issues without the content xml. Also I have tested using the content xml with only the fsbase and navigraph entrances, no issues at all

Regards,

Marcus P.

xaP1VAU.png

1 minute ago, vodka69 said:

and conflicts between asobo/microsoft airports and 3rd party airports are they managed?

Yes. They are managed. No conflicts seen at my end were they where prior beta when not disabling the default airports from MS (Like Leco had conflicts, they have gone now even without content xml)

Regards,

Marcus P.

xaP1VAU.png

You will have problems with Fenix as it will overspeed.

You have to manually make an entry 

<Package name="fnx-aircraft-320" active="true"/>

 

to avoid this.

I have no knowledge if they will fix it when SU10 will be official

Guenter Steiner
--------------------------------------------------------------------------------------

Betatester for: A2A, LORBY, FSR-Pillow Tester
--------------------------------------------------------------------------------------

12 minutes ago, vodka69 said:

and conflicts between asobo/microsoft airports and 3rd party airports are they managed?

I think it's a good idea to delete the Asobo version when you have a 3rd party. And btw, I haven't had any scenery conflicts during my nearly 2 month beta run. 

7950X3D | RTX 4090 | 64GB DDR5

  • Author

I don't expect any problems with airports. But regional or global scenery may be more sensible to priority settings. I don't know how MSFS handles this. For example the developer of MAMUDESIGN MARINAS - Boats and Piers in the World writes: "The package is gonna be loaded in the sim hierarchy at low level, so any other package more advanced/manually created will be able to exclude mine in their area" . Just being curious, if the content.xml is obsolete where and how does MSFS decide which priority should be used for a specific add-on?

Edited by Nemo

- Harry 

9800x3D (Strix x870e-E)  -  64GB RAM (DDR5 6000, CL 30)  -  RTX 5090, 34'' 1440p OLED HDR  -  Windows 11 Pro (1TB M.2)  -  MSFS 2024 (MS Store, 4TB M.2).

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.