BUG:FMS black screen after Destination change

[Mathieu Valade]

After a destination change to SFO, FMS Pilot side went black and copilot side is not responsive. Altitude is at FL340 and is going up 342, 344,346,348,340,342 on a constant basis. Basically all Avionics seems out of order. Print screen attach.

[richboy2307]

Hi,

Thanks for the the report. Sounds like a WASM crash.

Can you please detail how you changed the destination? Was it by entry KSDF/KSFO in the FROM/TO field on INIT page?

Also please share what navdata source (Navigraph or Default) and the original flightplan (e.g. VHHH/25L BEKO2B BEKOL A461 IDUMA IDUM3B ZGGG/20R)

 

Thanks!

[Mathieu Valade]

Hi,

So I used ALTN to enter KSFO as an alternate. (It was not the original alternate which was PHKO)

It's when I selected Insert after choosing the runway and approach in the FMS that the issue (bug) manifested.

 

Flight plan below:

KSDF/17L N0464F320 APALO6 APALO DCT ENL DCT KK51K DCT KK54G/N0452F340 DCT SLN DCT HYS J24 HGO DCT HVE J28 MLF J58 ILC DCT LIN J84 OAK DCT BEBOP/N0447F360 R464 BITTA INOYI1 PHNL/04L

Edited May 27 by Mathieu Valade

[S4nt0ss]

Having the same issue while programing the alternate route. using navigraph latest, route as follows. LEZL/27 HIJ2P HIJ M30 PARKA N858 DGO DGO1C LEVT/04

alternate LEMD/32R DGO3A DGO DCT NEA DCT NONTU NONTU3C

[skydiver6547]

I confirm having the exact same issue every time i  activate altn airport. I would appreciate if you could fix the bug.

 

Thanks

[richboy2307]

The team is aware of this issue of WASM crash when making changes to the ALTN airport/procedures and working on it. For the time being we recommend using the SEC F-PLN instead, and not using the ALTN feature.

Thanks!