richboy2307

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!

Hi @lilycozi Thanks for your feedback. Would be appreciated if you could provide some specific examples with screenshots/video of what you're observing. Thanks!

Thanks reported.

Well you assume wrongly, as there's many users congratulating us for great performance on OMDB Enhanced and EGLL Premium compared to their 2020 counterparts, even running on laptops in some instances. Just some samples to back the above: But anyways, please paste a screenshot of your in-game FPS counter whilst loaded at the airport, along with your sim graphics settings for more clues as to what may be happening. Thanks!

Yeah this is what it shows during boarding (except the ZFW and FUEL LOAD fields, those remain empty unless you manually input or click the SIMBRIEF IMPORT on top right). However at the end of boarding the TOTALS and ZFWCG should update to reflect the final loaded value. Weird that its not updating, like the boarding complete flag is not being read properly by the OIS. Anyways, reported for the team. But please also your GSX settings in case its relevant. The settings on the GSX menu. Just the SIMULATION page You will need to disable the OIS "GSX INTEGRATION" option to be able to access this menu. Thanks!

Do you mean the view resets to top of the F-PLN or that the procedure is getting input at the top of your F-PLN? IRL these would be 2 entirely independent units run by separate computers. However this is not the case in the sim currently, they're both the same pages hence you see the scroll on both. Thanks!

@Timalshiwa Yes please try on 1.0.3 and let us know if you still have the crash after. This update contains various stability and crash fixes in the WASM code that should lead to less memory corruption/overrun situations which lead to the reported WASM crashes. You can just reply here in case you do have another crash with the full report. If no longer crashing, still do let us know here so we can close the thread. Thanks!

Can't say I've seen that. Just tried to load via GSX on 2020 before replying to you and saw the values update after GSX has successfully completed boarding. Can you confirm your simbrief plan is imported on GSX prior to boarding? If yes, can you please also share your GSX Settings so we can try to reproduce the above. Thanks for the feedback. I'll update the images/instructions to reflect the 2020 UI. But apart from the visual differences, its essentially the same in both sims, especially on the cosole. Thanks!

Thanks reported.

That almost sounds like you managed to activate a text box on the OIS somewhere, which then inhibits control inputs and other sim events from being triggered. You'd need to click elsewhere on the OIS screen to exit it. If your camera view is stuck, then use the camera tool on the toolbar to go to any preset views where you have the OIS in view to click on the screen and exit the text field. In case it happens again, some screenshots or preferably a video recording would be ideal to offer some more clues. But no, that doesn't sound like a WASM crash. Thanks!

If you're using GSX to request boarding/refuelling, it does so progressively and the values will only update after the process is completed by GSX. If you're a non-GSX user or don't request boarding/refuelling via GSX first, you can set your fuel/payload using the loadsheet's ZET ZFW and SET FUEL page. Apologies you had a crash but please try after 1.0.3 update as this has been focused on stability and addressing the reproducible crashes. However if you still have a crash, then please use below guide to Verify & Report the Crash with all the requested information. Thanks!

Hi @David Whittaker That is intentional to lockout assistance options as they can conflict with AP/FBW logic. Additionally we recommend disabling assistances per below for the same reason: See above link and ensure all the assists are disabled. Also ensure you have the appropriate OIS option selected if you're only using your rudder to steer. Additionally the A350 uses CFD such that aircraft has momentum and you cannot make sudden turns at high speeds with full deflection, instead you will cause the wheel to skid so you should ease into turns at 10kts or lower speeds. Thanks!

Hi @Timalshiwa Were you on update 1.0.3? If not, can you let us know if you still experience a WASM crash (and include full report as above) after the update. Thanks!

Hi @simon tiger Apologies you had a crash but a message like that is not helpful. Please read the message above yours and follow the instructions to make a proper report that will help us to investigate/reproduce your experienced issue and thereby solve it. Thanks!

Hi @C. Schaffhausen Apologies you still had a crash. However in case it happens again, please don't close the sim. Use the below guide to verify and report the WASM crash with all the requested information, especially screenshots and reproduction steps. Thanks!

Hi @Swisspilot1986 Can you confirm if you cleared your WASM folder after updating? While the sim should handle this for you automatically on first launch after an update/reinstall, we have seen it not happening for some users so you should also try to manually clear your WASM folders. Clearing WASM Folders - Delete all contents on the file paths (Work folder and all .dlls) - FS20: https://forum.inibuilds.com/topic/24996-how-to-clear-the-wasm-folder/ - FS24: https://forum.inibuilds.com/topic/24917-how-to-clear-the-wasm-folder/ If you still have the crash, please don't close the sim. Use the below guide to verify and report the WASM crash with all the requested information, especially reproduction steps. Thanks!

Yes this was one of the various reported WASM crashes addressed in the 1.0.3 update. The update was tested by members of the community who previously reported this specific crash and they confirmed they weren't having the crash anymore.Same was confirmed by our own internal testing and volunteer testers. However, in case you still experience any further WASM crash, please report per guide below so we can look into it ASAP. Thanks!

Hi @sk0941 Thanks for your report. Apologies you had a crash however this issue is not universally reproducible. From my own experience, I always use the ATC COM page on FO side on my VATSIM flights and have yet to have a WASM crash as a result of that particular action.0 Can you check if you are still having this issue after the v1.0.3 update? While the sim should handle this for you automatically on first launch after an update/reinstall, we have seen it not happening for some users so you should also try to manually clear your WASM folders. Clearing WASM Folders - Delete all contents on the file paths (Work folder and all .dlls) - FS20: https://forum.inibuilds.com/topic/24996-how-to-clear-the-wasm-folder/ - FS24: https://forum.inibuilds.com/topic/24917-how-to-clear-the-wasm-folder/ If you still have the crash, please don't close the sim. Use the below guide to verify and report the WASM crash with all the requested information, especially reproduction steps. Thanks!

Hi thanks for your report. Can you guys check if you are still having this issue after the v1.0.3 update? While the sim should handle this for you automatically on first launch after an update/reinstall, we have seen it not happening for some users so you should also try to manually clear your WASM folders. Clearing WASM Folders - Delete all contents on the file paths (Work folder and all .dlls) - FS20: https://forum.inibuilds.com/topic/24996-how-to-clear-the-wasm-folder/ - FS24: https://forum.inibuilds.com/topic/24917-how-to-clear-the-wasm-folder/ Thanks!

Thanks, reported.

Hi @Top27 Toggling the REVERSE ON AXIS should reset the throttle calibration normally. You can also do the same by deleting your ThrottleData.ini file and relaunching the sim. For keyboard you want REVERSE ON AXIS = NO IDLE to be at ~22% CLB to be at ~50% FLX/MCT at ~75% TOGA at 100%

That sounds like a possible keybind conflict (inadvertent inputs on Aileron/Rudder/Pitch or trims for either of those). Check your control profiles and ensure none are bound on any connected devices other than the one you want. Additionally, you may use the AP DISCONNECT PROTECTION option from OIS Simulation Settings which inhibits the realistic AP disconnection logic (due to control inputs or excessive rate of change on g forces) Thanks!

I am sharing below information in the interest of transparency, to show that we're committed to the cause to improve the experience for all our customers as mentioned above but this issue is a complex one. 100% reproduction on one system does not mean 100% universal reproduction. As seen in this video below, I've been trying a few times to reproduce the crash based on your report. Loading in to an airport, changing navdata sources and constantly re-importing. Have done so over 50 times without a crash as yet on A350-900 (v1.0.2) in FS20. Once we get successful reproduction, we can introduce debuggers/logging to investigate further code-side and weed out the root cause. We try this on multiple systems and across testers by sharing the reproduction steps with them. 2025-03-11 20-30-19(1).mp4 So, if anything else to add to help us better reproduce the above, would be appreciated. Thanks!

Hi @EilidhP Thanks for your report. Passed on to the team. I understand your frustrations, the team are committed to resolve these instances of WASM crashes and improve stability for all. WASM is complex and is limiting by the fact there is no exception handling, so in case of even a small error in code or data received, the entire WASM crashes rather than failing a specific part of the function. So to reduce WASM crashes as much as possible, you need code to self-handle all edge cases perfectly. We are working tirelessly to that end and reports like these help in this effort. Thanks for your time and patience meanwhile!