IniSteve

We sometimes see an issue with the MSFS cache not clearing itself after installing third party scenery. A good way to manually refresh the sim cache is by clearing your Scenery Indexes - To do that locate your folder by following the path below: MSFS 2020 MSFS 2024 Then delete the contents inside but leave the folder intact. The indexes will rebuild on next load of FS. This should solve the issue.

Hi. We'll take another look and see if this is reproducible. Thanks.

I suspected that. As we learned in yesterday's dev stream, the texture loading with xbox is getting a refinement and hasn't yet pushed to users. The hope is wee see some improvement once that happens. IN the meantime, I have been able to get the textures to load clearly by switching to external view and back after a sec. That seems to refresh the cache. Sorry I don't have an immediate solution.

Hi Leon. is this on Xbox or PC?

Understood. The real world mechanics and pilots we've consulted with say the speed is accurate but I imagine it will also vary on a number of things such as hydraulic pressure in the systema or age, etc. Perhaps the aircraft in XP is newer thus works faster 😉

You'll have to ask Microsoft as it's their aircraft 🙂

Hi. A few questions - Are you on navigraph or default data? Are you selecting a runway first or SID/STAR? (The correct proc is to start with the runway, then select sid then transition (if avail) then *insert) Our testing team has flown well over 100 flights on the current build and have not seen this issue so I'd like to figure out why it's not working for you. Thanks!

Just to ensure I understand clearly, do you feel the MSFS animation is too fast?

HI. Can you confirm the overhead switches for Pitch Trim are on? These need to be engage in order for the front panel to display data

Hi. I've logged this and will pass it on to the team. Thanks.

Hi. Under "User Experience" in the ASSISTANCE OPTIONS section of the settings, ensure "Aerodynamic Visualization (CFD)" is ticked off -

Hi. Have you tried logging into and out of your simbrief account? Sounds like there is a caching issue on their end.

There should be a tab that shows "debug Log" on the homepage

Thanks for the update.

We are testing an update currently that hopes to resolve a number of issues, including this one.

Hi, I've logged this and pushed it forward to the team. Thanks.

Hi. We can certainly consider it but the worry might be running into VRAM limitations on the console. I will pass it on to the team and see if there is something that can be done. Thanks! 🙂

Hi. I will log this and we'll take a look.

Looks like you aren't on the latest update? (1.0.9) We moved to a scrollbar system vs multiple pages on the EFB settings page. You should see an option there as pmplayer indicated.

Hi, Our current plans don't include an expansion for Dubai. Despite that we're always considering future projects based on demand, new capabilities, or thoughts from the team, so never say never 🙂

HI, Can you reproduce this regularly? I tired this departure and the aircraft behaved as it should. Also, can you confirm was dataset you're using (Default of Navigraph?) Thanks,

Hi, Just tried this approach into Havana. The aircraft was able to maintain the arc at 260kias with no issue. (I even sped up to 280 to try and overshoot the turn to no avail) Can you confirm you're at or near a reasonable landing weight when performing this procedure?

Hi. This is a limitation (maybe it’s a feature) in the main sim. It happens with a number of addons and has been reported in the MS VR forum quite a few times.

Hi everyone. We're aware of a bug in the LNAV system and are working intensely to identify and resolve. The main issue we're up against is there isn't a steady pattern in when it fails. Earlier today I tried to reproduce this ~10x of which only 3 failed. 70% is still a poor margin for failure so we're combing through the code. I know that may be frustrating to hear since it's the weekend and you want to reliably operate the aircraft in the time you have but don't want to keep you in the dark or think we're not doing or best to resolve it quickly. Thanks for your patience with this.

This is the correct behavior for the flight management system. If the throttles are fully idle prior to 20' AGL the cue will not sound.