IniSteve

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.