richboy2307

Hi @BoeingSpeedbird I have moved the topic from MSFS 2024 to 2020 section as that is the sim you're using. This does sound like a WASM crash, however we need to determine if this WASM crash is a fault in the aircraft code (and thereby reproducible) or sim code (random, will happen sometimes but not always). Please see the information below to see if you can reproduce the issue reliably, and if yes, then please post exact reproduction steps. ---------- What is WASM? Why do WASM Crashes happen? These can be caused by either a) faults in the code, or b) in the way that code is executed by the sim. a) Faults in Code While we try our best to find and quash all bugs in code, we are still human. Mistakes or oversights can happen and sometimes these can lead the code to fail in certain specific instances, resulting in a WASM crash. These kind of crashes will be reliably reproducible, meaning you can have the crash nearly every time by executing the same code (e.g. by selecting something on the MCDU, or by pressing certain buttons on the plane, or by flying certain SID/STAR/APPROACH etc.) These types of WASM crashes are actionable, and dependent on your reports of the steps taken immediately before the crash happened. These, if reproducible on our end by following the same steps, can be debugged and usually resolved in a following update. b) Faults in the way the code is executed by the sim Since SU15, we suspect, there have been instances of "random" WASM Crashes caused by a "memory allocation bug", wherein the sim tries to reserve memory (for WASM) that it does not have access to, as a result leading to a WASM crash. These types of WASM crashes are difficult to reproduce and not something we can address as its not an issue with the aircraft code, rather just in the way the sim tries to store and execute it in some instances. These types of WASM crashes are not actionable on our part and would instead need fixes on the simulator's code (if possible). So why did you experience a WASM Crash? As mentioned above, we will first need to find out if the crash was (a) or (b). So you need to take note of exactly what you pressed or things you did, just before you noticed this crash happen. In case of MCDU Entries, we need the exact procedure entered, and at which step the issue happened (when you selected the runway; or the SID/STAR/Approach/Transition; or when you pressed insert after selecting which exact procedure) What systems stop responding, or what you cannot click after the crash is irrelevant as the whole WASM has already crashed, so anything using WASM will equally stop responding. Additionally, please see if you are able to repeat the crash by following those same steps. Once you know, you can mention those steps to us, and we can try to reproduce on our end to see if its actionable. Thanks!

Yes please verify your Flight Directors (FD) are running. On the ground prior to takeoff ensure your FCU is showing as in the image as well, with NAV mode armed in blue on the Flight Mode Annunciator (FMA) at the top of the Primary Flight Display (PFD) meaning that it will follow the MCDU F-PLN once airborne. "Armed" modes are always shown in blue color, whereas currectly "Active" modes are shown in green on the FMA. Also ensure the assists shown here are disabled, as they can also cause conflicts with Autopilot: Thanks!

Hi @ClanKilpatrick A. No. The 2024 Compatible Edition for now is only available for purchases made via inibuilds store (website or iniManager) or Simmarket respectively. You may request a permanent order transfer of your purchase to the iniBuilds Store using this form: https://inib.uk/order-transfer B. No. For Marketplace customers (PC/Xbox), as the FS 2024 Marketplace is not yet available, this is currently not possible unless you do transfer and make the upgrade via iniBuilds store after. As for Marketplace purchases/upgrades to FS2024 for Compatible/Enhanced/Premium editions of products in general, please see quote from below linked post: Thanks!

Hi @LukeFF The CPT side ET RUN/STOP buttons are mapped to L:INI_CHRONO_ET_STATUS, with a value of 2= STOP and 1 = RUN. The FO side is the same, except using L:INI_CHRONO_ET_STATUS_FO instead. Thanks!

Hi, please see linked post:

I believe it is INI_TILLER_DISC with values of 0 / 1 for pulled out/pressed in respectively.

Hi, Thanks team is aware of this one. The orientation of the lights was affected by one of the latest sim updates that changed some lighting properties. THanks!

Hi @SergioKlukas Can you please include screenshots with pointers as to what you're seeing? If you're talking about the N1%, the value at IDLE will vary depending on conditions, usually hovering around 20%. Thanks!

There is an LVAR list posted here for FS2020, I believe the same should apply for FS2024 as well: Alternatively, you can use the method mentioned further up in the post to access the Behaviours Dev menu and see switch-associated LVARs yourself live in the sim. Thanks!

Hi Thanks for the feedback, shared with the team. However for feature requests on Microsoft aircraft such as this, the appropriate place to post is on the MS Forums (Wishlist Section) as that decision rests with them. Thanks!

Hi, For more info see: Thanks!

Can you please share a screenshot (or preferably a video) of what you're seeing? Also please share your hardware (CPU/GPU/RAM) and sim graphics settings (Anti-aliasing mode used, resolution and cloud/texture/windshield settings). Thanks!

Please try loading into the aircraft now and see if you're still having the issues. Some of our testers reported the issue is no longer happening as of today. We believe it may have been related to the validity date format of this particular AIRAC cycle - the end date (23 Jan 2025) going into another year at the time this was initially reported (2024). However, now that we're in the same year, the issue is seemingly no longer occurring. We would appreciate if others could confirm the same. Thanks!

Hi, Unfortunately as this process is not entirely in our hands, we cannot provide any ETA for update availability via the Marketplace. The transfer requests have to be processed by both parties (original store and ours) so can take some time. Ofcourse with holidays period in between, some delay is to be expected for both of the above. In case you do not hear back regarding your order transfer by end of next week (check your email spam folder), please reach out to Direct Support with your original transfer request info : https://inibuilds.com/pages/contact Thanks!

Hi all, As mentioned on discord: For PC users, the community suggested workaround to this issue is switching Texture Resolution to "High" or "Ultra" for now. Thanks!

Hi @Errandil It's a known sim issue we are tracking that looks to be on the MS/Asobo side. It is not limited to just streamed aircraft, but rather a rendering thing. There is a thread here on the MS forums that you should post to for maximum visibility on this topic. For clarity, nothing has changed build-wise between pre and post patch with our aircraft so we're looking deeper into why folks are seeing this from time to time. For PC users, the community suggested workaround to this issue is switching Texture Resolution to "High" for now. Thanks!

Hi @Powie I would start by looking for conflicting control bindings for brake axis, particularly right brake. Also check for any conflicting control bindings for rudder (yaw or trim) as well as nosewheel steering. Have not seen this at all during testing, nor reported elsewhere so chances of it being an aircraft bug are low. In fact just tried at LFMN (ILS Y 04L) and did not have any issues (well other than the LOC/GS misalignment with runway but thats likely a scenery/navdata issue) 2025-01-03 21-48-54(1).mp4 Thanks!

Hi @eschoyen Does this issue also happen when you spawn on runway? I have tried spawning in at the gates and airports mentioned with the DHL PW livery and did not notice this issue. I suspect the following On spawn your aircraft is somehow going into "pushback" state by default, likely due to some keybind. Check your control bindings perhaps? Alternatively, reversers are being toggled somehow initially before the aircraft resets to cold and dark on spawn. Have you calibrated your throttles from the aircraft EFB? Make sure you do that and select "Reverse on Axis = NO" Thanks!

Thanks reported.

Thanks, reported

Out now as of 1 Jan 2025: Thanks!

Yes that is what it seems like at the moment, especially for all the phases until cruise. Its possible the AI Pilot is taking over on final approach as well, but that is quite odd as I see the AP disconnect automatically. I haven't had such issues when I have tried. Also thanks for making the post on MS forums as well for their teams. I see you also mentioned the issue on this forum bug report, may I suggest adding the above videos there as well? https://forums.flightsimulator.com/t/ai-pilot-engages-in-cursor-mode-and-messes-up-flight/671715 As for the avionics freeze, can you please also make a video for that? Also please try to delete your StreamedPackages folder to see if you still have the issue after? Instructions here for console: https://flightsimulator.zendesk.com/hc/en-us/articles/17268168854044-Loading-issues Well, their teams have been away for the holidays, so expect some delay in response. I'd imagine most would be back in office starting next week. Thanks!

This is a new release, which offers all those things mentioned on the dedicated FS2024 version (v1.0.0 FS2024). What I meant was that in terms of the changelog, the "fixed" items are the same, i.e. the below bugs mentioned as fixed on v1.0.1 FS2020 are fixed on launch of v1.0.0 FS2024 as well. Thanks!

Thanks I've shared with the team, but unfortunately we weren't able to reproduce the visual artifacting on our end. Can you please add an additional video of what you're seeing on 2024? Thanks!

Hi, @LucaMost English only please on the forums. It's a known issue we are tracking that looks to be on the MS/Asobo side. There is a thread here on the MS forums that you should post to for maximum visibility on this topic. For clarity, nothing has changed build-wise between pre and post patch with our aircraft so we're looking deeper into why folks are seeing this from time to time. For PC users, the community suggested workaround to this issue is switching Texture Resolution to "High" for now. Thanks!