Airbumps2501

Hi All, I'm at my wits end with this aircraft. On most flights now I'm finding that somewhere in the cruse the aircraft just stops responding. The Sim continues to function normally and I can escape and enter menus etc. I can click buttons in the aircraft but it simply doesn't response. Is this a WASM fault or is it something else? I've read about "Ghost WASM" crashes on the A350...... What can be done about this? I don't see this behaviour with other developer aircraft. Unfortunatly whilst you can click your way around the EFB, you can't actually action any autosaves..... I

As I type, I'm enroute from Sydney to Singapore in the A340. The sim is functioning fine but the aircraft isn't responding to any commands or inputs...its flown off track and there's nothing I can do but watch it continue. I can press buttons and the press in the sim..but there is no response from the aircraft. The EFB remains responsive and I can click my way around it, but button presses don't actually do anything. Is there anyway to bring the aircraft back from its ghost state? Or do we just need to accept this is going to happen with the A340? Whilst I understandin programming is complex, watching a recent interview with the CEO I see you've got over 80 people working for the company. These issues don't happen with Fenix or PMDG so I'm a little dubious its a "simconnect" issue... Really would like to hear whats being done behind the scenes to track down and resolve these issues.

Just had the same thing - Didn't realise there was such a thing as a "Ghost WASM Crash" but this is exactly what I just encoutered. I haven't touched the A350 in months and after two from four flights ended in this Ghost Crash I'm going to park the A350 back in the hanger and stick with aircraft that don't suffer the issue, i.e Fenix and PMDG.

Add me to the list of unhappy customers with the same issue. A 15 hour flight from KLAX to VHHH and at TOD the aircraft just stops responding. Dials spin, buttons press but nothing happens. The sim continues to run just fine but nothing out of the aircraft. WHat a complete bucket of junk.

Hi All, I've done four flights in the A340 now and on each occasion the take off calculator has given me the error "UNABLE TO FIND SAFE PERFORMANCE DATA". All takeoffs have been from major airports, EGLL, KCLT, KLAX and EDDM at moderate weights. In this instance, I'm AT KLCT trying to get it to give me take off performance for a flight to EDDM. Using the SimBrief take off calculator works fine - But the EFB one doesn't seem to work. Does anybody have it working or any suggestions?

Yeah I just noticed this too. Why would it call boarding / loading first....and then catering and refueling? Never seen an airline load the passengers and then open the doors to load catering!! Can we get this fixed in the next update please IniBuilds?

Would be nice to get some kind of comment from @IniSteve, @iniBuilds Team @iniBuilds Pablo or anybody else from inibuilds on this. It is effecting so many of us and there really has been ZERO communications or support offered. There are multiple forum threads abou the issue which has been very well reported for months (since SU4 Beta arrvied). Is this just going to be one of those issues thats easier to ignore than address?

Hi Eddie, Hows that closer look going? This is a pretty simple thing to replicate it would seem.

Yeah, starting at the gate is a work around but not a fix to the problem.

Steve this was reported by a number of members throughout the SU4 Beta period. The solution (as far as I know) was to always start cold and dark at the gate .. and even it didn't always work.

Does anybody know if this may be a WW SimAppPro issue or an issue with the way inibuilds is making the data available to SimAppPro? I have the same problem and REALLY REALLY REALLY want to just be able to use Spad.Next or Mobiflight to display the MCDU screen as opposed to having to use SimAppPro. Can we get a comment on this from anybody at iniBuilds?

@EddieThis issue has been fairly widely reported during the SU4 beta....... you should have been investigating months ago. 'I'm rebuilding my sim this week so can't provide you the crash log but I doubt there will be any shortage of people experiencing it.

This has been reported a number of times during SU4Beta and discussed in various forums. The response from people during the beta was, predictably "its a Beta - expect issues". Unsurprisingly, its now a problem for everybody....

Hi, I understand that at the moment the MCDU display data is only available to SimAppPro. I'm not sure how the protocols for this display work, but please please please consider opening the API to allow this data to be read by other apps like SPAD.Next or Moboflight. These apps are the backbone of a number of sim setups, particualary for simmers operating a lot of complex hardware. The current implementation (in 1.0.5) is buggy to say the least and the SimApp Pro applicaiton UI itself is...well, garbage.

Another vote for this. Excellent idea.