Cannot unselect “streamed” packages in my library

Find the Gaya folder in streamed and reproduce it empty in Community. Or did you not get it through the marketplace? There’s got to be a folder in streamed if you did.

There is no gaya EDDF folder.

I have also tried it with microsoft-airport-eddm-munich
Does also not work. I have created an empty folder called microsoft-airport-eddm-munich in the Community folder. It still shows it as streamed in the library.
Should it also work with default Asobo packages or only with 3rd Party addons?

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:
• relevant for every package I want to disable. Some packages are just unwanted and/or incompatible

I would presume that if you’re trying to override a default folder nested in a top level folder you need to create all folders in that tree in community. I haven’t tried it and am at work today so can’t.

Thank you very much man!!
I love this community that despite all the setbacks we are and will always be there to help each other!!

This simulator (Game!) is the most untested release ever experienced!

It occurred to me that MSFS 2024 might recognize content.xml as MSFS 2020 did in this path:

C:\Users\YourUser\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache

In the event that MSFS 2024 recognizes content.xml, think of a script to read the scenarios and with “true” or “false” so that the simu does not load it.

-1PowerShell (As administrator) (For users with Navigraph)
*Copy and paste (Enter)

Get the current user’s profile path

$userProfile = [System.Environment]::GetFolderPath(‘UserProfile’)

Define the paths for Community and Official\OneStore

$communityPath = “$userProfile\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community”
$officialPath = “$userProfile\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore”

Define where to save the Content.xml file

$outputFile = “$userProfile\Downloads\Content.xml”

Initialize the XML file

$content = @(‘<?xml version="1.0" encoding="UTF-8" standalone="yes"?>’)
$content += ‘’

Create lists for the packages and count the total amount

$firstPackages = @()
$normalPackages = @()
$lastPackage = “”

$priority = 2 # Start priority from 2 (priority 1 will not be assigned)

Write-Host “Processing the Community folder…”

Process the Community folder

Get-ChildItem -Path $communityPath -Directory | ForEach-Object {
Write-Host “Processing: $_”

if ($_.Name -eq "navigraph-navdata-base") {
    # This package goes at the beginning, priority 1 will be manually assigned later
    $firstPackages += "    <Package name='$_' priority='1' Active='True'/>"
} elseif ($_.Name -eq "navigraph-navdata") {
    # This package is saved for the end, priority will be assigned later
    $lastPackage = "    <Package name='$_' priority='0' Active='True'/>"
} else {
    # The other packages are processed normally, assigning sequential priority
    $normalPackages += "    <Package name='$_' priority='$priority' Active='True'/>"
    $priority++  # Increment priority for the next package
}

}

Write-Host “Processing the Official\OneStore folder…”

Process the Official\OneStore folder

Get-ChildItem -Path $officialPath -Directory | ForEach-Object {
Write-Host “Processing: $_”

if ($_.Name -eq "navigraph-navdata-base") {
    # This package goes at the beginning, priority 1 will be manually assigned later
    $firstPackages += "    <Package name='$_' priority='1' Active='True'/>"
} elseif ($_.Name -eq "navigraph-navdata") {
    # This package is saved for the end, priority will be assigned later
    $lastPackage = "    <Package name='$_' priority='0' Active='True'/>"
} else {
    # The other packages are processed normally, assigning sequential priority
    $normalPackages += "    <Package name='$_' priority='$priority' Active='True'/>"
    $priority++  # Increment priority for the next package
}

}

Now assign the highest available priority to the “navigraph-navdata” package

It will be assigned the last priority, which is the next after all the other packages

if ($lastPackage -ne “”) {
$lastPackage = $lastPackage -replace “priority=‘0’”, “priority=‘$priority’”
}

Combine all parts

$content += $firstPackages
$content += $normalPackages
$content += $lastPackage

Close the XML file

$content += ‘’

Save the content to the Content.xml file

Set-Content -Path $outputFile -Value $content -Encoding UTF8

Write-Host “File $outputFile generated successfully.”


-2 (Same but users without Navigraph)

Get the current user’s profile path

$userProfile = [System.Environment]::GetFolderPath(‘UserProfile’)

Define the paths for Community and Official\OneStore

$communityPath = “$userProfile\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community”
$officialPath = “$userProfile\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore”

Define where to save the Content.xml file

$outputFile = “$userProfile\Downloads\Content.xml”

Initialize the XML file

$content = @(‘<?xml version="1.0" encoding="UTF-8" standalone="yes"?>’)
$content += ‘’

Create a list for the packages

$allPackages = @()

$priority = 1 # Start priority from 1

Write-Host “Processing the Community folder…”

Process the Community folder

Get-ChildItem -Path $communityPath -Directory | ForEach-Object {
Write-Host “Processing: $_”

# Add the package with sequential priority
$allPackages += "    <Package name='$_' priority='$priority' Active='True'/>"
$priority++  # Increment the priority for the next package

}

Write-Host “Processing the Official\OneStore folder…”

Process the Official\OneStore folder

Get-ChildItem -Path $officialPath -Directory | ForEach-Object {
Write-Host “Processing: $_”

# Add the package with sequential priority
$allPackages += "    <Package name='$_' priority='$priority' Active='True'/>"
$priority++  # Increment the priority for the next package

}

Add all processed packages to the XML file

$content += $allPackages

Close the XML file

$content += ‘’

Save the content to the Content.xml file

Set-Content -Path $outputFile -Value $content -Encoding UTF8

Write-Host “File $outputFile generated successfully.”


IF THIS IS NOT THE ROUTE OF YOUR COMMUNITY AND OFFICIAL, CHANGE BOTH ROUTES

*YOU CAN ALSO CHANGE WHERE CONTENT.XML WILL BE (DEFAULT IN DOWNLOADS)

*Change from “true” to “false” to disable

Thanks for your effort. But that’s the developer job. We paid a lot of money for it.

You CAN Rename your “Custom” airport in your community folder to the same folder name within your streamed packages, make sure it is the same name. This will force the streamed data to read the one in your community first, the purchased airport from fs2020 marketplace will no longer stream, this is a temp workaround for now.

All chicken scratch to me. But if you made an app that would do this, i’d gladly open my wallet for you…:grin:

It’s super simple.
A command for powershell.
But it won’t let me post it properly here in the forum.
I will pass a .txt

1-Comando PoowerShell MSFS 2020 (Con Navigraph).txt (3,1 KB)

3-Comando PoowerShell MSFS 2020 (Sin Navigraph).txt (1,7 KB)

Change path to MSFS 2024
The community and official one in the powershell command

I apologize for my slightly complicated solutions.
I just try and pretend to help.
I always have and always will.
Greetings Toni
Happy flights!!!

Has anyone been able to get the LVFR KFLL buildings to appear? I did the workaround and disabled a bunch of add-ons but KFLL still appears flat.

Thank You so much , I was stuck at 98 percent and tried this and this was the solution ! It was an 2020 bredokk a320 liveries pack that was the culprit . Can’t believe we can’t simply deselect the so called addons that are clearly not viable for 2024 . Thank You a million! This should be pinned and addressed immediately to Asobo .

Check out this thread/topic

Thanks. Guess I just won’t play for awhile. There’s a buttload of folders in there haha.

Just wanted to update on putting the blank folder in community. I still have no working EGKK but I don’t know if that’s a general sim issue? I followed a video about fixing CTD’s that involved deleting StreamedPackages, scenery indexes, and rolling cache.

I noticed on load that StreamedPackages did not even try to re-download the Zinertek textures or the Origami EGKK package. So it might be a good idea to delete those after creating the blank folders just to make sure?

I still have no buildings at EGKK though.

edit: Actually I looked again and that’s not quite true, the buildings with the walkway overpass are missing but there are other generic terminal buildings. Guessing this is a sim issue then.

edit2: clarified that after wiping caches and streamedpackages that the content blocked by the blank community folder stuff no longer seems to re-download to streamedpackages.

I will not fly to 2024 until the issue of the inability to manually cancel push stream addons cannot be resolved,.

Whats insane about all of this is the fact that Microsoft seemingly did this purely to make it “fair” with marketplace-only purchasers (some PC but I imagine mostly Xbox) because people who have external products can just drop them into community. Mentioned by Raul from FSReborn here: https://www.youtube-nocookie.com/embed/xFHSJ_zLyYQ

So it caused this dumb cascading effect to loyal 2020 customers who could never get a fully vanilla 2024 package. There’s stuff people may have bought 2-3 years ago and don’t want anymore, and they might be stuck loading forever, not knowing its simply because of unrelated outdated 2020 junk that auto-streamed. Not to mention its causing issues and bogging systems down with zero tools to mitigate.

It should have been a vanilla install for everyone, if the market was down like it is, not accessing 2020 content would have been assumed anyway. It’s not like the devs had any say whether their stuff should ship with 2024 anyway, MS just sent it all. There are numerous other issues, but this one, Microsoft really shot themselves in the foot.