richboy2307

Hi, This is a sim issue with loading nodes for pilots to spawn at. We have little control beyond assigning the node/spawn point for these models, the rest is handled by the sim. This would be why they're there sometimes, not the others etc. Thanks!

It is the control for the air vent above it. Increase/decrease the airflow by moving towards +/- respectively.

Follow this guide to change variants. Please note whilst streaming the addon, it may take some time for the download to complete with the necessary files. Or you can manually download the whole aircraft via My Library to grab it all at once. Thanks!

Thanks, reported.

If you mean the window shades in the cabin, no they're not operable for performance reasons. If you mean "plugging" the windows on the outside, thats done via the livery textures by painting over the liveries. There is no dynamic setting to plug them. Thanks!

Thanks reported.

Hi @NickMunro It is definitely working, though there is a difference in the degree of change in A340 vs the A350, primarily for performance reasons. Dynamic Weathering/Dirt requires nodes, and each node comes at the cost of performance. In the current implementation, all efforts have been made to keep nodes to a bare minimum, as such alot more of the dirt/weathering is part of the livery/base textures as opposed to "dynamic". One place where you can observe this in effect currently for example is on the seals for avionics compartment (and other maintenance panels on the belly): (Click to enlarge image) But your feedback is noted and relayed to our Art team for consideration. Thanks!

Hey @Benutzer Thank you for your detailed report and information provided. Unfortunately we've not been able to reproduce your WASM crash as yet across various test systems, with or without your autosave. Here is a video from one of the attempts: 2025-10-14 15-28-12.mp4 This highlights the difficulty in replicating these crashes, so if you notice anything we can do differently in trying to reproduce, or better yet can provide a similar video of your own with the console window open, we can attempt again to hopefully trigger it and catch it with the additional sim debugging tools attached! Thanks for your cooperation.

@sdflyer Please make a seperate post and with all the appropriate information as per this guide pls:

Hey, Thanks for your report. We're working on some of the reported items, but there are also just few things we wanted to clarify that are non-actionable, Checked, it is coded as a window between the intercept alt (3000ft) and 1460ft in the Sim Default navdata unfortunately. Under Navigraph navdata this waypoint doesn't even exist (it goes from DESIM direct to EDDV09L with a 3 deg glidepath). Not much we can do about it, but yes it should not have shown as a 3000 Magenta ALT CSTR on the F-PLN page in this instance which is what team is working on. Team is working on this. For this particular approach, it is just an ILS-LOC, not an ILS-LOC-DME so that is correct behaviour in this instance. The DME information for this approach is to be received via VOR1/2 tuned to the HAD (113.95). That is dependent on the scenery as that is where the information is pulled from. If the scenery has not assigned ILS Freq/station to the runway, then it won't get pulled with the procedures for it. The plane is not in go-around phase, hence no go around indications on the PERF or anywhere else. For the LNAV however, this is an "artefact" of sim-default navdata, in the way that its been re-done now such that the Go-Around waypoints start from right after the MAPt in the database, rather than *after* the runway waypoint. As the leg from MAPt to runway gets sequenced, its already in the "go around legs" segment and hence its turned green. The triggers are different for LNAV vs the rest of the go around logic, and there is no easy way to get around this for sim default navdata without also introducing other complications with sequencing. It is on the docket but unlikely something that can receive a quick turnaround. Ideally though the sim would revert to the old way of defining go-around segment legs. Yes it is. If you're having issues, please provide video reference of observed behaviour in-sim for team's perusal. Thanks!

Hey @Asher Yearwood Thanks for the additional information. See this video - it is at a higher altitude, but also tried at alt/position where you stated and still could not repro: 2025-10-08 17-44-39.mp4 I have also attached an autosave (EGPH_DES.bin) that we loaded into for testing, this was saved whilst trying to re-create your flight. See if you can reproduce the issue on this autosave maybe? You can copy the autosave into the paths below, then load it via the EFB Autosave menu. Would be helpful if you can also create a video recording like the one above with the console window open that will help us see when the WASM crash triggers. We want to get to the bottom of these WASM crashes but step one is being able to reproduce them. So your help is appreciated. Thanks! EGPH_DES.bin

Hi @Asher Yearwood We have tried our end to reproduce your crash but have not been successful. Can you please provide the following additional info Are you able to reproduce this crash? Either this one specifically or in any other situation Which waypoint did you try to insert a DIR TO - RADIAL-IN towards? What RADIAL-IN value did you insert? Where approximate you were (closest waypoint) when you initiated this Ideally, please provide an autosave file closest to your time of crash so we can load in to the same scenario and try to reproduce you crash. File paths for the autosave can be found in the guide here: Thanks!

Hi, Not been able to reproduce this issue on our end on SU3. Can you confirm if you're on MSFS SU4 Beta? We've seen a few other reports on the discord that seem indicative of an SU4 Beta specific issue introduced with their latest sim update. Thanks!

Hi @MediocreGorilla Thanks for your report. This is a known byproduct of the the compression and package delivery method used for marketplace streaming. We're working with Microsoft on resolution. Thanks for your patience meanwhile!

Thanks for reporting, logged for the team.