richboy2307

Hi @Wothan1967 Thanks for your report. Shared with the team. If you are experiencing issues meanwhile I'd recommend reinstalling the scenery. Apologies for any inconvenience caused. Thanks!

Yes team is still working on LOD adjustments per user feedback. This process takes time and will be done in a future update. As user you can't do too much beyond increasing the 'Objects Level of Detail" distance in graphics settings, but do note this will come with a performance penalty. Thanks!

Yes as mentioned by AndyM, there are no static aircraft included with this scenery. If you are seeing statics, check your MSFS settings and disable air traffic there. Thanks!

Hi @Argaeus Apologies for delay in reply. But if you cannot find an order number, just put "123456" as the order number and include the other requested information proving proof of purchase. Thanks!

Thanks reported

Thanks reported.

Hi @Muffwin Can you please confirm if you're experiencing any such issue as of v1.0.4 update? We believe this may have been on of those instances of crashes induced by memory allocation bug but would appreciate if you could let us know your experience such that we can be sure. We have been trying since v1.0.2 and even now on v1.0.4 and unfortunately none of our testers could reproduce the condition you saw (HOLD not showing up and then WASM crash after changing HOLD parameters). Attached is my latest attempt at the same on v1.0.4 below. Let us know if you're still experiencing this, and any further reproduction steps in case you do. Thanks! 2025-03-17 21-04-39(1).mp4

A video like this where you get the crash would be even more helpful. Like we've been trying all sorts of functions and undoing and erasing TMPY on all and not getting the reported crash. So more information to match the conditions such that we can re-create the crash would be helpful. 2025-03-17 19-39-49(1).mp4 Thanks!

Thanks reported.

Hi @geckuz Thanks for your report. Apologies you experienced a WASM crash. Been trying to reproduce your crash but not having any success as yet. I'm afraid it might have been something specific to the conditions or type of action being undone. Can you please provide the following information which would help in reproduction of the crash: Your specific route (OFP) What was the change made which you were undoing at the time of crash? The NAVDATA method used (SIM DEFAULT or NAVIGRAPH). Thanks!

Yep that is what we're working on as a backup. We are still hopeful for a native solution sim-side, as that is most beneficial to all products, and especially on Xbox with regards to Multiplayer/AI traffic. Thanks!

@mseder A screenshot or video please of what you're seeing would be helpful as I'm not able to reproduce the issues you're mentioning. What are you using to control the aircraft? Is there any specific key on your keyboard or keybind you're pressing just before the issue begins? Or does this issue start as soon as you click on any textbox on the EFB and then you can no longer exit it? We need more information please. Thanks!

Allow me to clarify It is not mandatory for you to clear your WASM folder each update as the sim should handle this for you normally however we are recommending users do so at the moment. The WASM folder contains files that are generated by the sim on first launch of the A350 WASM. These files then are cached for subsequent launches UNTIL either user clears them manually, or the aircraft is updated (so A350 WASM version changes) It does not matter when you clear the WASM folder (before or after the update), as long as its done when the simulator is NOT running, on next launch the WASM Compile will be triggered. Why do we recommend clearing WASM folder? We have seen user reports where the sim has not handled this process gracefully, or their initial WASM Compile was somehow corrupted, so as a troubleshooting step we recommend clearing your WASM folder for the time being. Thanks!

Yes in case you're having this issue verify your AIR DATA knob is in the centre (AUTO) position. That is the only time (other than failures) that such an ECAM would trigger.

Yes , team is aware of issues with Navigraph token authentication over longer flights, specifically in 2020 more so than 2024. They're looking into it. Thanks!