Hello. I have MSFS 2020 and 2024. I have a problem with the approach to Yakutsk UEEE airport. In aircraft that use Navigraph Navdata for MSFS (2020 or 2024), there is no possibility to select any approach or SID and STAR procedure, e.g. in the A350 from Inibuilds that uses navdata msfs. There is only the runway itself. However, in Navigraph Navdata for PMDG, the procedures and approaches are already in the FMC. I do not have any scenery add-ons in the Community folder. How do I solve this problem? What should I do to make approaches appear in aircraft other than pmdg?
Hello! Welcome back to our forum!
Please try the solution in this post:
Let me know if this works better for you!
Kind Regards,
Malte
Where should I place this file in MSFS 2024?
Sorry, just realized the paths are different. Here is the path for 2024:
<community folder>\inibuilds-aircraft-a350\SimObjects\Airplanes\A350\attachments\inibuilds\Function_Interior_A350\panel
Where should I place this file in MSFS 2024?
Sorry, I updated my post but I guess you got the email before the edit was made?
My last post contains the path where you are supposed to place this within MSFS 2024.
It didn’t help me. Still no approaches.
And here is the path in MSFS 2024:
C:\Users###\AppData\Roaming\Microsoft Flight Simulator 2024\Packages\Community\inibuilds-aircraft-a350\SimObjects\Airplanes\A350\attachments\inibuilds\Function_Interior_A350\panel
Asobo in MSFS2024 I don’t know why they used a reduced version of navdata. PMDG has its own navdata and all airports and approaches are there.
Hello! I can see why. This is an issue that is specific to MSFS 2024, we shall see what we can do about it. I’ll get back to you!
Ah! To begin with, it does not look like you are using Navigraph data.
There is no 23L on UEEE - only 23.
Did you install and switch to Navigraph data in the OIS → Options → 3rd Party?
I don’t have a navigraph subscription. I checked it on pmdg with a friend who has a subscription. But in my opinion the default navdata in MSFS2024 should contain all airport data regarding procedures and approaches. And they come up with some reduced version. No sense.
Now I am confused. You are not using Navigraph data, but you are asking Navigraph for support? We did not develop this aircraft - iniBuilds did.
Your issue is likely caused by a mismatch between the scenery you are using and the navigation data in the simulator. This has resulted in issues like this since the release of MSFS 2020 and remains an issue in 2024.
The simple reason is that the procedures included in the navigation data for this airport are published for other runways (23, not 23L) - and thus, they will not show up.
And who makes navdata for asobo aircraft (e.g. TBM930, CJ4, HJET)? Isn’t it from navigraph? Why don’t these aircraft have these procedures and approaches? Doesn’t the A350 use the same navdata as the above aircraft?
Those aircraft use the data that is installed in the simulator. If you have a Navigraph subscription, you can install our data. Otherwise, you will be using the data that comes with the simulator!
That would depend on what you have selected in OIS → Options → 3rd Party.
Ok because I thought that asobo has a contract with Navigraph and Navigraph makes special navdata for their planes. So it turns out that it’s asobo’s fault. They have their reduced navdata and that’s why there are no airports and their procedures.
No, we have no such agreement.
Well, yes and no. If you have third-party scenery, then it is not Asobo’s fault. If you’re using stock scenery with stock navigation data, then sure! The stock data does include procedures, but not for 23L since that runway does not exist.
The default MSFS2024 scenery runway looks to be numbered 05R/23L, ASOBO issue.
Thanks for checking @srcooke !
That narrows it down a lot. This is caused by out-of-date scenery in a simulator that does not handle mismatches between scenery and procedures.
Quick fun fact: If you would use the Navigraph database within the iniBuilds A350 specifically, you would not have this issue!
For now, though, I am considering this topic solved! Thank you for the input again @srcooke .
Then they need to fix this scenery. On flightsim.to it is UEEE but only for 2020.
Feel free to let them know your thoughts!