Without key mapping commands, its very tricky for me just after takeoff, with right hand on joystick and in need of another right hand to use mouse for enabling auto pilot lnav vnav.

keymapping is an issue , a major issue for CS planes,

its best to either provide your own kepmapping like another company and another company do, or much better still comply with the standard fs keymapping , so we can use what we already got setup via fs and fsuipc.


I think the only way to find what keys are assigned to what actions in CS planes is to complete the job of ther cs developers by getting registered version of fsuipc.

Turn on fsuipc logging console window

as you push buttons / interact  with a/c in fs  , you can see the fs command those interactions are mapped to.

Assign those commands identified via fsuipc log output to your joystick/keyboard/controller etc.


This might not be an easy solution though, if CS has not yet fixed that very old bug with 757/767 where CS planes are sending 1 million unused messages to fsx per second. Cause with this bug fsuipc log window will be scrolling up with useless messages at the speed of light. So very hard to make out message related to a button you just pushed in the plane.

To be fair to CS the statment that cs planes use standard fs keyboard commands is partially true, but things like lnav, vnav, and other autopliot commands , i  dont know how to map, without having to use fsuipc log to identify.