Latest Update Feedback – FMS Arrival Issue, Sound Balance, GPWS Volume and Nosewheel Sensitivity

[High_cloud]

Latest update feedback

I tested the latest update and found a few issues worth reporting:

• AIRAC / FMS arrivals
  AIRAC appears to be current, but when selecting an arrival in the FMS, all STAR and runway information disappears. This happened to me on an EBBR–LIMC routing, and the same issue also occurred for edwardthepilot during his stream. I have attached a screenshot taken from the stream.

• Sound balance
  The overall sound mix feels off. Reverse thrust sounds are significantly too loud and sound distorted.

• Cockpit / exterior sound transition
  The cockpit sound balance also seems incorrect. When both the cockpit door and L1 door are open, moving around in the cockpit causes the exterior sound level to change very abruptly from very loud to very quiet. The transition does not sound natural.

• GPWS volume
  It would be useful to have a separate GPWS volume slider. At the moment, the GPWS callouts are too quiet compared to the rest of the aircraft audio.

• Nosewheel steering
  Nosewheel steering feels too sudden and overly sensitive, almost as if the aircraft is moving on ice. Even a very small control input causes a disproportionately large directional change.

Edited March 17 by High_cloud

[Jonwait74910]

Good luck

[IniJamir]

Hello,

The sound issues are known about by the team and fixes are already planned to address those issues, as for GPWS callouts, I'll have to ask if those are product of bug of a bug or if those issues stem from something else entirely. Secondly were the arrival issues encountered specifically in this route pair or have they occurred else where, I flew KIND-ONT-OAK with no issues as well as RCTP to VHHX following the update and have yet to see this occur. Nosewheel steering I'll raise as well, I know between multiple aircraft I just use the same input and as such I have to change how much input I taxi with between developers.

Thank you 🙂

[Joerg Lange]

There are arrival issues too for example in VIJP. Approaches to 08 are missing and the STARs dont work. For example the STAR BUBNU1C shows the waypoints million miles away. Just try it, most of the time it isn´t even possible to select a STAR - RWY - combination  in VIJP at all.

Edited March 17 by Joerg Lange

[alexm90]

I have just encountered the same issue at EGLL ILS09L, LOGA2H arrival was fine, LAM inital approach to 09L was halfway there, (up to LAM34) rest was gone. Had to fly via HDG and the charts to the ILS, the aircraft intercepted the LOC and GS just fine. The MCDU went crazy, also on the ND the next waypoint was jumping back and forth.

[NavyKing1992]

Ini Team,

First question:

Are there any news on an update regarding the FMS as stated above? E.g. I can not selecting SID/ STAR procedure at LIMC.

With the A300 compatible version no problems at all.

Second Question:

Are there any news regarding the EFB Map which is still flickering?

This is a known issue since 2024.

Any news/ update would be appreciated. Please do not forget the "old" customers.

Thanks

Chris

[IniJamir]

2 hours ago, NavyKing1992 said:

Ini Team,

First question:

Are there any news on an update regarding the FMS as stated above? E.g. I can not selecting SID/ STAR procedure at LIMC.

With the A300 compatible version no problems at all.

Second Question:

Are there any news regarding the EFB Map which is still flickering?

This is a known issue since 2024.

Any news/ update would be appreciated. Please do not forget the "old" customers.

Thanks

Chris

For the FMS users have only been reporting this issue with LIMC and default NAVDATA as the runways have changed, I can't find that discussion from our discord but that's where I had seen that being listed for Default NAVDATA users

EFB Map Flickering known issue that I'll kick back around myself. Thank you.

[NavyKing1992]

13 minutes ago, IniJamir said:

For the FMS users have only been reporting this issue with LIMC and default NAVDATA as the runways have changed, I can't find that discussion from our discord but that's where I had seen that being listed for Default NAVDATA users

 

Thanks for the quick reply. Appreciate it.
What do you mean with the "Default NAVDATA"?
I always use the newest Navdata from Navigraph. Right now the AIRAC Cycle 2606 rev.3.
I also have the A300 compatible version. That FMS works fine. Even LIMC shows no issues...

Looking forward to your answer.

Chris

[IniJamir]

NavData for Microsoft Flight Simulator 2024 is sourced from NAVBLUE which is updated by Asobo, Navigraph utilizes data from Jeppesen.

[Joerg Lange]

I still don’t know what you mean with “default NAVDATA”.

To be honest, I don’t understand all the answers regarding the FMS arrival problems. Perhaps it’s a translation issue on my side. In this thread, several users report the same issue with arrivals at LIMC, VIJP, EGLL together with screenshot and informations about the STARs ans approaches they tried. For me, it looks like a systematic error.

Are the developers aware of that? Has anyone tried to replicate the problems by using the examples from this thread? Do u need further informations, examples or screenshots?

[NavyKing1992]

17 hours ago, Joerg Lange said:

I still don’t know what you mean with “default NAVDATA”.

To be honest, I don’t understand all the answers regarding the FMS arrival problems. Perhaps it’s a translation issue on my side. In this thread, several users report the same issue with arrivals at LIMC, VIJP, EGLL together with screenshot and informations about the STARs ans approaches they tried. For me, it looks like a systematic error.

Are the developers aware of that? Has anyone tried to replicate the problems by using the examples from this thread? Do u need further informations, examples or screenshots?

Agree, it seems to be always the same. They sell new products and do not really care about the old ones.

[alexm90]

On 3/31/2026 at 9:20 PM, IniJamir said:

For the FMS users have only been reporting this issue with LIMC and default NAVDATA as the runways have changed, I can't find that discussion from our discord but that's where I had seen that being listed for Default NAVDATA users

EFB Map Flickering known issue that I'll kick back around myself. Thank you.

I use Navigraph and reported the issue on EGLL (inibuilds 2024 Version) ILS09L. It was selectable but half of the LAM transition disappeared in the approach.

[IniJamir]

49 minutes ago, alexm90 said:

I use Navigraph and reported the issue on EGLL (inibuilds 2024 Version) ILS09L. It was selectable but half of the LAM transition disappeared in the approach.

Thank you for the added information 🙂