Click a function, then move only the axis you want for it. The trainer picks the axis that moved most. Saved in this browser.
Anything you would rather fly from the keyboard or mouse, pick it here and its stick axis is ignored. Collective on the keys is the usual case for a stick with no throttle.
Pick what drives each axis. The two mouse axes can each fly one thing, anything else goes on the keys. On Windows, turn Sticky Keys off first (Settings, Accessibility, Keyboard), or repeated key presses can pop up a Windows dialog mid-flight. Click the view to capture the pointer, Esc hands it back. The cyclic stays where you put it, like the real thing, so bring it back yourself or right-click to snap it to neutral.
Self-centring off means the cyclic holds its deflection, which is what a mouse does best. Turn it up if you would rather it sprang back like a stick, and keep it off once you can fly without it.
The collective spring applies when the collective is on the keys. It puts the lever back to the hover setting, the centre mark on the bar, as soon as you let the key go: hold a key to climb or sink, release to sit. A real collective and a HOTAS throttle both hold where you leave them, so this is off on stick and HOTAS and only ever applies here. It also stops the mouse wheel holding a setting, so turn it off if you fly the collective on the wheel.
Curve 1.0 is linear, the same as in-game with no device-software curve. Higher values flatten the centre. Once you find a value that feels right here, reproduce it in the T.Flight's Windows profile or accept linear in the game.
Curve 1.0 is linear. Higher values soften the first part of the travel, so small mouse movements do less and a hover is easier to hold. Match whatever sensitivity curve the game gives you.