Keyboard/Joystick Default Input Fix / Proposition

[sedenion]

Since one of my major chagrin (with the Padlock View) is the default input configuration, I made one myself.

 

I know that the current key command are not fixed and still WIP, i propose here a rework/relook of the current default input files to maybe inspire Zeus, if he and community judge this relook is a good work. If not, then, I will just cry all the night and buy a red wine bottle.

 

To prevent some catastrophic consequence of changing habits i followed some rules:

- Section's names and command distribution in sections are the same

- Majority of key combo binding remain the same (but there is few tactical changes)

 

What I have done :

 

 

1) Commands renaming

 

I renamed ALL commands (yes, am creasy) according some "intuitive" AND "rational" rules:

- Keeping the consistency with actual DCS naming rules (Captials, On/off) when it's pertinent (the default DCS naming rules is more about feeling than consistency, but... )

- Renamed common commands to exactly fit with the already existing DCS commands (allow automatic i18n for some commands... maybe a bad idea, don't know, you will tell me)

- Renamed commands to allow alphabetical rules to keep some commands together in the command view in DCS, this, to have a better readability and consistency in command display.

- Renamed commands to be both explicit, readable and not too long

 

2) Added commands

 

Some command were added:

- All INS buttons and Selector (that is not so vital, but adds consistency)

- “Master Arm To On” and “Master Arm To Off”, yes ! I found how to do ! Am proud. (see clickabledata.lua, almost super-simple).

EDIT: Damn, i just discovered that, that actualy set the switch Up or Down, but that does not switch the Master Aram Mode... So, i ADD to missing commands

 

- “Gun Arm To Safe” and “Gun Arm To Armed” (that is not so vital, but can be useful)

 

3) Some key combo changed

 

I changed some default key combos binding for “tactical” and consistency purposes:

- All “Autopilot” related key combos now use the “FC3” key binding standard: LAlt+1, LAlt+2, etc. for two reasons: First: This remain OK with the DCS/FC3 standard, and Second: This allow to use previous key combos for other things !

- All “Trim” related key combos, because: First: The current default ones are obviously not standard at all with DCS, so I turned trim key combos to DCS standard. And Second: This allow to use previous key combos for other things !

 

4) Default key combo added

 

I added some default key combos. However, since the current command list still WIP, I added combos ONLY for commands that seem to be definitives ones. I also leaved some key combos “free” for futur commands that does not currently exist, typicaly : “RWR On/Off/Auto Toggle” or “VTB Screen Power On/Off” for example.

The added key combos were chosen according some simple rules:

- Consistency with already existing combo in others modules (at least, those I have)

- Some logical consistency where possible according : On = Rshift, Off = Ralt, Auto/Test = Rctrl.

- The “Alone” key without “Rshift”, “Ralt” or “Rctrl” leaved free for futur “Toggle” command.

 

5) What is missing ?

 

Is missing some short-cut commands, that I can't create since they must be “hard coded” as internal commands. I already mentioned those missing commands, I juste leave here the new list ( this is not an exhaustive list, since am not really familiar with all the Engine, Hydraulic and Electrical parts... So maybe someone else can complete this list):

 

In Weapons Management:

- Master Arm To On

- Master Arm To Off

 

In Weapons Preparation:

- Missile Selector Left/Right/Auto Cycle

- Bomb Fuze Disarm/Delay/Instant Cycle

 

In Countermeasures

- CM Box On/Auto/Off Cycle (“CM Box” renamed “Countermeasures Mode” in my default.lua. Ok don't cry, I f*** don't know how to name this thing)

 

In Flight Control:

- Slats ForceUp/ForceDn/Auto Cycle (not vital, but consistency)

- FBW Gain Normal/Emergency Toggle (not vital, but consistency)

 

In Sensors:

- Radar Azimuth Angle Increase

- Radar Azimuth Angle Decrease

- Radar Scan Lines Increase

- Radar Scan Lines Decrease

- Radar Power Off to Emit (Kind of Inc)

- Radar Power Emit to Off (Kind of Dec)

- Radar B-Scope/PPI Mode Toggle

- IFF Power Sect/Cont/Off Cycle (or maybe just IFF Power Cont/Off)

- RWR On/Off Toggle

- Radar Altimeter On/Off Toggle

 

In Cockpit Display

- VTB Screen Power On/Off Toggle

 

You will find my custom default input fix files, in JSGME compatible here: http://forums.eagle.ru/attachment.php?attachmentid=143606&stc=1&d=1467796691 or in joint piece.

 

 

 

Please comment ! “Haa That is soo baad!” or “What you doing is just sooo useless, go die man !” or “Ho that piece of crap !”, “What this poor FC3 noob player !”, “I think pink is a better color than On/Off”... am now psychologically prepared to ear ANYTHING.

Beta M-2000C - Input Fix.zip

Edited July 6, 2016 by sedenion

[Gliptal]

I actually though of doing something similar myself the other day, but gave up due to the lack of time. Excellent work, I also feel the keybinding menu (in general, not just for the M-2000C) needs an overhaul and new consistency rules.

[3rd Wing - Raiden]

Hi Sedenion,

 

Impressive work here! Would you be kind enough to quickly explain what is the Padlock view?

 

Thanks,

[Gliptal]

Hi Sedenion,

 

Impressive work here! Would you be kind enough to quickly explain what is the Padlock view?

 

Thanks,

Padlock view keeps the camera centered on a given object.

[3rd Wing - Raiden]

Like you lock the target on and the camera view automatically slew to keep the target centered in the frame?

[sedenion]

Like you lock the target on and the camera view automatically slew to keep the target centered in the frame?

 

That's it... (the feature already exists for all DCS modules, don't know why this does'nt work in M2K module)

Edited July 6, 2016 by sedenion

[myHelljumper]

Blue is a better color than "master arm to on" :noexpression: