After installing 2503 rev3, all the sid/stars are missing in these airports, it seems the deault aircraft are not using navigraph data but rather using ingame navdata. im NOT on su2 beta. nefore the update it was working but now it is not. any help? maybe with the secenery reorder tool but i dont know the priorities
Hi,
The question is, do you use a 3rd party scenery, or do you use the stock scenery?
When you use 3rd party sceneries, please remove them and try again to verify whether the data is there.
Usually, it’s a scenery issue that the scenery isn’t 100% MSFS2024 compatible. When you use 3rd party scenery, which developer is it from?
Cheers
Richard
Hello,
I’m using third party scenery from scenery TR. When I remove the scenery (LTFM) it says not in database. The problem is that 24 hours ago it was working perfectly but now after installing revision 3 it somehow only shows 2 waypoints sfter departure. I think the aircraft is not using the navigraph data, probably using lido data. Is there a way to adjust this from the package reordering tool?
I assume you have any other issue because LTFM is also included in our data, so you can also select it without a 3rd party scenery. The airport exists and can select when you have installed our data. So, is there any other issue on your system besides a navdata issue?
I will check if the LTFM scenery is compatible with MSFS2024 SU1.
Cheers
Richard
PS: I have no experience with the re-order tool, so I can’t help you here, I’m sorry
Hi again,
I have tested the scenery, and it is not 100% MSFS2024 SU1 compatible. The package_order_hint tag is missing in their manifest file, and therefore, the scenery will not be loaded in the correct order. Please report this to the scenery designer.
I have added it manually, and here is the result:
Airport diagram on the WorldMap with all runways:
… and here from the C172 equipped with the G1000 (stock aircraft):
I have used the OMED4D departure with the OSMEV transition, and you can see all the waypoints.
So, I can´t identify any navdata issue here; I´m sorry - the 3rd party scenery is working correctly when the package_order_hint is set correctly, but the 3rd party developer must do that.
I hope that helps,
Richard
PS: Be aware that some stock aircraft can´t handle the transition, so using one of the WT devices, like the G1000, G3000, or similar, is highly recommended. That’s the best reference for testing.
hello, thanks for the reply, i did what you reccomended and indeed it works with the wt instruments but does not work with the aircrafts like ini a330 or wt 787. any advice on that maybe?
well it worked for the 787, i have to select an invisible transition but for ini aircraft it doesnt work. im curious for istanbul that departures dont have a transition but approaches have transitions. but all in all most approach procedures are missing. only ils z are available, ils x and ils y are missing
Hello again richard, after some investigation, i feel like the sim is not using navigraph data at all. it is using the the default navdata provided on all aircraft. you can see that with navigraph installed, ibla4e departure shows IBLAL as the endpoint, which is not the correct waypoint as it was changed 1.5 years ago. i feel like the sim is not using navigraph data as i can select the same departures without navigraph installed in my sim so installing navigraph does not change anything
Hello,
I know, I crosschecked with fenix/charts/ini350 to see if it is iblax in navigraph database, you are correct. my issue is probably not related to any scenery or etc but rather the sim uses the lido data and disregards navigraph data. when it uses navigraph data, the sim correctly shows all the procedures correctly in every aircraft but i cannot make the sime to use navigraph data. as the sim uses lido data it shows as IBLAL not IBLAX. I hope that explains
Ah now I understood … Will check it against our data.
Cheers
Richard
1 Like
Hello Again Richard,
I am so sorry to reply this much to the topic but I think I found the issue. I realized that the issue happened AFTER installing the revision 3. I had a backup of revision 2 and tried that it is working now.
Hi,
After a few hours of analysis, we have identified a minor logical bug in the approach data for LTFM. Only this airport is affected.
We will fix it in the next few days and release a new revision. Thanks for your hint and also your patience. I will update you here when it is fixed.
Have a lovely Saturday evening
Richard
1 Like
Hi,
I have fixed the issue with missing procedures for none existing stock airports:
Revision 4 is now online. Please confirm that you also see all approaches into LTFM. Thank you very much!
Cheers,
Richard
1 Like
Hello Richard,
Thank you very much! I now see all procedures for LTFM in the sim with all aircraft.
1 Like
Fantastic—thank you very much.
It was indeed a small bug in the exporter, which we have identified thanks to your report! Thank you very much again for giving us the opportunity to improve our service/data.
Please let me know when you have any more questions and/or when you see any more anomalies.
Thank you very much & enjoy your Sunday,
Richard
1 Like
Hello,
I don’t know if this is caused by Navigraph or by Asobo but wanted to ask. As there is a new runway opened 06R/24L for LTFJ, there is a mod that adds the new runway to the sim but adding it removes ALL the procedures for LTFJ no waypoints no even Sid/star/approach names. when you select a runway it just says none. I am adding the mod links below. I would appreciate if you can try it.
Many thanks in advance for your help,
https://flightsim.to/file/1916/istanbul-sabiha-gokcen-international-airport base scenery
https://flightsim.to/file/66035/ltfj-sabiha-gokcen-airport-with-new-runway-and-working-gates runway fix
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.