I've done probably 50 flights with the A300 without any issues but the flight I'm trying to do now causes all displays and flight deck systems to "freeze". The sim doesn't freeze, I can still control the aircraft manually but the autopilot doesn't do anything and the PFD and ND don't show any movement. Some buttons can be clicked but their action have no effect.

I'm trying to to LSGG-LFSB with the LUMEL 8K arrival, ILS Z 15 approach. I've tried the same route 3 times with the same results. Before the last attempt I uninstalled and reinstalled the A300 and updated my Navigraph navdata.

 

Any idea what's causing this? I've googled and found others having this issue but no real solution.

I had the same yesterday. I received a CPDLC message, then performance absolutely tanked for 10-20 seconds. When performance came back, all systems were frozen but some buttons could be clicked (without any effect), and I could control it manually just as you described.

I can confirm this issue. All Systems freeze during a flight. Controls of the airplane are normal.

Same happened to me just now.  I was deleting points on the STAR in flight and then the FMS went blank and all systems froze.  I was flying the PW version, have not had this on the other version.  See screenshot.  This needs to be fixed.

 

Thanks reported, we're looking into this. 

Meanwhile keep adding the instances where you notice it including
- What you did immediately prior to it crashing
- What version of sim are you on (SU14 or SU15 Beta)
- Route / Procedure if any it crashed on
- Navigraph or Default Navdata
- Screenshot/Video clip any if possible

Thanks!

Same happened to me right now. I was trying to get the ATIS via IDC and the systems froze. Im still in SU14.

Edited April 1, 20242 yr by bluefly330

1 hour ago, richboy2307 said:

Thanks reported, we're looking into this. 

Meanwhile keep adding the instances where you notice it including
- What you did immediately prior to it crashing
- What version of sim are you on (SU14 or SU15 Beta)
- Route / Procedure if any it crashed on
- Navigraph or Default Navdata
- Screenshot/Video clip any if possible

Thanks!

Thanks for looking into this. Further to my screenshot as per above, I am on SU14, using Navigraph subscription and was using the new PW version.  This happened when I tried to modify the STAR in flight.  I have done a lot of flights without issue in the GE version without any issues.

 

Regards,

For me this has (so far) only happened when trying to to LSGG-LFSB. I've tried 4 times now, both with the GE version and now after the release with the PW.

Each time it's been the LUMEL 8K arrival for the ILS Z 15 approach at LFSB. Two times I've had the freeze occurring enroute and 2 times after pushback during engine start.

 

After giving up on  this route I did LFSB-EDDP without any issues. Prior I've done 40-50 lags without issues.

Best advise. Just delete the aircraft. I reported this issue already twice (month ago).. And there some other topics regarding that same issue.. 

The issue is defentily known by inibuilds. It also happend on the XPlane A310 according to forum threads. 

I am very frustated that I have paid like 50€ and they are not fixing it. I just cant use the aircraft because it freezes too often.. 

Since January my A300 is parked at VHHH because I a m not able to contiue to OTHH. Latest bug I observed is regrarding the yel hyd system. The aircraft ist beautiful, but a full of bugs

On 4/1/2024 at 5:49 PM, danielfall said:

For me this has (so far) only happened when trying to to LSGG-LFSB. I've tried 4 times now, both with the GE version and now after the release with the PW.

Each time it's been the LUMEL 8K arrival for the ILS Z 15 approach at LFSB. Two times I've had the freeze occurring enroute and 2 times after pushback during engine start.

 

After giving up on  this route I did LFSB-EDDP without any issues. Prior I've done 40-50 lags without issues.

LSGG-LFSB is imposible to do. When calculating the performace a300 frozen, Msfs was running but plane froze. Inibuilds i spent 52 euro for this?????

This has happened again to me, I could replicate it twice now.  Trying to modify the STAR INBO8K for ILS02 at LPPT.  As soon as I removed a waypoint everything freezes.

I am on SU14 and was using the GE version of the A300 latest update.  This needs to be fixed please.

 

Thanks all, noted and reported.

We're looking into these CTDs and have already resolved some as of 1.1.1 HF1. However rest assured work continues to try and nail these.

Not sure if this is related, but I've had my ECAM DU1 screen just freeze today with a "NORMAL" message, that would not respond to any of the buttons controlling the display, like the Clear button.

Happened right after I hit the TOGA button on take-off.

Picture attached.

Luckily no impact on the FMS or the rest of the flight. Just no system messages.

VHHH still a no go. Selecting STAR arrivals will jam the FMC. Odd thing only 07R, 25L are available.

2 hours ago, chinjh said:

VHHH still a no go. Selecting STAR arrivals will jam the FMC. Odd thing only 07R, 25L are available.

And on the last yards to the runway the LOC pointer move away to the right and the plane try to follow this pointer and steers away, you have to shut down fast the AP and do a hand fly landing, hopefully they look at this problem..

cheers 😉

Edited April 25, 20242 yr by pmplayer

6 hours ago, pmplayer said:

And on the last yards to the runway the LOC pointer move away to the right and the plane try to follow this pointer and steers away, you have to shut down fast the AP and do a hand fly landing, hopefully they look at this problem..

cheers 😉

I just tried this out Hong Kong (Chek Lap Kok) Intl. Airport (VHHH) NavData for Three-runway System

It sort of fix most of the issues with missing runways of 07L and 25R and waypoints. But note some of the Loc pointers are still heavily missplaced and you would have to manually plot them or delete them to avoid jamming the fmc. I noticed my FMC jammed cause it was drawing up a lot of incoherent lnav directions whenever selecting any arrivals of 07R and 25L.

When getting ready to descent, instead of clicking the destination LSK to set STAR.... I clicked LSK for Alternate. Then the same issue reported in this topic happened.
BTW, what would be the proper procedure to go for alternate or retry a rejected landing at destination. Usually I do it by heading and ILS, but when I need to do RNAV I have I can´t reset the approach.

On 5/15/2024 at 6:54 AM, MarcusVT said:

When getting ready to descent, instead of clicking the destination LSK to set STAR.... I clicked LSK for Alternate. Then the same issue reported in this topic happened.

Hi what was the route used when you noticed this? I am not able to induce any WASM crashes by simply adding a STAR/APPROACH proc to an ALTN airport on the MCDU FPLN page.

Also please provide the Navdata source used (Navigraph or Default). 

On 5/15/2024 at 6:54 AM, MarcusVT said:

BTW, what would be the proper procedure to go for alternate or retry a rejected landing at destination. Usually I do it by heading and ILS, but when I need to do RNAV I have I can´t reset the approach.

See attached bits from FCTM.

Thanks!

Dear Inibuild

So now I have to report the same thing happening after updating to the latest version.
I purchased the A300 on day 1. Then I updated until 1.02. After that, I kept staying on this version because after each update, I have read from bugs at all the WASM and Fall out of the sky. That's why I decided to stay with the version I had installed.

However, after SU15 release, I decided to give the newest built a chance. I uninstalled the plane and delted also the work folder. After this I tried several time the flightplan, @danielfall is talking about. Same here. Each time I start Eng1, the whole display and buttons freeze. I always switch on first Eng2 than Eng1. Each time there, the plane stopped working.

After several attemps, I tried another flightplan from OIIE-LIRF. Here I was perfectly able to complete the whole startup procedure and take off.

Afther that I tried the LSGG-LFSB flight again, and again the same: FREEZE. To be honest, I never tried this route before but so know I do not know, If those freezes are occured by some Airports SID or STAR. I also did it with an empty Community folder and the INI blank livery: Flightplan was
LSGG/04 N0473F300 MOLU4N MOLUS N871 KONOL Z59 LUMEL LUME8K LFSB/15

So as Daniel, I am absolutely not able to do the flight LSGG-LFSB. I use Navigraph, but I don't know, if INI A300 takes my Navigraph Data or Sim Data. How can I check this?

I realy hope, you find a solution for that.

Kind Regards

Patrick

Oh and it's with both, PW and GE.

So tried it again.

LSZH-EDNY everything went fine. Then I selected EDNY-LFSB ILS15. Approximately 1min later, the A300 froze (not the sim]. So there is def. something wrong with LFSB ILS15. According to your changelog, it should be fixed with Version 1.02 but it's not. If I search LFSB in this forum, there are a lot of other users having it.

I hope you realy can fix this. LFSB is an airport I often use in RL and there are indeed A300 flying there.

Kind Regards

Patrick

Hi, are y'all using any scenery for LFSB as well?

I have just flown a flight with the route below, once in GE F and once with PW Pax, with Navigraph Navdata (2405 rev.1) on SU15, with v1.1.1 of the A300 without any crashing issues.

LSGG/04 N0473F300 MOLU4N MOLUS N871 KONOL Z59 LUMEL LUME8K LFSB/15

This is with a near empty community folder, no sceneries used for either airport. Not getting any WASM crashes throughout the route, even tried to change the STAR/APPROACH procedures multiples time in the air, whilst in a hold, from ILSZ15 to ILSY15 to ILSX33 to ILSY15, no crashes, and MCDU has changed the procs appropriately.

In any case, we do have a new update for the A300 which will hopefully address the issues you are facing. Enclosed is a post shared on our discord. Please try that update (once available) and do report back if you still face such issues. Thanks!

Using FSDT LFSB. RNAV15 is working just ILS not.

On 5/27/2024 at 6:18 AM, richboy2307 said:

Hi what was the route used when you noticed this? I am not able to induce any WASM crashes by simply adding a STAR/APPROACH proc to an ALTN airport on the MCDU FPLN page.

Also please provide the Navdata source used (Navigraph or Default). 

See attached bits from FCTM.

Thanks!

Thank you for this procedure, I'll try it right now. BTW, where can I get FCTM? It would save a lot of time here at forum 😄