February 13, 20233 yr The only things I have set in MSFS controls, is menus, pause, views, etc. Everying else (axes, AP controls, flaps, gear, trim, etc, etc) is configured by individual plane, in AAO. AAO auto-launches with MSFS and auto-selects the right profile for the chosen plane in MSFS - so it's exactly what I was used to in XP11. Edited February 13, 20233 yr by JYW Bill 😎 FS2024 • PMDG 738, 777F & 777-200LR • Fenix A319, A320, A321 • TFDi MD-11 • AS/ToLiss A346 • iFly 737 MAX8 • Ini A340 • AS CRJ v2 • Ini A300 Premium • FSS 727F • FFX HJET, Visionjet and P180 2024 • A2A Comanche 2024 & Aerostar • All BLACKSQUARE aircraft • COWS DA40 & DA42 • FSW C24R Sierra & C414 TrackIR • BeyondATC • PMS GTN Payware • RealTurb • Axis & Ohs • FS Realistic Pro 9800X3D • RTX 3080 • 64GB DDR5-6000 NPPL licence holder in the UK
February 13, 20233 yr Spad.Next for me I switched after getting tired of switching profiles based on aircraft. Also I have the ability to map controls to various switches in payware aircraft based on conditions which is not available with the in sim controller mapping. For example I can assign multiple controls to a button that will be executed in sequence such as turning taxi lights off when landing lights are turned on. You can make this work the same using the in sim controller mappings for lights but not for all such as APU or other things. Auto switching profiles per aircraft is big reason for me. In sim mapping is not ideal when you have 30+ profiles for each aircraft. Makes it very inconvenient.
Archived
This topic is now archived and is closed to further replies.