Input settings, controls.ini file code list and descriptions & vJoy binding hints

[melodrama]

Hello, I'm using the programs Joystick Gremlin and vJoy to bind my controls. (I can bind one or more buttons as mode selector with Joystick Gremlin that is not possible with Condor's own binding system)

Binding itself was/is quite tricky because system identifies and bind the actual control instead of vJoy.

I ended up bind most of the axis and buttons manually and make the required modifications into controls.ini file directly. controls.ini file is quite cryptic, it contains weird-looking control device id codes (keyboard and control id's are between braces) and list of number-type codes how Condor input commands are linked to input control devices, codes on the left are Condor side codes and right ones are the connected control device codes for axis, hats and buttons.

I made lot's of testings and I found what these left side codes means. List is here:
controls.ini code : Description
0 : Bank axis
1 : Pitch axis
2 : Rudder axis
3 : Air brake axis
4 : Trimmer axis
5 : Flaps axis
6 : Throttle axis
2005 : View POV
???? : Bank Mouse
???? : Pitch Mouse
3008 : Bank Left
3009 : Bank right
3010 : Pitch up
3011 : Pitch down
3012 : Rudder left
3013 : Rudder right
3014 : Rudder centre
3015 : Trim up
3016 : Trim down
3017 : Trim centre
3018 : Airbrakes in
3019 : Airbrakes out
3020 : Flaps up
3021 : Flaps down
3022 : Gear
3023 : Wheel brake
3024 : Release
3025 : Water
3026 : Smoke
3027 : View pan left
3028 : View pan right
3029 : View pan up
3030 : View pan down
3031 : View reset
3032 : View snap left
3033 : View snap right
3034 : Zoom in
3035 : Zoom out
3036 : Panel zoom
3037 : Game menu
3038 : Pause/Autopilot
3039 : Miracle
3040 : Send message
3041 : Show classification
3042 : Show icons
3043 : HUD toggle
3044 : Extend chat log
3045 : Screenshot
3046 : Cockpit view
3047 : External view
3048 : Chase view
3049 : Tower view
3050 : Towplane view
3051 : Fly-by view
3052 : Padlock view
3053 : Net player view
3054 : Replay Camera
3055 : PDA screen 1
3056 : PDA screen 2
3057 : PDA screen 3
3058 : PDA screen 4
3059 : PDA next
3060 : PDA zoom in
3061 : PDA Zoom out
3062 : Climb/Cruise toggle
3063 : MC increase
3064 : MC decrease
3065 : Vario volume increase
3066 : Vario volume decrease
3067 : Altimeter up
3068 : Altimeter down
3069 : Radio frequency up
3070 : Radio frequency down
3071 : G meter reset
3072 : Lift helpers
3073 : Task helpers
3074 : Check time
3075 : Extract/Retract motor
3076 : Start motor
3077 : Throttle up
3078 : Throttle down
3079 : Start flight
3080 : Toggle auto rudder

Most of these Condor side codes are bind into keyboard as default and they are listed under keyboard device id code. List above is useful when binding controls manually. You can bind vJoy device via Condor Assign window also if you find a way how to send vJoy axis-, HAT- or specific button activation information without pressing the actual control button at the same time. Some of the vJoy axis can be found when the actual controls are not connected to PC, but not all. Then I founded that I can use Joystick Gremlin macro feature; I can add 2-3 second delay before actual vJoy command (button Press and Release commands, for example) => I can activate the control bind command outside the Condor assign window and then activate the actual assign cell/field before vJoy sends the command. This works well with the button assign, I didn't find proper way (yet) how this could work with axis (I found the missing axis just by trying different code alternatives)..

controls.ini is located under *\Documents\Condor\Pilots\* (*=your own computer and Condor installation specific folder names)

[Kandiru]

Fascinating, Joy2Key works for me.

[Bre901]

I ended up bind most of the axis and buttons manually and make the required modifications into controls.ini file directly. controls.ini file is quite cryptic, it contains weird-looking control device id codes (keyboard and control id's are between braces) and list of number-type codes how Condor input commands are linked to input control devices, codes on the left are Condor side codes and right ones are the connected control device codes for axis, hats and buttons.

I made lot's of testings and I found what these left side codes means. List is here:

Nice job
However you might have saved yourself all that testing time if you had searched the forum
viewtopic.php?f=29&t=19771

[melodrama]

Yep, I saw that => most of the codes were available from Condor side but not all (codes 1-6, and 2005 and newest adding 3080 were missing from CMD.txt file)..