No sids and stars for msfs default aircraft

Have anyone else noticed that msfs deafult or planes based on deafult msfs aircraft (horizon sim 787-9, fbw a320…) is missing all sids and stars since the last update?

Does anyone know if there is a fix for this?

Hi @Loven08 ,

We’ve moved your topic into the User Support Hub.

The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.

If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.

If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.

All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.

Yea but this mainly has to do with msfs deafults. I just said that the 3rd partys also gets effected but they are not the primary issue. it is the deafult 787-10 and the deafult a320 neo that is the problem

I saw that you reported it for the MSFS default aircraft. But if it was a global bug, many users would already have reported it since last update (which update are you referring to ?).

I have loaded the default A320 at Miami and have access to the SIDs:

Have you disabled all your addons if any and tested again ?
Which airports have you tested ?, could you provide steps you are following to reproduce that issue ?

Also when creating a bug, please do not delete the template and fill in required information. It is very useful for the devs and users that want to try reproducing the issue.

Well, I don’t report problems like these too often, sorry.

I have tried it in ‘safe mode’ and it still seems to appear. I have tried the deafult a320, 787 and also the horizon 787 + the fly by wire a 320 wich are based on the deafult aircraft. I have tested it at ESGG, KJFK, RJTT and ESMQ (without 3rd party mods). Both in safe mode and without safe mode.

Here are some pictures of it in the deafult a320 and deafult 787:




I have only noticed it since the sim update 15.

Also I have noticed that when launching my sim and it serches for updated it always goes in the an update for a sec and then continues with loading in the sim. This has been going on for around a month maybe. It is like the sim is unable to update (but it could instan sim update 15 no problem.) this is a bit annoying as it goes out of full screen evry time i start the sim.

I don’t want to reinstall my whole sim if I don’t really need to as it takes so long to do that and my setting takes ages to correct.

I don’t know if anyone has a simple solution to this.

Which version are you running ?: 1.36.2.0 (SU14) or 1.37.12.0 (SU15B)
I am asking that because the other issue with the windowed mode you are commenting is a known one and is fixed in SU15B (planned to be released in May):

Regarding your SID/STAR issue, let’s wait for feedback/advices from the community.

I’m running 1.36.2.0 at the moment.

Yea, lets hope someone has any idea of what’s going on with my sim and if someone has a solution.

btw, it seems to be the case in the Asobo ATR-72 as well

Thanks for the help so far!

1 Like

A reinstal solved the no sids/stars issue

1 Like

Just the program, or data too?

Well, I uninstalled it via steam and also removed the Roaming file. That seems to have fixed it, it took quite a while to download everything again (with all my addons I probably get up to over 1TB of data…) but that seems to be the only thing I could do to fix it. And with all my addons back the problem has not come back so it seems like it wasn’t any addon that caused it.