Had my first WASM crash in the 175 today. Not quite ready for prime time.
I own it and think it is worth itāI paid more too. It is not perfect by any means but certainly flyable and a good learning experience because it is not a Boeing or Airbus cockpit. Only problem is while learning you donāt know if you are making mistakes or if you are dealing with a bug.
Exact same flight today EGPD-> EHAM and FMS/flightplan import works fine with no WASM crashes. Make it make sense.
So three flights in (E190) and no WASM crashes 
. Overall Iām quite happy with the experimental build. VNAV for the most part works fine on ascent and descent. Only those above/below constraints at EHAM to watch out for and manually edit in FMC otherwise it always picks the below constraint instead of the above constraint (leaving me late on descents/approaches).
My only other gripe is it climbing to meet G/S in APP mode instead of just waiting for G/S to meet it. I had that happen again today.
Overall though no reason not to give the experimental branch a try, VNAV is quite useable in itās current state.
I have to be honest. Even though I have sympathy and appreciation for developers, I have given up and I donāt know why anyone else still tries to fly those jets. Weāre not talking about something that came out a couple of months ago. There are so many good Jets and airlines out there that do work, so why even keep bothering with this thing after all this time? I liked a lot of its features and gave it a shot several times, including the experimental version, but there are just too many bugs that remain after way too long.
Because it is a lovely short-haul aircraft with three APUs 
Because thereās a dearth of modern aviation outside of Boebus and Airing, and because most modern simmers are afraid of gets with 6-packs and no magenta lines developers donāt do enough retro stuff. So weāre left hanging on the Embraer if we want modern novelty.
Sure- understandable. Thatās why I bought it as well. But until it matches up with the other jetsā avionics, VNav, bindings, etc. work, even if not āretroā, Iāll stick with the non-retro.Too frustrating.
Hey guys, Iām having an issue with the NavData Updater in the experimental version (see attached screenshot).
When I run the updater, it doesnāt update the AIRAC cycle to the current Navigraph REV2 version ā it stays on REV1 instead. After the update, the aircraft is also unable to capture the ILS localizer during approaches, even though the LOC signal appears correctly.
Whatās interesting is that if I completely uninstall everything and delete the WASM folder, the ILS works normally again. That makes me think both issues could be related somehow.
Has anyone experienced this or found a solution? Thanks!
So for reasons unknown, both the 190 is working and the 175 is working most of the time, but with the 175, I find that my key binding and joystick periodically do not respond, although if I go into a different screen (not MFSF), the bindings and joy stick will return. So weird. Anyone encounter this problem?