Anyone using the TM Airbus sidestick/quadrant managed to get their controls properly calibrated/set up yet ? Worked in MSFS 2020, but it's beyond ****** here.
Yea you can use increase simulation speed and get max payout but you risk killing yourself, like seriously risk it lol.
Any of them ... can't get throttle to work. Configures it as a button rather than a full axis. Basically gives me 0-100% throttle between the first 2 detents.Yes, I have. What aircraft are you calibrating controls for?
Ran out of fuel after only 30nm ? Should have just taken a glider insteadI've managed to grind myself up 300k now.
I did a mission, fortunately not a freelancer one, it gave me that old de havillan plane, was about a 30nm trip no problems, got about 1nm from the runway and still needed to turn and the ****** ran out of fuel!
Needless to say it wasn't pretty, I didnt want to risk gliding it too far, so made the turn, in hind sight too early and came flying over the run way. oh well, not my plane.
There's a control binding to add fuel if necessary.
Any of them ... can't get throttle to work. Configures it as a button rather than a full axis. Basically gives me 0-100% throttle between the first 2 detents.
Also, landing gear / parking brake switches ... how do you get it to recognise on/off states ? I can do this via 3rd party software but not in MSFS itself.
edit. Managed to get the throttle working for light aircraft by switching off "virtual buttons" in control panel then binding throttle 1 & 2 to "throttle 1 axis" and "throttle 2 axis" respectively. This prevents them from being seen as "buttons". Still haven't worked out how to get switches to act as toggles rather than buttons though eg. parking brakes, engines, landing gear.
The fear it was trying to kill me in a aircraft I have to pay for was real! Massive brown trouser moment as releasing AP put my too high trim straight to 100%, spin the trim wheel slightly and it went to -100% while I was in a nose down stall. Managed to recover it but a bit of working out, I think the bug may be related to VS not being 0 when engaging AP.