richboy2307

Ok. I'm hoping that resolves it for you. That's fine, it will vary per sim and installation. But just delete everything you see there. It will all be re-generated on next launch of the aircraft. Do remember to re-do your throttle calibration as that too will be reset. Yeah that is the issue I'm afraid. Regrettably, from our testing so far of reported crashes, very few of them are reliably reproducible as they're very case-specific instances and require close matching of conditions to reproduce. If we can reproduce the crashes, we can observe them via debugger and then resolve them. However without that, we're guessing at best and there is no way to verify that any fix is even working. Nonetheless, we are committed to resolve these instances of WASM crashes and improve stability for all. The team is working tirelessly to that end but we also require your help to report them as they happen, especially the reproduction steps. Thanks!

If you find yourself stuck in a text box on the MFD, try using the KCCU ESC key If its on an OIS text entry field, you can click anywhere outside the text box to exit the input mode. 2025-03-05 15-29-39.mp4 If the OIS window is not in view, use the sim's toolbar camera window to move to a view that will have it visible to do so. Sorry but unfortunately you have experienced a WASM crash. For more information on what that is please see linked guide below. Regrettably, from our testing so far of reported crashes, very few of them are reliably reproducible as they're very case-specific instances and require close matching of conditions to reproduce. Nonetheless, we are committed to resolve these instances of WASM crashes and improve stability for all. The team is working tirelessly to that end but we also require your help. In case you experience a WASM crash, please do not close the sim immediately. Use the below guide to properly report the necessary information and reproduction steps to us. Thanks!

@CR7 Thanks. Yes users have reported this issue and we have addressed identified causes in the v1.0.1 update already. Can you confirm you cleared your WASM folder before launching the 1.0.1 update? This will force a fresh WASM Compilation and ensure you're running the latest code. If not yet done, please try now: Over the past few hours we've tried to reproduce your crash internally and via our other testers but not able to do so. Personally I've tried to import over 50 times, on both SIM DEFAULT and NAVIGRAPH navdata sets and am not yet able to induce a WASM crash doing so. It would be great if you could record a video as below of the crash happening with your console window open in order to help us exactly recreate your steps. 2025-03-05 15-19-42(1).mp4 Thanks!

Thanks known issue of STEP ALT not clearing after completion, already logged.

Hi @aljina I'll pass on your feedback for alternative sources for ATIS. But the way it is currently programmed requires CPDLC to pull this data via Hoppie. There can be delays in receiving this data depending on server workload. Just for clarification, after you have entered your Hoppie ID, you do not actively need to connect to any network. Simply head to ATC COM > D-ATIS page and submit a request. Depending on the network chosen on the CONNECT Page, if a D-ATIS station is online, the data will be pulled from that station. If not, then it will fallback to METAR by default. In case you're trying to poll D-ATIS from a station on VATSIM/IVAO that is NOT split into Departure (_D) or Arrivals (_A), then you should select NONE in order to poll their D-ATIS. The feature implemented has no tangible effect on any of those factors, especially memory usage or additional applications as you do not require any additional software to be installed. Thanks!

Hi @rstwx That sounds like corrupted Navdata. Can you confirm what navdata option you're using on the OIS Settings page? If navigraph, try updating the navdata or using Sim Default first. For more information see: Thanks!

Thanks reported.

Hi @DiscoStu Sorry but unfortunately you have experienced a WASM crash. I have tried a to reproduce your issue but not yet been able to induce a crash by doing the following: Trying both Sim Default / Navigraph Navdata Swapping secondary flightplans (sim default or navigraph data) into active a few times Trying in climb, cruise or descent phases Trying to also match what's seen on your FMS as having a DIR TO leg active and then swapping runways. Regrettably, from our testing so far of reported crashes, very few of them are reliably reproducible as they're very case-specific instances and require close matching of conditions to reproduce. Nonetheless, we are committed to resolve these instances of WASM crashes and improve stability for all. The team is working tirelessly to that end but we also require your help. In case you experience a WASM crash, please do not close the sim immediately. Use the below guide to properly report the necessary information and reproduction steps. Thanks!

Hi @TPGiovanni If you're using TCA Airbus Throttles ensure you're using the Throttle 1 Axis (0 to 100%) and Throttle 2 Axis (0 to 100%), as well as the REVERSE ON AXIS = YES selected on the throttle calibration page. Normally that should be enough, then you run through the calibration process. As you make changes, it should save to the ThrottleData.ini file dynamically. If not, its usually due to the sim lacking proper write permissions (Windows UAC). Try running the simulator as admin. As you may have already seen, paths and guidance on how to conduct the calibration can be found here: In case you're still having issues, please share Screnshots of your control bindings assigned to Throttle and Reverser functions Screenshot of your OIS Throttle Calibration page Your Throttledata.ini file Thanks!

Hi, Thanks printer functionality is planned for the ULR update. Can you please elaborate on the issues and provide screenshots/reference for the observed behaviour so I can share with the team. Thanks!

Hi @flightcpt.th That seems like your WASM is not initializing on spawn so any part of the aircraft that relies on WASM will equally not function as intended. The WASM initialization is handled entirely by the sim on first launch to compile the code into necessary .DLLs in native code. Please try the following exactly in this order: Close the sim. Clear A350 WASM folder ( https://forum.inibuilds.com/topic/24996-how-to-clear-the-wasm-folder/ ) Rename your current ``Community`` folder to ``_Community`` Create a new ``Community`` folder, and copy only the ``inibuilds-aircraft-a350`` inside it. Launch the sim and spawn directly on a runway. Wait for WASM compilation (this may take up to 20 mins on first launch, this is normal, for more info: https://forum.inibuilds.com/topic/25259-help-stuck-on-loading-screen-long-loading-times-on-first-launch/) Once the aircraft has loaded in, verify that the systems are working. Close the sim and restore your original community folder by - Delete the new ``Community`` folder - Rename the old ``_Community`` folder back to ``Community`` Then you may continue to use the sim as normal. Spawning on a runway directly on first launch, without any other addons will force a clean WASM compilation. Then from next launch onwards it will not need to re-do this process. Let us know the result. Thanks!

Hmm, thanks reported.

Hi, CRZ Winds are currently not imported for LAT/LON or FIX type waypoints. Team is aware of this issue. Thanks!

Thanks for your suggestion, I've forwarded to the team.

Hi @CR7 Are you having this crash repeatedly upon F-PLN import or only one instance? If you've had it more than once, are you getting it specifically on this route only? Or can you reproduce the crash on any import. Thanks!

Hi Thanks team is aware and looking into this. Its to do with Navigraph Authentication token (on the OIS code) intermittently re-setting or not working as intended in some instances. In case you're having issues please try to Reset Navigraph Token by following the instructions below: Thanks!

The Fenix works externally to the sim, with all data lookup and ILS signal calculations also running external to it. We understand your frustration, however there are sometimes limitations to doing things internally within the sim environment in the interest of cross-platform compatibility. These issues of sceneries affecting availability of procedures/data is for the most part a sim issue and will affect any Aircraft who rely on the sim for this basic function. The plane comes with a Cycle 2303 data bundled by default. If you have an active Navigraph Subscription, it is recommended to update to the latest navdata cycle via the OIS. Instructions here: Glad you found it. Yeah not sure why OPST scenery is affecting this but glad you found the culprit. Worth reporting to the maker of the scenery as well. As the solution has been found I will lock this thread now. Solution: For anyone else coming across this thread, please follow the best practices mentioned above to set ILS IDENT and in case of issues try with an empty community folder to rule out conflicts. Thanks!

Hi, The autopilot disconnects due to excessive roll/pitch, or overspeed/stall conditions, or continuous user input on primary flight control axis The above conditions can be caused by abrupt "live" weather changes, or sim AI assistance options, or noisy axis that cause phantom inputs, or conflicting keybinds on trim/primary flight controls (usually keyboard) triggering unintentional input, or conflicting keybinds relating to AP disconnect triggering unintentional input, or momentary performance hiccups that lead to erroneous CFD data triggering the above conditions Just for some context, I've done 2 this weekend, and 9 total 12hr+ flights without any such issues. Collectively amongst our testers we have over 1000+ hours of successful flighting prior to release, with many long-hauls both real-time and accelerated via time compression. Not to mention the countless other customers out there enjoying these flights as we speak. So no, there was no fundamental issue that was overlooked or untested in that regard. There are however lot of variables to this equation (hardware, peripherals, control setups and server connectivity etc) and we are monitoring user reports of such issues. We hear your feedback and are working on a user option to inhibit the realistic AP disconnection logic in the interest of ensuring flight completion. In the meanwhile we recommend users use "LOW" turbulence settings, ensure all AI assistance options are disabled, verify their control bindings as well as use the "AFK mode" on OIS Simulation settings page such that the sim may pause in case of AP disconnection. Thanks!

Ok thanks, I was able to reproduce the issue using Navigraph navdata and specifically pulling RBO via IDENT. Logged.

Hi @henkhugo I am not able to reproduce your issue. Just tried on both Navdata sets in both FS 2020 & 2024 (with Asobo FACT scenery). Able to receive proper indications on the PFD and arm APPR mode. Please try with an empty community folder, in case your scenery is causing some conflicts. Thanks!

Hi @cellomike 1. As others have already replied, use the KCCU arrows or your physical mouse's scrollwheel over the KCCU scrollwheel to navigate dropdown lists. This is by design. 2,3,4,5,6,8,10,11 Thanks reported. 7. reported that P.POS option should be conditional, i.e. possible only if aircraft is already on an offset segment at the time. Otherwise default START WPT is current TO waypoint. 9. Can you please clarify what you mean by this one? Preferably provide some screenshots/reference for current vs expected behaviour. As for your personal observations regarding handling, I've shared internally for further review. Thanks for your report!

Hi @Harry320 Thanks for your report. That is a WASM crash. Can you please use the below guide to check your console for WASM error message received right after it crashes? Also please include the reproduction steps. I tried a few myself on the ground and in the air but didn't get a WASM crash. So the information provided will help us to reproduce and solve the issue. Thanks!

@RTK1972 That sounds like your installed scenery is having a conflict with the default Navdata. The iniBuilds A350 Airliner comes bundled with an older Navigraph AIRAC data (2303) by default as part of your purchase. The subscription is required to update to the latest, however without one you can still use the older cycle. Thanks!

Hi @Dazza/ @RTK1972 Are you using 'SIM DEFAULT' navdata or 'NAVIGRAPH' on the OIS OPTIONS - THIRD PARTY page? For the 'SIM DEFAULT' navdata, the ILS autotune feature is dependent on the scenery add-on used having properly defined the ILS frequencies for each runway. The ILS itself will exist and function, but as its not tied to the runway, it will simply not be autotuned. Best Practice - Approach Preperation As part of your descent preparation, MFD FMS NAVAIDS page Verify the correct ILS station identifier (IDENT) is shown. - Refer to charts to find the IDENT of your specific ILS. - If the field is not properly populated, manually input the desired IDENT. - The FREQ and CRS fields will update automatically upon entering the IDENT. E.g. For FACT ILS Z RWY 19 approach, we'd enter the ILS IDENT of 'KSI'. EFIS Control Panel - LS push button Verify that the LS button is pressed in and lit up green when passing 10,000ft. This will help ensure that approach guidance is shown on the PFD. When you are in range, the the tuned ILS IDENT, FREQ, CRS and DME (where coupled to the same station) will be shown on the bottom left corner of your PFD. You will also see the LOC/GS guidance diamonds. Thanks!

Hi @Speedrick007 You can click on the doors on the diagram directly of the OIS GROUND page to toggle them. Thanks!