richboy2307

Hi, sorry I was unable to reproduce the issue on latest version (1.1.4) from iniManager. It seems to be working fine for me, per video below. 2025-01-06 23-48-20.mp4 Can you please try to clear your A300 WASM folder to see if that resolves the issue? If not, try running with an empty community folder (only inibuilds a300 inside) to rule out any conflicts due to other addons. Thanks!

@einherz Thanks for sharing the video. I see the issue at the timestamp and added to your initial report for the team. 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, Apologies for delayed response and thanks for your report. Was your physical throttle axis already on IDLE at the time you disconnected the throttles? I just tested, the moment you disconnect the autothrottles, the A310 starts to read the position of your physical throttle axis and as such makes adjustment accordingly. In my test I had my physical throttles axis at ~50%, whereas aircraft was descending essentially on IDLE with AT. As soon as I disconnected AT, the throttles were now at 50%. In real life, this would not be an issue as when you disconnect AT, your physical throttles will be wherever AT had it last. However in sim, this is a limitation as most users do not have a physical throttle axis that is controlled by servos to match the state of AT. So you just need to be mindful of the position of your axis at the time you're about to disconnect AT. Thanks!

Hi @sidneyschwartz Apologies for late resopnse, but I hope you found your answer already. If not, the value goes on the INIT B page, as seen on the video here (30:42): Thanks!

Hi @WallyWalt Apologies for delayed response and thanks for your report. No there is no failure or service based maintenance system implemented on the A310. Have you had this issue on subsequent flights or was it just that once? Thanks!

Hi @neagabi Apologies for delayed response and thanks for you report. That is very odd, can you please share the OFP for your flight? This should be available as a PDF from simbrief. Also have you had this issue again ever since? Thanks!

Hi @HawkEyeGuy7659 Firstly, a Happy New Year to you too! 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 @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!

Yes that is an option, as long as both purchases are made via the same via the same account on inibuilds store (website or iniManager) or Simmarket respectively. For Marketplace customers (PC), as the FS 2024 Marketplace is not yet available, this is currently not possible unless you request a permanent order transfer of your purchase to the iniBuilds Store: https://inib.uk/order-transfer As for Marketplace purchases/upgrades to FS2024 for Compatible/Enhanced/Premium editions of products in general, please see quote from below linked post: Yes expect some delay due to the holidays. I've replied to your forum post here as well with additional info: 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!