Jump to content

Help ED to help us - stateful commands


Recommended Posts

Working perfectly:

SPUU-52 Power :

{down = device_commands.Button_5, cockpit_device_id = devices.SPUU_52, value_down = 1.0, name = 'SPUU-52 Power ON', category = "Left Electropanel's Dash"},
{down = device_commands.Button_5, cockpit_device_id = devices.SPUU_52, value_down = 0.0, name = 'SPUU-52 Power OFF', category = "Left Electropanel's Dash"},

Coordinates Calculator Controls :

{down = device_commands.Button_2, up = device_commands.Button_2, cockpit_device_id = devices.DISS_15, value_down = 1.0, value_up = 0.0, name = 'Coordinates Calculator OFF', category = "Coordinates Calculator"},
{down = device_commands.Button_3, up = device_commands.Button_3, cockpit_device_id = devices.DISS_15, value_down = 1.0, value_up = 0.0, name = 'Coordinates Calculator ON', category = "Coordinates Calculator"},
{down = device_commands.Button_4, up = device_commands.Button_4, cockpit_device_id = devices.DISS_15, value_down = 1.0, value_up = 0.0, name = 'Map Angle Decrease', category = "Coordinates Calculator"},
{down = device_commands.Button_5, up = device_commands.Button_5, cockpit_device_id = devices.DISS_15, value_down = 1.0, value_up = 0.0, name = 'Map Angle Increase', category = "Coordinates Calculator"},
{down = device_commands.Button_6, up = device_commands.Button_6, cockpit_device_id = devices.DISS_15, value_down = 1.0, value_up = 0.0, name = 'Path km Decrese', category = "Coordinates Calculator"},
{down = device_commands.Button_7, up = device_commands.Button_7, cockpit_device_id = devices.DISS_15, value_down = 1.0, value_up = 0.0, name = 'Path km Increase', category = "Coordinates Calculator"},
{down = device_commands.Button_8, up = device_commands.Button_8, cockpit_device_id = devices.DISS_15, value_down = 1.0, value_up = 0.0, name = 'Deviation km Decrease', category = "Coordinates Calculator"},
{down = device_commands.Button_9, up = device_commands.Button_9, cockpit_device_id = devices.DISS_15, value_down = 1.0, value_up = 0.0, name = 'Deviation km Increase', category = "Coordinates Calculator"},

Drift Angle Gauge Controls :

{down = device_commands.Button_11, cockpit_device_id = devices.DISS_15, value_down = 1.0, name = 'Drift Angle Indicator TEST', category = "Coordinates Calculator"},
{down = device_commands.Button_11, cockpit_device_id = devices.DISS_15, value_down = 0.0, name = 'Drift Angle Indicator OPER', category = "Coordinates Calculator"},
{down = device_commands.Button_12, cockpit_device_id = devices.DISS_15, value_down = 1.0, name = 'Drift Angle Indicator SEA', category = "Coordinates Calculator"},
{down = device_commands.Button_12, cockpit_device_id = devices.DISS_15, value_down = 0.0, name = 'Drift Angle Indicator LAND', category = "Coordinates Calculator"},

 

Almost working :

Navigation Lights (
No difference between DIM and BRIGHT
(the code itself works)
) :
{down = device_commands.Button_12, cockpit_device_id = devices.NAVLIGHT_SYSTEM, value_down = 1.0, name = 'Navigation Lights Bright', category = "Right Electropanel's Dash"},
{down = device_commands.Button_12, cockpit_device_id = devices.NAVLIGHT_SYSTEM, value_down = 0.0, name = 'Navigation Lights OFF', category = "Right Electropanel's Dash"},
{down = device_commands.Button_12, cockpit_device_id = devices.NAVLIGHT_SYSTEM, value_down = -1.0, name = 'Navigation Lights DIM', category = "Right Electropanel's Dash"},

Formation Lights (
No difference between DIM and BRIGHT (the code itself works)
) :
{down = device_commands.Button_13, cockpit_device_id = devices.NAVLIGHT_SYSTEM, value_down = 1.0, name = 'Formation Lights Bright', category = "Right Electropanel's Dash"},
{down = device_commands.Button_13, cockpit_device_id = devices.NAVLIGHT_SYSTEM, value_down = 0.0, name = 'Formation Lights OFF', category = "Right Electropanel's Dash"},
{down = device_commands.Button_13, cockpit_device_id = devices.NAVLIGHT_SYSTEM, value_down = -1.0, name = 'Formation Lights DIM', category = "Right Electropanel's Dash"},
Link to comment
Share on other sites

Excuse my ignorance Madcat,I have found the route to my Defualt.Lua folder via (DCS World/Mods/aircrafts/ "aircraft" /Input/ "device" /default.lua).

 

I have then copied and paste the 'Armament Safety Selector' text into my Joystick Default.Lua folder,down at the bottom of the text within it,and then tried to save it as required,but I get 'Access Denied',am I doing something wrong here ? :doh:...........my first time editing controller scripts btw,sorry.

Hi Basco1 !

 

Honestly I've never gotten any error message when editing those files.

So unfortunately I can only give some advice you may know and took care of already:

 

  • only use Notepad++ to edit those files

     

    [*]close all programs that could potentially currently read the file

    [*]make sure the file is not write-protected

    [*]make sure you enter the code before the last two curly brackets

    • in case of joystick files, I always add the code before the curly bracket prior to the "axisCommands" section

     

Hope you get this solved or somebody else has a better idea than I do!

 

 

Greetings

MadCat

Link to comment
Share on other sites

Thanks Madcat,yes the problem's my end I'm sure.

Chillblast Fusion Cirrus 2 FS Pc/Intel Core i7-7700K Kaby Lake CPU/Gigabyte Nvidia GTX 1070 G1 8GB/Seagate 2TB FireCuda SSHD/16GB DDR4 2133MHz Memory/Asus STRIX Z270F Gaming Motherboard/Corsair Hydro Series H80i GT Liquid Cooler/TM Warthog with MFG 10cm Extension/WINWING Orion Rudder Pedals (With Damper Edition)/TrackiR5/Windows 11 Home

Link to comment
Share on other sites

Working perfectly:

 

Batteries :

{down = device_commands.Button_2, cockpit_device_id = devices.ELEC_INTERFACE, value_down = 1.0, name = 'Battery 2 ON', category = "Right Electropanel's Dash"},
{down = device_commands.Button_2, cockpit_device_id = devices.ELEC_INTERFACE, value_down = 0.0, name = 'Battery 2 OFF', category = "Right Electropanel's Dash"},

 

Hi. Batt 2, really works? It didn't work for me.

i7-2600 @3.4GHz | Corsair 16GB @1600MHz. | MSI GTX1660Ti Gaming X | Samsung 256GB SSD (Win10HPx64)
Samsung G5 32" + Samsung 18" + 2x8"TFT Displays | Saitek X-55 Rhino & Rudder | TM MFD Cougars | Logitech G13, G230, G510, PZ55 & Farming Sim Panel | TIR5
>>MY MODS<< | Discord: Devrim#1068

Link to comment
Share on other sites

  • 2 weeks later...

Hi,

Thanks for the effort. I have a problem though.

When I enter the commands in the default .lua file and then open

the settings in options all commands are greyed out. I cannot assign

any of them. Any solution to this?

[sIGPIC][/sIGPIC]

_____________Semper paratus, In hoc signo vinces________________

 

PC: Intel i7-8700K (4.9 GHz), Aorus Ultra Gaming Z370 MB, Gigabyte RTX 3080, 32 GB DDR3 (3,2 GHz), Samsung EVO 860 M.2 500 GB SSD + Samsung 960 M.2 250 GB SSD Gaming: Virpil T-50 CM2, TM WH Throttle, Crosswind pedals, HP Reverb

Link to comment
Share on other sites

  • 3 weeks later...
Hi,

Thanks for the effort. I have a problem though.

When I enter the commands in the default .lua file and then open

the settings in options all commands are greyed out. I cannot assign

any of them. Any solution to this?

 

Did you add the commands to both the Input\Joystick\Default.lua and Input\Keyboard\Default.lua? From your description it sounds like you've added them to only one of them.

 

Anyway, in today's "I really can't believe they left out this command" segment: Separate up and down keys for the landing gear in the P-51D/TF-51D.

 

Working perfectly:

{down = device_commands.Button_3, cockpit_device_id  = devices.CONTROL_SYSTEM, value_down = 1.0, name = 'Gear Up', category = 'Systems'},
{down = device_commands.Button_3, cockpit_device_id  = devices.CONTROL_SYSTEM, value_down = -1.0, name = 'Gear Down', category = 'Systems'},


Edited by Olethros
Link to comment
Share on other sites

Good and some "neutral" news!

 

As of the latest patch 1.2.10.32095 released today, the situation is as follows:

 

Fw190D-9:

ED adopted
almost every
command, or edited them themselves (yet all the naming is identical to this thread :music_whistling:).

"Gunsight ON" and "Gunsight OFF" now work the gyros, yet in the control options it does still say "Gunsight ON (OFF)".

Either way, they are in by default now,
thank you
!

 

Not adopted to the Fw190:

"Bomb Emergency Release Push" (maybe that handle is in fact spring loaded, I don't know)

"Rocket Emergency Release Cover Close" (I thought that cover/lock was spring loaded)

I will investigate on those two commands, maybe it is correct how it is now (or somebody with more information about these, PM me please)

 

P-51D/TF-51D:

Commands for the "Fuel Booster" have been added by default.

 

Not adopted to the P-51D/TF-51D:

Commands for Landing Gear Up and Down.

 

 

For all the other airframes in this thread (Ka-50, Mi-8, UH-1, F-86), no commands were adopted to the default controls.

I may bring this thread specifically to the attention of BST too.

 

 

NOTE:

All remaining codes are still working, yet some may require reassignment in the options.

 

NOTE 2:

All the commands that are default by now, were deleted from the respective posts.

Thank you again, ED !:thumbup:

 

 

Greetings

MadCat


Edited by -=MadCat=-
Link to comment
Share on other sites

Good and some "neutral" news!

 

As of the latest patch 1.2.10.32095 released today, the situation is as follows:

 

Fw190D-9:

ED adopted almost
every
command, or edited them themselves (yet all the naming is identical to this thread :music_whistling:).

 

For all the other airframes (Ka-50, Mi-8, UH-1, F-86), no commands were adopted to the default controls.

I may bring this thread specifically to the attention of BST too.

 

Greetings

MadCat

 

Good work, MadCat. I'm sure the devs would agree with my statement. :P

 

Is it just me or did they switch all Huey commands to the device_commands.Button_X format? I didn't keep the old files to check.

Link to comment
Share on other sites

  • 2 months later...
Hi everybody!

 

introduction of diff.lua files, I think we can help ED to give us more convenient controls by default.

 

Please explain the diff-files?

 

For example, in my C:\Users\pappavis\Saved Games\DCS\Config\Input\MiG- 21Bis\keyboard\ this diff-file is like this;

 

MiG-21Bis Keyboard.diff.lua;

local diff = {
["keyDiffs"] = {
	["d3116pnilunilcd12vd1vpnilvunil"] = {
		["name"] = "Airbrakes On",
		["removed"] = {
			[1] = {
				["key"] = "C",
			},
		},
	},
},
}
return diff

 

Where must i place the code you provide here for alternate inputs?

met vriendelijke groet,

Михель

 

"умный, спортсмен, комсомолетс"

 

[sIGPIC]159th_pappavis.jpg[/sIGPIC]

 

[TABLE]SPECS: i9-9900K 32gigs RAM, Geforce 2070RTX, Creative XFi Fata1ity, TIR5, Valve Index & HP Reverb, HOTAS Warthog, Logitech G933 Headset, 10Tb storage.[/TABLE]

Link to comment
Share on other sites

  • 3 weeks later...

@pappavis:

I cannot help you with commands unique to the MiG-21 as I don't have that module.

However all the other commands in this thread need to be put in the default.lua files for the respective aircraft and input device.

Check the -> first post <- of this thread for detailed information where and how to copy and paste them.

If it is still not working after that, PM me (again, I cannot check code for the MiG-21).

 

 

@everybody

With the release of the Bf109K-4 I was very happy to see how wide-ranging the control options are.

We may got something moving with this thread, thank you ED, and not to forget thanks to everyone who contributed thus far :thumbup:

Hopefully 3rd party developers will add commands to their default files too! :music_whistling:

 

 

The only not existing commands for the Bf109K-4 are listed below.

As I was working in the default.lua files, I noticed some "hints" that ED seems to be working on the missing commands already.

For the time being, here go my additions.

 

 

 

Bf109K-4 :

Working perfectly
:

 

FuG16ZY Volume:

{pressed = device_commands.Button_4, cockpit_device_id = devices.VHF_RADIO, value_pressed = 0.5, name = _('FuG16ZY Volume Increase'), category = _('VHF Radio')},
{pressed = device_commands.Button_4, cockpit_device_id = devices.VHF_RADIO, value_pressed = -0.5, name = _('FuG16ZY Volume Decrease'), category = _('VHF Radio')},

FuG16ZY Fine Tune:

{pressed = device_commands.Button_9, cockpit_device_id = devices.VHF_RADIO, value_pressed = 0.2, name = _('FuG16ZY Fine Tune Increase'), category = _('VHF Radio')},
{pressed = device_commands.Button_9, cockpit_device_id = devices.VHF_RADIO, value_pressed = -0.2, name = _('FuG16ZY Fine Tune Decrease'), category = _('VHF Radio')},

FuG25a IFF Test (
Note
: IFF not modeled in DCS, only button animation working):

{down = device_commands.Button_14, up = device_commands.Button_14, cockpit_device_id = devices.VHF_RADIO, value_down = 1.0, value_up = 0.0, name = _('FuG25a Test'), category = _('FuG 25a IFF Control Unit')},

 

Almost working:

Microphone PTT (
button animation works, yet does not seem to be "wired" yet
):

{down = device_commands.Button_56, up = device_commands.Button_56,  cockpit_device_id = devices.FUSEBOX, value_down = 1.0, value_up = 0.0,  name = _('Microphone PTT'), category = _('VHF Radio')},

 

Additional note:

Due to very limited time, I did not yet check all the other modules for potentially added code out of this thread to the default.lua files.

I will do that once I have the spare time and then update this post/thread accordingly.

 

 

So long, greetings and a blessed christmas season to everyone !:xmas:

MadCat

  • Like 1
Link to comment
Share on other sites

  • 1 month later...

Thanks for all the great work here MadCat. I'm new to DCS and the F86 but this thread really helped me get my controls working the way I want.

 

I have a few more additions for the F86, all working perfectly. Forgive me if I double up on anything that already exists, I tried to keep it with only commands not on the "master" F86 post of this thread.

 

Taxing and Landing Light Switch

{down = nav_lights_commands.F86_CockpitDeviceCommand_LandAndTaxiLights, cockpit_device_id = devices.NAV_LIGHTS_INTERFACE, value_down = 1,  name = _('Landing & Taxi Lights Switch - Extend/On'),    category = _('Left Forward Console')},
{down = nav_lights_commands.F86_CockpitDeviceCommand_LandAndTaxiLights, cockpit_device_id = devices.NAV_LIGHTS_INTERFACE, value_down = 0, name = _('Landing & Taxi Lights Switch - Off'),    category = _('Left Forward Console')},
{down = nav_lights_commands.F86_CockpitDeviceCommand_LandAndTaxiLights, cockpit_device_id = devices.NAV_LIGHTS_INTERFACE, value_down = -1, name = _('Landing & Taxi Lights Switch - Retract'),    category = _('Left Forward Console')},

Engine Anti-Ice/Screen Switch

{down = air_commands.F86_CockpitDeviceCommand_EngineAntiIceScreen, cockpit_device_id = devices.AIR_INTERFACE, value_down = 1,  name = _('Engine Anti-Ice & Screen Switch - Extend'),    category = _('Left Forward Console')},
{down = air_commands.F86_CockpitDeviceCommand_EngineAntiIceScreen, cockpit_device_id = devices.AIR_INTERFACE, value_down = 0,  name = _('Engine Anti-Ice & Screen Switch - Retract'),    category = _('Left Forward Console')},
{down = air_commands.F86_CockpitDeviceCommand_EngineAntiIceScreen, cockpit_device_id = devices.AIR_INTERFACE, value_down = -1,  name = _('Engine Anti-Ice & Screen Switch - Anti-Ice'),    category = _('Left Forward Console')},

Pitot Heat Switch

{down = air_commands.F86_CockpitDeviceCommand_PitotHeater_Sw, cockpit_device_id = devices.AIR_INTERFACE, value_down = 1,   name = _('Pitot Heater Switch - On'),     category = _('Left Forward Console')},
{down = air_commands.F86_CockpitDeviceCommand_PitotHeater_Sw, cockpit_device_id = devices.AIR_INTERFACE, value_down = 0,   name = _('Pitot Heater Switch - Off'),     category = _('Left Forward Console')},

Position and Fuselage Light Switch

{down = nav_lights_commands.F86_CockpitDeviceCommand_PosAndFusLts,         cockpit_device_id = devices.NAV_LIGHTS_INTERFACE,    value_down = 1, name = _('Position and Fuselage Light Selector Switch - Steady'), category = _('Right Forward Console')},
{down = nav_lights_commands.F86_CockpitDeviceCommand_PosAndFusLts,         cockpit_device_id = devices.NAV_LIGHTS_INTERFACE,    value_down = 0, name = _('Position and Fuselage Light Selector Switch - Off'), category = _('Right Forward Console')},
{down = nav_lights_commands.F86_CockpitDeviceCommand_PosAndFusLts,         cockpit_device_id = devices.NAV_LIGHTS_INTERFACE,    value_down = -1, name = _('Position and Fuselage Light Selector Switch - Flash'), category = _('Right Forward Console')},

Generator Switch

{down = electric_commands.F86_CockpitDeviceCommand_GeneratorSw,         cockpit_device_id = devices.ELEC_INTERFACE,    value_down = 1, name = _('Generator Switch - On'),            category = _('Right Forward Console')},
{down = electric_commands.F86_CockpitDeviceCommand_GeneratorSw,         cockpit_device_id = devices.ELEC_INTERFACE,    value_down = 0, name = _('Generator Switch - Off'),            category = _('Right Forward Console')},

Also, up the way I noticed one of the testers asking what commands were still needed. Hopefully someone here already has an answer, but if not there are a few things I would like to see.

 

-A working button to start the aircraft's elapsed time clock- the bindings already listed in the game control settings (systems tab) don't seem to work.

-Pressurization/Life support controls- I can't find any way to bind the pressurization diff switch (2.5/5 PSI iirc), the oxygen regulator lever (starts in the off position on a cold start), the ram/bleed select switch, and even the normal/100% O2 switch, even though I have never found a reason to move it.

-Commands to move the manual bombing control panel functions- IE the depression knob, a button to flip the altitude cards, and a button for the mode switch on the panel (bomb/normal I think). I'm talking about the panel on the upper dash at the lower left of the A4 sight itself. Some bindings exist to adjust the bombing altimeter on the A4, but nothing for the bomb panel.

 

Thanks, and thanks again MadCat for an outstanding thread.

Multiplayer as Variable

 

Asus Z97-A - I7 4790K - 32 GB HyperX - EVGA GTX 1080 Ti - Corsair 750i PSU

 

TM Warthog HOTAS - TM Cougar MFDs - CH Pedals - TrackIR 5 - Samsung RU8000 55”

Link to comment
Share on other sites

  • 1 month later...
  • 4 months later...

I'm not sure if this is the proper thread for it, but I found that adding these lines to the default.lua of the Mi-8 adds assignable axis for the PKV gunsight. :music_whistling:

 

 
{action = 3001, cockpit_device_id = 47, name = "PKV Intensity"}, 
{action = 3003, cockpit_device_id = 47, name = "PKV Elevation"},

Happy Flying! :pilotfly:

Link to comment
Share on other sites

  • Recently Browsing   0 members

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