No HOTAS Controls in dcs world

[fabrizi]

Hi there, i just got dcs world, but i was a constant user of DCS a-10c and in dcs a-10 i could asign a control like Joy_Btn_9 + joy_hat_up (joy button 9 was a "extension" or atleast it was in dcs a-10) now in dcs world, i loaded up the same control sceam that i used in dcs a-10 and there are errors where there is a HOTAS extenion ,im using the thrustmasters t.flight hotas by the way. is there a way to fix this or change somethign but keeping the same controls

[cichlidfan]

You need to tell DCS world about the 'extension' (DCS calls them modifiers) that you are using. Your profile does not include that setting so you have to assign it again. Once you do all of your red controls will be fixed.

[fabrizi]

Yeah, the thing is when i try to reset the controls, i look for the modifier that i was using before, it was btn 9 (for example) and its not available in dcs world, Yet at least

[cichlidfan]

I have not messed with any of that in DCS World since I program my HOTAS outside of the sim.

 

My recollection of setting modifiers in A-10 was that you could pick from a list or, what I did, just press the desired button to fill in the field. If that is not working then there might be a bug in there or possibly your config file(s) have gotten corrupted.

[EtherealN]

now in dcs world, i loaded up the same control sceam that i used in dcs a-10 and there are errors where there is a HOTAS extenion

 

By "loading loading up the same control scheme", do you literally mean using the same files?

 

If so, this will indeed not work, since World is a larger, non-plane-specific, framework, and you'll have to configure within the program for each aircraft. Copy-pasting will cause corrupt files, since the expected file format and syntax will be different.

[tintifaxl]

The incompatibilities of input definition files between patch levels is one of the quirks I wish ED would do something about. Maybe a little tool that takes the old input files and converts them to the new format?

[Yskonyn]

There have been changes in the format, so we won't get around redoing our configs in DCS World.

 

As for Fabrizi; in the lower left on the controls options menu you will find a button labeled 'Modifiers'. Here you can add any key or joystick button you want to act as one.

Then you can reprogram your profile as you want again.

[winz]

The incompatibilities of input definition files between patch levels is one of the quirks I wish ED would do something about. Maybe a little tool that takes the old input files and converts them to the new format?

Don't want to sound like a smart-ass, but that's why it is beneficial to use the hotas profiles for keybinds and not the in-game key setup. :)

[Yskonyn]

Don't want to sound like a smart-ass, but that's why it is beneficial to use the hotas profiles for keybinds and not the in-game key setup. :)

 

Well its not that you have to keep changing stuff all the time. Just now, once, because we transfer to a new integrated system. Inconvenient? Yes. A big problem? No.

The keybinds inside DCS work great without having to resort to 3rd party tools or profiling software. :joystick: ;)

[cichlidfan]

Actually, I have found that if your lua files are cleaned out of any functions not needed, by the controller involved, that they transfer just fine. I use a custom lua file for every controller and moved all of them from A-10 to World with not one problem.

 

For example, this is my A-10 rudder lua in its entirety:

 

function layout()

return {

forceFeedback = {

trimmer = 1,

shake = 0.5,

swapAxes = false,

},

keyCommands = {

},

axisCommands = {

{combos = {{key = "JOY_RZ", filter = {saturationX = 1, saturationY = 1, deadzone = 0.05, invert = false, slider = false, curvature = {0.41}}}, }, action = iCommandPlaneRudder, name = "Rudder"},

{combos = {{key = "JOY_X", filter = {saturationX = 1, saturationY = 1, deadzone = 0, invert = true, slider = false, curvature = {0}}}, }, action = iCommandLeftWheelBrake, name = "Wheel Brake Left"},

{combos = {{key = "JOY_Y", filter = {saturationX = 1, saturationY = 1, deadzone = 0, invert = true, slider = false, curvature = {0}}}, }, action = iCommandRightWheelBrake, name = "Wheel Brake Right"},

},

}

end

 

and my Warthog lua:

 

 

 

function layout()

return {

forceFeedback = {

trimmer = 1,

shake = 0.5,

swapAxes = false,

},

keyCommands = {

{combos = {{key = "JOY_BTN3"}, }, down = iCommandPlane_AAP_SteerSw_Down, up = iCommandPlane_AAP_SteerSw_Down, name = "AAP STEER Switch Down", category = "AAP"},

{combos = {{key = "JOY_BTN5"}, }, down = iCommandPlane_AAP_SteerSw_Up, up = iCommandPlane_AAP_SteerSw_Up, name = "AAP STEER Switch Up", category = "AAP"},

{combos = {{key = "JOY_BTN20"}, }, down = iCommandPlane_APU_Start, up = iCommandPlane_APU_Off, name = "APU Start/Off", category = "Engine Control Panel"},

{combos = {{key = "JOY_BTN24"}, }, down = iCommandPlane_EAC_ARM, up = iCommandPlane_EAC_OFF, name = "EAC Arm/Off", category = "LASTE Control Panel"},

{combos = {{key = "JOY_BTN10"}, }, down = iCommandPlane_HOTAS_BoatSwitchAft, up = iCommandPlane_HOTAS_BoatSwitchCenter, name = "HOTAS Boat Switch Aft", category = "HOTAS"},

{combos = {{key = "JOY_BTN9"}, }, down = iCommandPlane_HOTAS_BoatSwitchForward, up = iCommandPlane_HOTAS_BoatSwitchCenter, name = "HOTAS Boat Switch Forward", category = "HOTAS"},

{combos = {{key = "JOY_BTN12"}, }, down = iCommandPlane_HOTAS_ChinaHatAft, up = iCommandPlane_HOTAS_ChinaHatOff, name = "HOTAS China Hat Aft", category = "HOTAS"},

{combos = {{key = "JOY_BTN11"}, }, down = iCommandPlane_HOTAS_ChinaHatForward, up = iCommandPlane_HOTAS_ChinaHatOff, name = "HOTAS China Hat Forward", category = "HOTAS"},

{combos = {{key = "JOY_BTN15"}, }, down = iCommandPlane_HOTAS_LeftThrottleButton, up = iCommandPlane_HOTAS_LeftThrottleButton_Off, name = "HOTAS Left Throttle Button", category = "HOTAS"},

{combos = {{key = "JOY_BTN26"}, }, down = iCommandPlaneAutopilot, up = iCommandPlaneAutopilot, name = "LAAP Engage/Disengage", category = "LASTE Control Panel"},

{combos = {{key = "JOY_BTN28"}, }, down = iCommandPlaneStabHbarBank, up = iCommandPlaneStabHbarHeading, name = "LAAP Mode Selector (ALT)", category = "LASTE Control Panel"},

{combos = {{key = "JOY_BTN27"}, }, down = iCommandPlaneStabPathHold, up = iCommandPlaneStabHbarHeading, name = "LAAP Mode Selector (PATH)", category = "LASTE Control Panel"},

{combos = {{key = "JOY_BTN16"}, }, down = iCommandPlane_L_ENG_FUEL_FLOW_Norm, up = iCommandPlane_L_ENG_FUEL_FLOW_Override, name = "Left Engine Fuel Flow Norm/Override", category = "Engine Control Panel"},

{combos = {{key = "JOY_BTN31"}, }, down = iCommandPlane_L_ENG_OPER_Ign, up = iCommandPlane_L_ENG_OPER_Norm, name = "Left Engine Oper Ign / Norm", category = "Engine Control Panel"},

{combos = {{key = "JOY_BTN18"}, }, down = iCommandPlane_L_ENG_OPER_Motor, up = iCommandPlane_L_ENG_OPER_Norm, name = "Left Engine Oper Motor / Norm", category = "Engine Control Panel"},

{combos = {{key = "JOY_BTN30"}, }, down = iCommandLeftEngineStop, up = iCommandLeftEngineStart, name = "Left Engine Throttle Set OFF", category = "Systems"},

{combos = {{key = "JOY_BTN25"}, }, down = iCommandPlane_RDR_ALTM_NRM, up = iCommandPlane_RDR_ALTM_DIS, name = "RDR ALTM Normal/Disable", category = "LASTE Control Panel"},

{combos = {{key = "JOY_BTN17"}, }, down = iCommandPlane_R_ENG_FUEL_FLOW_Norm, up = iCommandPlane_R_ENG_FUEL_FLOW_Override, name = "Right Engine Fuel Flow Norm/Override", category = "Engine Control Panel"},

{combos = {{key = "JOY_BTN32"}, }, down = iCommandPlane_R_ENG_OPER_Ign, up = iCommandPlane_R_ENG_OPER_Norm, name = "Right Engine Oper Ign / Norm", category = "Engine Control Panel"},

{combos = {{key = "JOY_BTN19"}, }, down = iCommandPlane_R_ENG_OPER_Motor, up = iCommandPlane_R_ENG_OPER_Norm, name = "Right Engine Oper Motor / Norm", category = "Engine Control Panel"},

{combos = {{key = "JOY_BTN29"}, }, down = iCommandRightEngineStop, up = iCommandRightEngineStart, name = "Right Engine Throttle Set OFF", category = "Systems"},

{combos = {{key = "JOY_BTN23"}, }, down = iCommandPlane_FLAPS_DN, up = iCommandPlane_FLAPS_MNR, name = "Toggle Flaps Dn", category = "Systems"},

{combos = {{key = "JOY_BTN22"}, }, down = iCommandPlane_FLAPS_UP, up = iCommandPlane_FLAPS_MNR, name = "Toggle Flaps Up", category = "Systems"},

},

axisCommands = {

{combos = {{key = "JOY_RX", filter = {saturationX = 1, saturationY = 0.15, deadzone = 0.3, invert = false, slider = false, curvature = {0}}}, }, action = iCommandPlaneSelecterHorizontalAbs, name = "HOTAS Slew Horizontal"},

{combos = {{key = "JOY_RY", filter = {saturationX = 1, saturationY = 0.15, deadzone = 0.3, invert = false, slider = false, curvature = {0}}}, }, action = iCommandPlaneSelecterVerticalAbs, name = "HOTAS Slew Vertical"},

{combos = {{key = "JOY_Y", filter = {saturationX = 1, saturationY = 1, deadzone = 0, invert = false, slider = false, curvature = {0.35}}}, }, action = iCommandPlanePitch, name = "Pitch"},

{combos = {{key = "JOY_X", filter = {saturationX = 1, saturationY = 1, deadzone = 0, invert = false, slider = false, curvature = {0.35}}}, }, action = iCommandPlaneRoll, name = "Roll"},

{combos = {{key = "JOY_RZ"}, }, action = iCommandPlaneThrustLeft, name = "Throttle Left"},

{combos = {{key = "JOY_Z"}, }, action = iCommandPlaneThrustRight, name = "Throttle Right"},

},

}

end

 

 

 

 

EDIT: @fabrizi Have you looked at the modifiers.lua from your A-10 install (it is in C:\Users\<yourname>\Saved Games\DCS Warthog\Config\Input)? Did you copy that over as well? If you look at it with an editor (Notepad++ preferably) you should be able to see how your key assignment should look. The lines in the file for world have an additional option (it was removed in A-10) so there is a slight difference.

 

EDIT 2: Btw, the A-10 GUI manual specifically mentions the problem the OP is seeing. Missing modifier.

 

Red conflict text appears when there are incorrect modifiers. For example, if you delete one of the present modifiers, then all strings with this modifier will be shown in red.

Edited July 4, 2012 by cichlidfan

[cichlidfan]

I just connected a TM T.Flight HOTAS X to a clean install of DCS World and assigned button 9 as a modifier. This is what the modifiers.lua looks like:

 

NOTE: Red text is the line that was added by the change. The rest is all default.

 

return {

["RAlt"] = {key = "RAlt", device = "Keyboard", switch = false},

["RCtrl"] = {key = "RCtrl", device = "Keyboard", switch = false},

["LWin"] = {key = "LWin", device = "Keyboard", switch = false},

["LCtrl"] = {key = "LCtrl", device = "Keyboard", switch = false},

["JOY_BTN9"] = {key = "JOY_BTN9", device = "T.Flight Hotas X {DF0BB730-C5F2-11e1-8001-444553540000}", switch = false},

["RWin"] = {key = "RWin", device = "Keyboard", switch = false},

["RShift"] = {key = "RShift", device = "Keyboard", switch = false},

["MOUSE_BTN3"] = {key = "MOUSE_BTN3", device = "Mouse", switch = false},

["LShift"] = {key = "LShift", device = "Keyboard", switch = false},

["LAlt"] = {key = "LAlt", device = "Keyboard", switch = false},

}

[swordfish45]

Just an FYI, my Saitek x52 ceased all input after install of DCS World + A-10 add on. I tried un/repluging and reloading my profile, but no button input got to the OS, let alone the game. I rebooted and it went back to normal.

[rogueone]

TM HOTAS

 

:)

I just connected a TM T.Flight HOTAS X to a clean install of DCS World and assigned button 9 as a modifier. This is what the modifiers.lua looks like:

 

NOTE: Red text is the line that was added by the change. The rest is all default.

 

Cichilidfan,

I reviewed your HOTAS Notepad ++ file and it looks like exactly what I need, the problemis "ME"...have been retired from LOckheed-Martin for over 20 years and only recently got back in...I wonder if I could impose on you to write me a short step by step procedure for updating and installing changes to my HOTAS file.

 

Thanks from an "old" pilot

 

rogueone:)

[cichlidfan]

I can do that but it won't be until later tonight. You might have a look at the attached in the meantime.

 

It is the relevant pages extracted from the DCS A-10 GUI manual.

Control Assignment Pages from DCS A-10C GUI Manual EN.pdf

[rogueone]

Thanks for your reply...with this info I think I can work it out.

 

Rogueone