I have the same issue as Diegoamd and Silo01 mentioned. Both, the A330 and the A306 (Premium) freeze up the Sim, if one enters the ILS28 approach for LSZH into the MCDU. I tried both, with Navigraph and stock Navdata. The result is the same. It would be great if this issue could be resolved in the near future, as LSZH is the airport I fly into most often.

Hi @LtSnake

Moved to a new topic as this is a separate issue to the one where you had initially posted.

I was able to reproduce the WASM crash, reported.

Thanks!

Is there any estimate when a fix for this issue will be published?  All inibuilds aircraft are still experiencing the wasm crash when loading the ils28 in LSZH which is really annoying as it is the main landing runway in the evening.

This is still not fixed on the A330 or the 306, even with the newest sim update of msfs 2024. Quite infuriating, actually. The upside is, now it doesn't freeze the entire sim. It only freezes the mcdu. So you can at least quit to menu and don't have to restart the sim.

Please fix this on your products in a timely fashion! This absolutely needs to be prioritised. RWY 28 is the standard arrival to LSZH in evening hours. So this bug makes your product absolutely unusable for VATSIM flying in the evening. Also, I suspect that RWY 28 at LSZH is not the only procedure that has this problem.

Edited March 8, 20251 yr by LtSnake

12 hours ago, LtSnake said:

This is still not fixed on the A330 or the 306, even with the newest sim update of msfs 2024. Quite infuriating, actually. The upside is, now it doesn't freeze the entire sim. It only freezes the mcdu. So you can at least quit to menu and don't have to restart the sim.

Please fix this on your products in a timely fashion! This absolutely needs to be prioritised. RWY 28 is the standard arrival to LSZH in evening hours. So this bug makes your product absolutely unusable for VATSIM flying in the evening. Also, I suspect that RWY 28 at LSZH is not the only procedure that has this problem.

Yes, all the hype has been for the A350. 

This is a shameful way to support a product marketed as Premium. It isn't. 

Hello,

This was resolved with yesterday's big update (1.0.3).

Enjoy!