Custom Autopilot / Fly-By-Wire

If this is the case, your throttle is not calibrated properly. The values of the throttle axis range from -1.0 to 1.0 independently if you're using reverse on axis or not. When the current throttle position is larger or equal than the start position and smaller or equal than the end position of a detent, the throttles are considered to be in that detent.

Ensure that:

• detents are large enough defined, so hardware inaccuracy is taken into account (i.e., detents on the Thrustmaster TCA are not that hard and values can quite differ even if one thinks it's in the detent)
• there is enough range between the detents (meaning the end position of a detent and start position of the next detent are at least as wide as the detents)

Important: if you have issues, don't look at the animation part to check if it's in the detent. Check the values in the EFB, those are relevant and not the animation.

Important rule is to always monitor the FMA. If you're in manual flight, and you're in CLB, OP CLB, DES or OP DES the Autothrust applies either THR CLB (limited by the throttle levers) or THR IDLE. The speed needs to be controlled by pitch and in manual flight the pilot is responsible to do so by following the flight director orders.

If this is not your desired mode, you can do two things:

• engage another vertical mode (i.e., V/S or FPA)
• disengage both flight directors, this will force the Autothrust into SPEED mode

Reminder: Speed is only controlled properly using thrust when Autothrust is engaged and active, thrust levers are in detent CLB, active FMA mode is SPEED or MACH.

SRS mode needs at least a V2 entered on TO PERF page. Additionally, it does only engage when the detents are set properly. If no FLX temperature is set, this needs to be TOGA. If a FLX temperature is set, it's FLX/MCT or TOGA.

Other conditions:

• plane needs to be at least 30 s on ground
• Flaps extended at least in position 1+F

There is currently no auto-tune available for the LOC on take-off. You need to enter the right frequency manually. Besides that, RWY mode only engages with the following conditions:

• LOC signal valid
• LOC deviation smaller than 1/2 dot
• Deviation between plane heading and LOC bearing is < 20°
• Plane needs to be at least 30 s on ground
• Flaps extended at least in position 1+F

Ensure that both thrust reduction and acceleration altitude on TO PERF page are properly set up.

Before reaching 400 ft radio altitude, the FMA needs to show LOC and G/S. If one of them is still in capture mode (LOC* or G/S*) you need to perform a go around maneuver or land manually, LAND will not engage that way.

The Autoland system is quite complex and is dependent on multiple environmental conditions to work properly, such as:

• LOC accuracy in terms of
• alignment of heading to the runway heading
• alignment on the runway centerline
• availability down to 0 ft and also during roll-out
• G/S accuracy in terms of
• alignment to the correct height (50 ft over runway threshold)
• availability down to 50 ft
• ground in front of the runway threshold needs to be more or less stable (no fast raising terrain) beginning 200 ft radio altitude

Reminder: If the autoland warning light goes on, it's IRL procedure to go around!

Unfortunately, many runways (either using Navigraph or not) have issues for LOC and/or G/S, either in terms of alignment or availability. On many runways, you lose the LOC during ROLL OUT. In that case, the rollout has to be performed manually by disengaging the AP.

Ensure that no SimConnect.cfg is in the Documents folder of your user profile. An older version of Kinetic Assistant installed that file, and it's causing issues with SimConnect connection between our custom systems and the sim.

Ensure that you get enough frames per second (see on top).

Ensure that you don't have any mods or add-ons installed that have influence on the flight model or other physics.

In most cases, a time compression up to 4x is safe to use. Nevertheless, depending on environmental conditions and the performance of your computer, oscillations can still occur.

The reason it can work for some and not for others is how time compression works. For example, when using time compression of 2x for the custom systems it's like having 1/2 of your displayed fps, when you're using 4x it's like 1/4 of it. So considering the 17 fps requirement, it means you need ~ 30 fps and ~ 45 fps for 4x to work somehow, at least for smooth cruise.

When you encounter heavy turbulence, it might be needed that time compression is reduced.

In MSFS, there is a special binding for rudder available for use with Xbox-Controllers (it's bound by default). This binding is Rudder Axis Plus and Rudder Axis Minus. In the case of an Xbox-Controller, the rudder in centered when both axes (Plus and Minus) are in the middle of the range. When using a "normal" axis with those two bindings, this can cause issues because usual axes use the full range.

To enable the use with normal axes, the following needs to be done.

Put a file named ModelConfiguration.ini into the work folder (see "Work folder location" on this page) that has the following option set to true:

[flight_controls]
disable_xbox_compatibility_rudder_axis_plus_minus = true