Jump to content

[RESOLVED] Common thread for all missing / wrong control binds


Kercheiz

Recommended Posts

Here is list all the stuff in the mirage that you can control properly by clicking in the cockpit, but can't via binds. It's not just a lack of features, it makes the module very hard to use in challenging, multiplayer, radio intensive situations.

 

My first take:

 

  • Most multiposition knobs lack increase/decrease commands and we can't bind an encoder. HOTAS and panels have lots of encoders we would like to use with.
    • UHF Channel preset
    • V/UHF Channel preset
    • TACAN 10 digit
    • TACAN 1 digit
    • PCN Mode
  • The ALT pressure has increase/decrease binds but these are using "pressed" action, which makes the pressure change by a bunch of millibars for the slightest input. It's unusable, changing them to "down" would allow millibar input.
  • Missing V/UHF numpad binds. Entering manual frequencies on the tiny buttons in VR is a real, real pain

 

 

Link to comment
Share on other sites

I can confirm that changing:

 

    {pressed = iCommandAltimeterPressureIncrease, up = iCommandAltimeterPressureStop, name = _('Alt Pressure INCREASE'), category = _('Autopilot, Navigation, & INS')},
    {pressed = iCommandAltimeterPressureDecrease, up = iCommandAltimeterPressureStop, name = _('Alt Pressure DECREASE'), category = _('Autopilot, Navigation, & INS')},

To:

 

    {down = iCommandAltimeterPressureIncrease, name = _('Alt Pressure INCREASE'), category = _('Autopilot, Navigation, & INS')},
    {down = iCommandAltimeterPressureDecrease, name = _('Alt Pressure DECREASE'), category = _('Autopilot, Navigation, & INS')},

 

Does fix the crazy ALT pressure control issue.

Regarding the missing V/UHF numpad binds, this does solve it:

 

	{down = 3952, up = 3952, cockpit_device_id = devices.VHF,	value_down = 1,		value_up = 0,		name = _('VHF MEM/CLR'),	category = _('Radio')},
	{down = 3953, up = 3953, cockpit_device_id = devices.VHF,	value_down = 1,		value_up = 0,		name = _('VHF VLD/XFR'),	category = _('Radio')},
	{down = 3954, up = 3954, cockpit_device_id = devices.VHF,	value_down = 1,		value_up = 0,		name = _('VHF 1/READ'),		category = _('Radio')},
	{down = 3955, up = 3955, cockpit_device_id = devices.VHF,	value_down = 1,		value_up = 0,		name = _('VHF 2/SQL'),		category = _('Radio')},
	{down = 3956, up = 3956, cockpit_device_id = devices.VHF,	value_down = 1,		value_up = 0,		name = _('VHF 3/GR'),		category = _('Radio')},
	{down = 3957, up = 3957, cockpit_device_id = devices.VHF,	value_down = 1,		value_up = 0,		name = _('VHF 4'),			category = _('Radio')},
	{down = 3958, up = 3958, cockpit_device_id = devices.VHF,	value_down = 1,		value_up = 0,		name = _('VHF 5/20/LOW'),	category = _('Radio')},
	{down = 3959, up = 3959, cockpit_device_id = devices.VHF,	value_down = 1,		value_up = 0,		name = _('VHF 6/TONE'),		category = _('Radio')},
	{down = 3960, up = 3960, cockpit_device_id = devices.VHF,	value_down = 1,		value_up = 0,		name = _('VHF 7'),			category = _('Radio')},
	{down = 3961, up = 3961, cockpit_device_id = devices.VHF,	value_down = 1,		value_up = 0,		name = _('VHF 8/TOD'),		category = _('Radio')},
	{down = 3962, up = 3962, cockpit_device_id = devices.VHF,	value_down = 1,		value_up = 0,		name = _('VHF 9/ZERO'),		category = _('Radio')},
	{down = 3963, up = 3963, cockpit_device_id = devices.VHF,	value_down = 1,		value_up = 0,		name = _('VHF 0'),			category = _('Radio')},
	{down = 3964, up = 3964, cockpit_device_id = devices.VHF,	value_down = 1,		value_up = 0,		name = _('VHF CONF'),		category = _('Radio')},

 

Link to comment
Share on other sites

Important button bindings missing from joystick\default.lua (though can get them from clickabledata.lua

 

3467  Engine Shutdown Button

 

Important axis bindings missing from joystick\default.lua (though can get them from clickabledata.lua):

 

{action = 3209, cockpit_device_id = 5, name = _('Target Wingspan')},
{action = 3192, cockpit_device_id = 5, name = _('Minimum Altitude Selector')},
{action = 3703, cockpit_device_id = 16, name = _('MAGIC Tone Volume')},
{action = 3705, cockpit_device_id = 16, name = _('Marker and SERVAL Volume')},
{action = 3706, cockpit_device_id = 16, name = _('UHF Radio Volume')},
{action = 3707, cockpit_device_id = 16, name = _('V/UHF Radio Volume')},
 

Mappings that are/were incorrect in joystick\default.lua:

 

    --RADALT - This is RADAR ALTIMETER POWER, not MODE, and mappings were to incorrect toggle positions

    -- Below are corrected mappings and names
    {down = 3205, up = 3205, cockpit_device_id = 5, value_down = 0,   name = _('Radar Altimeter Power OFF'), category = _('Sensors')},
    {down = 3205, up = 3205, cockpit_device_id = 5, value_down = 0.5, name = _('Radar Altimeter Power ON'), category = _('Sensors')},
    {down = 3205, up = 3205, cockpit_device_id = 5, value_down = 1,   name = _('Radar Altimeter Power TEST'), category = _('Sensors')},
 

--Subsystems
  -- Electrical
  -- Names were HUD Altimeter Power Switch, but this is Altimeter VTH Mode
    -- Below are corrected mappings and names
    {down = 3204, up = 3204, cockpit_device_id = 5, value_down = 0, name = _('Altimeter Mode Barometric'), category = _('Electrical')},
    {down = 3204, up = 3204, cockpit_device_id = 5, value_down = 0.5, name = _('Altimeter Mode Radar'), category = _('Electrical')},
    {down = 3204, up = 3204, cockpit_device_id = 5, value_down = 1, name = _('Altimeter Mode Minimum'), category = _('Electrical')},

Link to comment
Share on other sites

On 12/10/2020 at 9:52 PM, tanr said:

Important button bindings missing from joystick\default.lua (though can get them from clickabledata.lua

 

3467  Engine Shutdown Button

 

Do you mean the throttle "STOP" detent, unlocked with the little red button besides the throttle, which stops the engine?

 

 

Link to comment
Share on other sites

 

13 hours ago, tanr said:

Yes, that one.

 

It has a bind, "Engines STOP" in "Engine & Fuel". I use it and just checked it's there and works.

 

 

On 12/14/2020 at 1:25 PM, jojo said:

Impressive work guys 👍

 

Can you do your editing in "Saved Games" or do you have to do it in Core folders (loosing it at each DCS World update) ?

Unfortunately, only in the core folders. DCS stores modified file in a "Backup" folder when overwriting during an update, but you still have to restore it.


Edited by galinette
Link to comment
Share on other sites

  • 1 month later...
  • RAZBAM_ELMO changed the title to [RESOLVED] Common thread for all missing / wrong control binds
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...