Yup same issue here with the MD-82.
Can also add GSX Pro Services remote control to that list as while sometimes the MD-82 loads, the GSX menu just outright doesnât appear in the MD-82 tablet aircraft services EFB.
Whilst SU4 seems to have addressed the see-through cockpit (LOD?) issue that was introduced in SU3, it now seems to have rendered the A350 unusable, in my view.
On my PC (high-end), I am told that all of the batteries are off, one engineâs master switch is off and unsurprisingly, that that engine has low oil pressure.
I donât think the LOD issue is completely resolved either, since lettering on some of the buttons can disappear either when I zoom out (not excessively) in 2D, or when I move back a little in VR. This seems to apply on all airliners.
As your post was merged here, I assume you found the solution to your issue?
If not, here again:
A known WASM bug is causing this. Fortunately it can easily be corrected until there is a fix. Just go to the maintenance menu in the EFB and replace batteries, service the engine, etc.
And your A350 is good to go.
Bit if you are using Navigraph, be aware that WASM bug also blocks the navdata update - it will hang.
Unfortunately this can only be solved for now by switching to the Sim default navdata on the EFB.
Else the A350 seems to work quite well. Had more than 20 hours with it in SU4.
1 Like
Hi folks,
This issue should now be resolved as of the latest 1.6.7.0 test build which was just released. For those who are participating in the beta and were experiencing issues with WASM add-ons previously, can you kindly confirm that it is now working correctly?
WASM API
- Fixed call to execute_calculator_code causing ctd
- Fixed WASI fd_write function returning an error when unable to write the requested number of bytes
- Fixed WASI fd_pwrite function missing conversion of iovs & nwritten pointers from linear memory to host memory (could lead to crashes)
- Fixed WASI fd_read function returning an error when unable to read the requested number of bytes
- Fixed WASI fd_pread function missing conversion of iovs & nread pointers from linear memory to host memory (could lead to crashes)
- Fixed fsVarsEnvironmentVarGet in Vars API
Thanks,
MSFS Team
1 Like
No luck for me so far, 777 still not working. No buttons can be pressed 
1 Like
For the PMDG 777, only the MINS and BARO knobs seem to be working. All the other buttons, knobs and switches donât work at all. Nothing happens when I click them.
2 Likes
Yeah, this isnât fixed. 777 is closer, but not there. A38X is still causing a complete freeze after Fly Now is clicked. Something is still going on that wasnât there in SU3.
1 Like
PMDG 777s not working. Canât turn knobs etc.
iFly Max not working. CTD/Never loads in.
Jetways not working (Bad jetway data).
Fenix working (still no Metars available though).
JFâs RJs seem to work (Just quick start-up).
GSX working.
BATC working.
FS2Crew working.
Night lighting was really good, imho. You see the individual lights much farther away - instead of the sepia-mask. No moon up. Dark where it should be dark. Some dark area bugs though: Suddenly no lights where there should be lights (on the ground). Looked like a lake - but was not (North of EDQM).
A/C lights seemed a bit brighter to me (Fenix). TWY+RWY-turn off LGTs brighter. At least seemed to me on my HDR. Good. BCN a bit too bright? Also the âhazeâ seemed gone when using Landing-LGTs. Was fine in previous SU4s too though. Good.
2 Likes
I cant be at my sim right now, but for people who are testing, have you tried deleting the wasm folder and let the sim regenerate the wasm folder?
Xbox series X. PMDG 777-300ER still spawning completely WASM crashed
After clearing out the WASM folder and letting the WASM recompile, the PMDG 777Fâs screens work but bound hardware and mouse interactions with buttons is still broken.
Thats a pity! This also happend before the the third build! So i guess nothings changed on that sideâŠ
1 Like
The night lighting is better than it was but still terrible. The radius of the light emitted on the ground is all wrong. Sharp cutoff and a perfect circle. Light fades in the real world. They need to get rid of the procedural floating lights and use real light sources. It has improved but it is still a million miles away from where it could and should be at this stage.
Sorry, in 1.6.7.0, WASM removed and recompiled, for the PMDG 777 series none of them work, everything is frozen, no buttons are accessible. However, it is a little better, the autopilot Control panel is displayed as well as the engine and Crew Alert Display.
1 Like
The Just Flight fleet seem to be fixed from my testing so far - Turbo Arrow, Tomahawk, Hawk T1, Avro RJ. I still need to test the Vulcan and piston Arrow.
Has anyone tested the A350 yet?
The FlightFX Citation X is still broken (too dark screens)
The ifly 737 max makes the whole sim frozen when you hear the loading sound, just before the fly now button
1 Like