iniBuilds

Please may you contact direct support? https://www.inibuilds.com/contact

No worries! As this has been resolved, will lock 🙂

No worries: Main things to look for if CTD with FMS FROM /TO: - Navigraph updated / removed - Custom airports with a custom ILS may cause CTD

Thanks for translating ❤️

We do have some elements of it, but will add more.

We recorded the plane IRL - it is indeed very loud in the cockpit. We have recorded a lot of feedback, and team will work on this now. Will ensure these feedback points are addressed and in the next version.

Will pass this to the community team and see if someone has made one.

Thanks for the report, we will try and look into it.

Some people have cycled YES/NO and back to intended setting and it has worked

Have you followed the FAQ instructions?

There is no TERR radar. Kind Regards

There are main areas to look at if crashing: - Make sure Navigraph Navdata fully updated - If you dont use it, remove it - Clean Community - a custom ILS in a scenery will cause you to CTD when doing FROM/TO. Many thanks.

Or alternatively you can delete it!

11/11/2022 - 2100z So to all having throttle calibration issues / if you know others who have it please let them know. We have made a fix code side but as a temporary workaround on TCA units: Paths: MS Store version: C:\Users\yournamehere\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\microsoft-aircraft-a310-300\work Steam: C:\Users\yournamehere\AppData\Roaming\Microsoft Flight Simulator\Packages\microsoft-aircraft-a310-300\work Steps Locate your ThrottleConfiguration.ini file, open it and set both reverse_idle entries to a value that is 0.05 less than your idle value. Example: [throttle_common] reverse_on_axis = true [throttle_axis_1] reverse_full = -1.000000 reverse_idle = -0.200000 -> Change to -0.45 because (idle is -0.39 - 0.05 = -0.45) idle = -0.396667 toga = 1.000000 [throttle_axis_2] reverse_full = -1.000000 reverse_idle = -0.200000 -> Change to -0.45 because (idle is -0.39 - 0.05 = -0.45) idle = -0.395569 toga = 1.000000

So to all having throttle calibration issues / if you know others who have it please let them know. We have made a fix code side but as a temporary workaround on TCA units: Paths: MS Store version: C:\Users\yournamehere\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\microsoft-aircraft-a310-300\work Steam: C:\Users\yournamehere\AppData\Roaming\Microsoft Flight Simulator\Packages\microsoft-aircraft-a310-300\work Steps Locate your ThrottleConfiguration.ini file, open it and set both reverse_idle entries to a value that is 0.05 less than your idle value. Example: [throttle_common] reverse_on_axis = true [throttle_axis_1] reverse_full = -1.000000 reverse_idle = -0.200000 -> Change to -0.45 because (idle is -0.39 - 0.05 = -0.45) idle = -0.396667 toga = 1.000000 [throttle_axis_2] reverse_full = -1.000000 reverse_idle = -0.200000 -> Change to -0.45 because (idle is -0.39 - 0.05 = -0.45) idle = -0.395569 toga = 1.000000

Thanks for your feedback, will be noted..

Yes, you must go to latest. You will then see no crash 🙂

Airspeed down: AP_SPD_VAR_DEC (default MSFS command) Airspeed Up: AP_SPD_VAR_INC (default MSFS command) Altitude down: AP_ALT_VAR_DEC (default MSFS command) Altitude Up: AP_ALT_VAR_INC (default MSFS command) VS down: AP_VS_VAR_DEC (default MSFS command) VS Up: AP_VS_VAR_INC (default MSFS command) Heading down: HEADING_BUG_DEC (default MSFS command) Heading Up: HEADING_BUG_INC (default MSFS command) AP1: A310_AP1_BUTTON (Lvar) AP2: A310_AP2_BUTTON (Lvar) TOGA: A310_takeoff_toggle (Lvar) Airspeed knob push: A310_FCU_SELECTED_SPEED_BUTTON (Lvar) Airspeed knob pull: A310_FCU_MANAGED_SPEED_BUTTON (Lvar) Heading Pull: A310_FCU_SELECTED_HEADING_BUTTON (Lvar) Heading Push: A310_FCU_SYNC_HEADING_BUTTON (Lvar) VS Pull: AP9_BUTTON (Lvar) Altitude Knob Pull: A310_FCU_ALTITUDE_PULL_COMMAND (Lvar) Altitude Knob Push: A310_FCU_ALTITUDE_PUSH_COMMAND (Lvar) (edited)

There is no paintkit at this time

Firstly you must establish if you use reverse thrust on an axis or not. If no, ensure this is set to NO on the EFB and calibrate as per the instructions on the calibration menu. Reload the plane to ensure this change is made properly, and you will be able to bind reverse thrust to a button / input on your hardware. If yes, and you do intend on using reverse thrust on an axis, ensure you set this to YES, and calibrate as per the instructions on the calibration menu. Reload the plane to ensure this change is made properly, and you will be able to use your reverse on an axis with your hardware.

https://www.simbrief.com/system/dispatch.php?sharefleet=347385_1664536765275

We have a comprehensive, in-sim checklist which will take you from cold & dark, to post-flight on the blocks. We also have an in-depth manual available alongside tutorial videos available on YouTube. https://inib.uk/Discover-The-A310-Playlist

Please use the Weight and Balance tab in our EFB. Please do not use the Microsoft Flight Simulator weight and balance menu – this will have no impact, and may cause issues with your flight.

Update - 15/11/2022: 12:30z For the time being, if you're experiencing crashes while entering the FROM/TO pair, please remove the "navigraph-navdata" and "navigraph-navdata-base" folders, as well as any custom airports that cause a crash in the citypair input. --------------------- If you’re using Navigraph navdata, please ensure it is up to date. If you’re not using Navigraph, please post in more details over on the right support section.

The nav select three-way switch must be set to VOR to enable manual VOR navigation.