richboy2307

Your planned SimBrief flightplan may be imported directly into the MCDU via the ACARS page. This flightplan can also be loaded onto the Aircraft EFB to view the Operational Flight Plan (OFP) and other relevant information. Please follow below steps for setting up and using this feature. Setting Up SimBrief Import The import features only work after you have entered your (5) Simbrief Pilot ID (numbers only) on the Aircraft EFB Settings app. Your Pilot ID is found on the 'Account Settings' page on Simbrief website. You can also switch (6) Weight Units between Metric (KG) and Imperial (LBS) units here to match your planned flight. Importing into EFB Navigate to the "My Flight" app on the Aircraft EFB home page. Here you can select the "IMPORT FROM SIMBRIEF" button on the bottom right to retrieve your flightplan. After the flightplan is imported, you can click the "VIEW FLIGHTPLAN" button to preview your text OFP. Importing into MCDU Press the (1) MENU button to access the MCDU Main menu page. From here press the (2) R1 LSK "ACARS" button to access the ACARS page. Then press the (3) L1 LSK "REQUEST SIMBRIEF" button to begin the import. You will be returned to the INIT A page and shown the (4) Scratchpad message "AOC RTE UPLINK" upon successful import. Importing Simbrief Fuel & Payload Lastly, you may update your Fuel & Payload as planned via Simbrief on the Aircraft EFB using the guide below:

Hi, That would depend on where did you buy the T-33 from? - If it was from the iniBuilds store, you would have to download iniManager already to install it in the first place. The inimanager is available for download here. Once you are logged in to the same account used for purchase, head to "My Products" section, then select T-33 from the list. If there are any updates available, you will be prompted with a yellow 'Update' button on the page along side the sim for which it is available. - If you bought it elsewhere (Simmarket/Marketplace), then the updates will be handled via those respectively. Thanks!

Hi @CptFerox @Argonox Most users have made changes to the controller profiles, having unbound unnecessary controls from keyboard/mouse and other connected devices so we recommend the same. As a last resort, you may also try a sim re-install, especially if the initial sim install was within first few weeks when server issues were prevalent as it is possible some core files were improperly installed. Currently we do not have any other suggestions other than those above at this time. As also mentioned on the previous post, currently we have not seen any issues aircraft-code wise that would cause AP disconnection issues, nor have we been able to reproduce this on our end (having done multiple "AFK" flights, longer than 6h as well). Thanks!

Hi @Jeff Green We have to wait for a fix from MS/Asobo side as last sim update has affected reflections across the board. Thanks!

Hi @Jorrallcorrall We're not able to reproduce such issues (flight control or engines cut off) on long or short segments across the A330 fleet (or other default airbus aircraft) internally or through any of our testers. So the issue is likely client side, please take a look at the suggestions below to see if you can find the cause: Sorry you're experiencing this, please also take screenshots of when this happens (A screenshot that shows PFD/ND/FCU in clear view + a screenshot of your pedestal (MCDU till rudder trim) + a screenshot of your overhead panel), so we can see if there are any clues as to why this may be happening. The AP/AT disconnection is usually caused by control inputs, which could be caused by conflicting keybinds from any of your connected devices. These can include primary flight controls (axis/buttons for Aileron/Elevator/Rudder) and trim for those controls. For the throttles these keybinds could also be nudging the them out of the relevant detents, and thereby leading to AT disconnection. The banking left is indicative of inputs on aileron or rudder (or their respective trim). Alot of these are assigned to common keys (e.g. Enter for RUDDER YAW RIGHT) on the default profiles for keyboard. So it is possible these are being inadvertently registered by the sim as you're using your keyboard outside of flight sim as well. TOGA LK will usually engage when aircraft has entered a low speed regime to prevent stall (ALPHA FLOOR PROTECTION), so that is just the result of an AT/AP disconnect situation leading to a degradation of your speed. This also seems a keybind issue related to MIXTURE (axis or set rich/lean) or CONDITION. Alot of users who have reported such issues have resolved after ensuring any bindings related to these are unassigned from all connected devices, except for the switches/axis where you want it to be assigned. You should also be wary of the control profiles, as these can be assigned individually per aircraft now so you want to ensure the correct ones are assigned and active. Some users have also reported that even though a profile was showing active on UI, it wasn't the case until the changed to default profile, and then back to their custom profile and hit save after. The last thing (particularly PC related) is that if your PC has power saving enabled on USB ports. It is possible that after a few hours of non-usage, it enters a power-saving state, which causes device to reconnect. MSFS2024 loads the "default" controller profile initially when a device is connected, before reverting to custom profiles if the device is recognized again. So its possible that is what is happening in these instances. So spend some time looking into these to see if you can resolve the issues. Thanks!

The Behaviours menu is a bit different in terms of layout in FS2024, with alot more options but it generally works in the same way. Enable Developer Mode in settings and then open the behaviours menu from the [DEVMODE] toolbar. Highlight the interaction you want to inspect by hovering your mouse over it and then press 'L Ctrl' +'G' on your keyboard. On the [INSPECTOR] Tab, you can usually fin the affected variables under Animations or Mouserect dropdowns. Then go to [VARIABLES] Tab, type in the name of LVAR and use your mouse to conduct the interaction to monitor the changes in values. Note: The sim does not allow all LVARs to be defined by the user, but this way you can find the affected LVARs for each interaction to see the ones you can manipulate. 2025-01-07 14-50-23.mp4 Thanks!

Hi @einherz Just to confirm you're talking about the turn & slip indicator, correct? From what I can see, it does move around a little bit whilst taxiing, but generally remaining centered in place. I believe this is a feature of the new CFD of FS2024 where it is perhaps more sensitive to slight changes of g-forces and that is what you're seeing? 2025-01-07 00-54-06.mp4 Thanks!

Hi @Alan Fernandes We are unable to provide any ETA as the process is not entirely in our hands. However, we hope the update (v1.1.4) is pushed via marketplace soon. Thanks!

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!