Keyboard Mapping Sugestion

[sedenion]

I created this keyboard mapping according current DCS standards, based on F-15 C and Su-25T keyboard mapping, transpose in philosophy to the M2000... The mapping is an attempt to be both convenient and fidel to M2000 operation, without conflicts. I made some comments to explain the command behaviour when its needed.

 

It is obviously incomplete, and subjected to debate

 

Category Key Command Comment

Weapons "D" PCA Stores Select Cycle (Weapon Select) Cycle through PCA stores buttons select

Weapons "C" HOTAS PCA Override A-A Guns

Weapons "LAlt – C" HOTAS PCA Override MAGIC Maybe "LAlt - D" ?

Weapons "LShift – C" Guns RAP / LEN Mode Select Select RAP / LEN in PCA

Weapons "LAlt – W" Launch Permission Override (?)

Weapons "LCtrl - V" Missil Pylon Selector Left / Right / Auto

Weapons "Space" Fire (guns)

Weapons "RAlt - Space" Fire weapon (BRM)

Autopilot "LAlt - 9" Autopilot – Disengage

Autopilot "H"; "LAlt - 2" Autopilot – Altitude hold

Autopilot "A"; "LAlt - 1" Autopilot – Attitude hold

Autopilot

Countermeasure "E" Jammer Cycle T/ M/A

Countermeasure "LAlt – E" Jammer Modes Cycle

Modes "0" Master Arm Switch On/Off Master Arm On / Off

Modes "Ralt – 0" Master Arm Switch Off If enabled disable Master Arm

Modes "1" Navigation Modes Cycle Master Arm Off: Cycle through PCA modes buttons except POL / Master Arm On : Do Nothing

Modes "2" Special Modes Deselect (Normal/BVR Mode)

 

Modes "3" CAC Mode – Vertical Scan

Modes "4" CAC Mode – Bore

Modes "5" CAC Mode – Horizontal Scan

OR:

Modes "3" CAC Modes Cycle Cycle through Vscan / Hscan / Bore

 

Modes "6" Ground Avoidance Mode

Modes "7" Police Mode On/Off Select / Deselect the POL mode in PCA

Modes "Ralt – 7" Police Mode Off If selected deselect the POL mode in PCA

Modes "LShift – 1" PCA Button 1

Modes "LShift – 2" PCA Button 2

Modes "LShift – 3" PCA Button 3

Modes "LShift – 4" PCA Button 4

Modes "LShift – 5" PCA Button 5

Modes "LCtrl – 1" PCA Gun Mode Select

Modes "LCtrl – 2" PCA Stores 1 Select

Modes "LCtrl – 3" PCA Stores 2 Select

Modes "LCtrl – 4" PCA Stores 3 Select

Modes "LCtrl – 5" PCA Stores 4 Select

Modes "LCtrl - `" Next Waypoint

Modes "LShift - `" Previous Waypoint

Sensors "RCtrl - I" TDC Center

Sensors "/" TDC Right

Sensors "," TDC Left

Sensors "." TDC Down

Sensors ";" TDC Up

Sensors "Enter" Lock Target

Sensors "RShift - R" RWR On/Off

Sensors "Rshift - =" Radar – Increase Scan Bars

Sensors "Rshift - -" Radar – Decrease Scan Bars

Sensors "RAlt - =" Radar – Increase Azimuth Angle

Sensors "RAlt - -" Radar – Decrease Azimuth Angle

Sensors "RCtrl - =" Radar – Increase Range

Sensors "RCtrl - -" Radar – Decrease Range

Sensors "I" Radar – Power Modes Switch

Sensors "Back" Radar – Unlock / Back to Search

Sensors "RShift - I" Radar – PRF Select

Sensors "RAlt - I" Radar – PPI / B Mode Select

Systems "S" NWS On/Off

Systems "L" Cockpit Light Disable or Enable all cockpit lights at medium/convenient intensity <--- Bad idea

Systems "RAlt - RCtrl - L" Anti-collision light

Systems "RAlt – Rshift - L" Formation light

Systems "RCtrl - L" Navigation light

 

( Edit add: )

 

Systems "O" VTB On / Off

Edited December 29, 2015 by sedenion

[Azrayen]

I'm not sure the M-2000 avionics allow the pilot to select directly a precise CAC mode as in:

Modes "0" Master Arm Switch On/Off Master Arm On / Off

Modes "Ralt – 0" Master Arm Switch Off If enabled disable Master Arm

Modes "1" Navigation Modes Cycle Master Arm Off: Cycle through PCA modes buttons except POL / Master Arm On : Do Nothing

Modes "2" Special Modes Deselect (Normal BVR Mode)

Modes "3" CAC Mode – Vertical Scan

Modes "4" CAC Mode – Bore

Modes "5" CAC Mode – Horizontal Scan

Modes "6" Ground Avoidance Mode

Modes "7" Police Mode On/Off Select / Deselect the POL mode in PCA

Modes "Ralt – 7" Police Mode Off If selected deselect the POL mode in PCA

I guess I would prefer those controls not to be implemented, as I found it's clearer to use the PCA buttons (either clicking or keyboard mapping, player's choice).

 

Not fond of the idea to have all cockpit lights through one control (L) either. That defeat the purpose of having separate controls; it's more interesting and efficient for the (virtual) pilot to explore and choose the correct lightning for his personnal taste and current conditions: you don't use all lightnings at the same time!!

 

In short, I'm all for having keyboard controls for people who don't want to use clickable cockpit, but I don't like the idea of over-simplifying the M-2000 to make it a FC3-style manageable aircraft. That would defeat the purpose of DCS.

For this purpose (more easy stuff), the best way IMO would be to have another, separate, "easy" mapping as it already exists with easy avionics mode for other aircraft.

 

Cheers

Az'

[OnlyforDCS]

I agree with the OP, it's a pretty good list. As for Azrayen's complaint, I feel both camps can be satisfied, wherever we can cycle through something a single keyboard mapping should be used. It doesn't detract from anyone's experience, those who have the HOTAS options or want to click on the switches can still do so.

 

Remember real pilots have hands which they can use to do all of this, we are limited by our mouse and keyboard, so there is no real reason not to simplify the user interface, as it doesn't in any way diminish from the experience or system modeling that's going on 'under the hood' so to speak.

[sedenion]

I'm not sure the M-2000 avionics allow the pilot to select directly a precise CAC mode as in:

 

We can keep a cycle through CAC mode... that's not bad

 

I guess I would prefer those controls not to be implemented, as I found it's clearer to use the PCA buttons (either clicking or keyboard mapping, player's choice).

 

Here we have a "puriste" flavour :D I think it's better to keep some "helpers" shortcuts: Not everybody have a super HOTAS with 36 mappable HATs, and not everybody want to spend time on "clicking" or press keyboard key... Some shortcut command and cycle for PCA is a must i think, even if it's not "so realistic": It's keyboard mapping... If you want to click or press a key for each PCA button, you can, but why prevent cycle rapidly through PCA for players that will find it convenient ?

 

At least, if you want a quick access to PCA modes through 1 2 3 4, we can keep direct access to PCA button with 1 2 3 4 and let "Navigation Modes Cycle", "Special Modes Deselect", etc. on "RShift+1", "RShift+2", "RShift+3", etc.

 

Not fond of the idea to have all cockpit lights through one control (L) either. That defeat the purpose of having separate controls; it's more interesting and efficient for the (virtual) pilot to explore and choose the correct lightning for his personnal taste and current conditions: you don't use all lightnings at the same time!!

 

I am ok with that... one key for all cockpit light is not a good idea... i suggested it without conviction.

 

In short, I'm all for having keyboard controls for people who don't want to use clickable cockpit, but I don't like the idea of over-simplifying the M-2000 to make it a FC3-style manageable aircraft. That would defeat the purpose of DCS.

 

If you keep all other options (individual binding to buttons), why that would defeat the purpose of DCS ?.... here you say "Ok, the Module MUST BE HARD TO PLAY, because, this is a module for real simers who possess the Warthog and all stuff to exploit the module with all its realism"... I'm sorry but this is an egoist (and elitist) position...

 

For this purpose (more easy stuff), the best way IMO would be to have another, separate, "easy" mapping as it already exists with easy avionics mode for other aircraft.

 

:/