KASE Missing Approaches

[poliver]

I am using the Working Title SR22T in FS2024 and was planning a flight from KHND to KASE, and although the charts are showing in Navigraph Charts, I cannot select any of the public approaches (I am aware of the public and special authorization approaches) in either the EFB or on the G1000 itself. It’s as if the approaches don’t exist. The only options are visual approaches into either runways 15 and 33. The STARS are showing with no issues.

I have attempted to troubleshoot by extensive searches of people with the same problem and it has come up short. I have uninstalled, deleted community folders, and reinstalled Navigraph hub, updated the AIRACS, and it still is showing the same problem. The G1000 on the SR22 is connected to Navigraph, and still no instrument approaches are able to be selected, but the charts are available.

Using the 3rd party version of KASE from Orbx.

There has to be a way to get this working. This is only the latest of problems I’ve had with FS2024 since coming over from P3Dv4 a month ago. I’ve spent more time trying to fix things than actually fly. Is this just a case of FS2024 prioritizing it’s own inadequate navdata over Navigraph’s, or is it something else?

Paul

[NAVData]

Hi Paul,
First of all, thank you very much for your report and the details. May I have one question?

When you use the stock KASE (so without the 3rd party scenery) do you see the approaches than (all with our data installed)?

Cheers,
Richard

[poliver]

Hi Richard,

Thanks for replying so quickly. I just uninstalled the 3rd party scenery and the approaches are now showing up, including the authorization only approaches. Is there a way to work around this?

Paul

[NAVData]

Hi again Paul,
Thanks for testing - in 99.9% it´s a scenery issue, rather than a navdata issue.

ASOBO/MS has changed the way to prioritize the loading order of third-party sceneries and third-party navdata. That means, both must be fully SU3 compatible, so that this new (by the way great) logic works correctly on the systems.

I can´t say if the 3rd party scenery is really SU3 compatible.

What does this mean (sorry, when it is a little bit technical):
The scenery must have the new attribute package_order_hint set in the manifest.json file. When you examine our manifest.json file, you will see this new attribute with our specified value.

{
  "dependencies": [],
  "content_type": "SCENERY",
  "title": "AIRAC Cycle Base",
  "manufacturer": "Jeppesen",
  "creator": "Navigraph",
  "package_version": "0.1.0",
  "minimum_game_version": "1.5.27",
  "minimum_compatibility_version": "5.27.0.112",
  "export_type": "Community",
  "builder": "Microsoft Flight Simulator 2024",
  "package_order_hint": "CUSTOM_NAVDATA",
  "release_notes": {
    "neutral": {
      "LastUpdate": "",
      "OlderHistory": ""
    }
  },
  "total_package_size": "10453953"
}

This attribute must be set, because this “tells” the sim what kind of package the sim is currently loaded. Again. I can´t say if this attribute is set, but it is worth checking.

Then, it is essential and HIGHLY recommended to delete your content.xml file once. Because also here, there was a change from SU2 → SU3.

We have written an FAQ for this “reset” of the content file:

FAQ - MSFS2024 (SU3 and above) - Reset your content.xml file

There is a new loading order logic since SU3, therefore it is essential to reset your content.xml file once, when ex: you miss airports you miss procedures you miss waypoints legs missing from the nav devices third-party scenery issues flightplan import issues … This file will automatically be recreated at the next start of the sim. You will find the content.xml file here (attention, the location is changed since SU3 - it´s now in a sub-folder, with your xbox-game-tag-id): Sim from Marketpl…

Also worth trying…

I´m pretty sure that when both “conditions” are set, the navdata are also working. I would start by resetting the content file and checking if that resolves the issue. After that, I would check the manifest.json file to see if the attribute is set. Depending on that result, inform ORBX.

Hope one of these tricks are helpful for you.

Cheers,
Richard

[poliver]

I reset the content file, but that didn’t do anything, although I think it might not be an issue with the scenery itself. I also checked the manifest.json for the scenery and did not see any “package_order_hint” attribute either (although it is set in the Navigraph base file).

However, I changed the “package_order_hint” attribute in the navigraph avionics G1000 manifest.json from “NONE” to “CUSTOM_NAVDATA” and that seemed to work. It even has the non-public approaches as well. Do you think that might have been the reason for the G1000 in the SR22 not having the approaches? Thanks for all your help!

Paul

[NAVData]

Hi Paul,
This seems somewhat random, as it has no connection to our avionics systems.

Here from the SDK:

Package Tool XML Properties

I have installed the scenery to check, and I can confirm now that this IS a scenery issue. The developer deleted the approaches. See here the cmd line (yellow line):

Here you see how the sim loads the packages:

1. fs-base-genericairports package (default data)
2. fs-base-nav package (default data)
3. navigraph-nav-jepp package (our data)
4. KASE 3rd party scenery
   
   

Now, when a 3rd party scenery has a DELETE departures, arrivals, approaches inside set, all these things (which are loaded before from #1-#3) will be deleted from the scenery. In this case, the approaches will be deleted, and therefore, you will only see the visual (which are default in the sim when no procedures are available). SIDs and STARs are not affected, and you can select them because the scenery deletes only the approaches.

So, it IS a third-party scenery issue, and I would report exactly that to the devs there. You and we can´t do anything - the only way could be to reorder the package above our packages, but you usually should avoid this manual reordering.

I hope that helps,
Richard

[NAVData]

As a cross-check, when I re-order the 3rd party scenery above our packages:

… you see all the approaches, which we offer:

So, it´s not a navdata-related issue; it is a 3rd party scenery issue, and the reason is that they delete the approaches, as described in my previous posting.

Cheers,
Richard