Jump to content

Recommended Posts

Posted

According to this thread:

http://forums.eagle.ru/showthread.php?t=123212

 

I have a problem assigning the 3-way switches of the HOTAS Warthog to any function in the configs, being precise the middle stage of those switches.

 

I wanted to ask in this subforum if any of you has the same issue or if the problem is on my side?

 

The thing is with the old config format DCS was smart enough to assign the middle stage of a switch to the corresponding game switch if I assigned the UP and DOWN stage to that switch. No it does'nt and I have ~9 switches 3-way switches left as 2-way switches which is pretty annoying because the P-51D has many 3-way switches...

Posted

I've found using the Thrustmaster software to be very quick and I've had no problems. Once you figure out the differences in pulse, hold, etc you can program and reprogram it pretty quickly.

Posted

The workaround in the lua files as recommended is pretty easy to do and definitely works. Helps to use the find function under the edit tab to locate the correct joy button amongst all the lines of text. Worth the effort and you get to add a new skill to your list of computer abilities acquired whilst playing flight sims! :thumbup:

Posted
... Worth the effort and you get to add a new skill to your list of computer abilities acquired whilst playing flight sims! :thumbup:

 

Something I could do without :(

Windows 10 64bit, Intel i9-9900@5Ghz, 32 Gig RAM, MSI RTX 3080 TI, 2 TB SSD, 43" 2160p@1440p monitor.

Posted

It really seems to be pretty easy and straight forward... just pretty annoying to substitute the default.lua after every update again with the special commands to enable correct 2-way and 3-way buttons for TM HOTAS...

 

Here are my working extra custom lines to the default.lua:

 

--Custom

{down = device_commands.Button_7, up = device_commands.Button_7, cockpit_device_id = devices.FRONT_SWITCH_BOX, value_down = 1.0, value_up = 0.0, name = 'Alternate Gun safety switch GUN CAMERA SIGHT', category = 'Front Switch Box'},

{down = device_commands.Button_2, up = device_commands.Button_2, cockpit_device_id = devices.FRONT_SWITCH_BOX, value_down = 0.3, value_up = 0.0, name = 'Alternate Ignition switch BOTH', category = 'Front Switch Box'},

{down = device_commands.Button_11, up = device_commands.Button_11, cockpit_device_id = devices.FRONT_SWITCH_BOX, value_down = 0.1, value_up = 0.0, name = 'Alternate Bomb-rocket selector switch TRAIN', category = 'Front Switch Box'},

{down = device_commands.Button_11, up = device_commands.Button_11, cockpit_device_id = devices.FRONT_SWITCH_BOX, value_down = 0.3, value_up = 0.0, name = 'Alternate Bomb-rocket selector switch ROCKETS', category = 'Front Switch Box'},

 

{down = device_commands.Button_11, up = device_commands.Button_11, cockpit_device_id = devices.ENGINE_SYSTEM, value_down = 0.0, value_up = 0.1, name = 'Alternate Mixture IDLE CUT OFF', category = 'Flight Control'},

{down = device_commands.Button_11, up = device_commands.Button_11, cockpit_device_id = devices.ENGINE_SYSTEM, value_down = 0.2, value_up = 0.1, name = 'Alternate Mixture EMERGENCY FULL RICH', category = 'Flight Control'},

 

{down = device_commands.Button_8, up = device_commands.Button_8, cockpit_device_id = devices.K14_GUNSIGHT, value_down = 1.0, value_up = 1.0, name = 'Alternate Gunsight gyromotor power', category = 'K-14 gunsight'},

{down = device_commands.Button_3, up = device_commands.Button_3, cockpit_device_id = devices.K14_GUNSIGHT, value_down = 0.0, value_up = 0.1, name = 'Alternate Gunsight mode FIXED', category = 'K-14 gunsight'},

{down = device_commands.Button_3, up = device_commands.Button_3, cockpit_device_id = devices.K14_GUNSIGHT, value_down = 0.2, value_up = 0.1, name = 'Alternate Gunsight mode GYRO', category = 'K-14 gunsight'},

 

{down = device_commands.Button_6, up = device_commands.Button_6, cockpit_device_id = devices.ENGINE_CONTROL_PANEL, value_down = 1.0, value_up = 1.0, name = 'Alternate Fuel Booster', category = 'Engine Control Panel'},

 

{down = device_commands.Button_3, up = device_commands.Button_3, cockpit_device_id = devices.FUEL_SYSTEM, value_down = 1.0, value_up = 1.0, name = 'Alternate Fuel shut-off valve', category = 'Fuel Control'},

 

Needed for that profile:

p51d_-_hotas_diagram.jpg

  • 1 year later...
Posted

From the graphic in the previous post it's apparent that a number of buttons and switches are using key-modifiers. But it seams that the only modifiers DCS recognizes are a keyboard's standard meta-keys (Alt, Ctrl, etc.).

 

Is my assumption correct?

 

Is there any way to use a Throttle or Joystick button as a modifier, for example the Master Mode Control Button the the stick?

When you hit the wrong button on take-off

hwl7xqL.gif

System Specs.

Spoiler
System board: MSI X670E ACE Memory: 64GB DDR5-6000 G.Skill Ripjaw System disk: Crucial P5 M.2 2TB
CPU: AMD Ryzen 7 7800X3D PSU: Corsair HX1200 PSU Monitor: ASUS MG279Q, 27"
CPU cooling: Noctua NH-D15S Graphics card: MSI RTX 3090Ti SuprimX VR: Oculus Rift CV1
 
Posted
From the graphic in the previous post it's apparent that a number of buttons and switches are using key-modifiers. But it seams that the only modifiers DCS recognizes are a keyboard's standard meta-keys (Alt, Ctrl, etc.).

 

Is my assumption correct?

 

Is there any way to use a Throttle or Joystick button as a modifier, for example the Master Mode Control Button the the stick?

 

 

Hi,

 

 

Pic 1 - in game profile

Should be possible for every joystick/throttle button that is recognized and listed

 

 

Pic 2 - profile in combination with a joystick-software

It`s possible with the X52 - Saitek - Profileditor

Pinkie - standard modifier

Clutch as second modifier

Posted

Thanks Blech! :thumbup: I never realized that I could create my own Modifier buttons :doh:. That's exactly what I was looking for.

 

PS I hope you forum name isn't Germany :huh:

When you hit the wrong button on take-off

hwl7xqL.gif

System Specs.

Spoiler
System board: MSI X670E ACE Memory: 64GB DDR5-6000 G.Skill Ripjaw System disk: Crucial P5 M.2 2TB
CPU: AMD Ryzen 7 7800X3D PSU: Corsair HX1200 PSU Monitor: ASUS MG279Q, 27"
CPU cooling: Noctua NH-D15S Graphics card: MSI RTX 3090Ti SuprimX VR: Oculus Rift CV1
 
Posted

You mean the "Pinky Lever"? LOL that's what I decided on too :D

When you hit the wrong button on take-off

hwl7xqL.gif

System Specs.

Spoiler
System board: MSI X670E ACE Memory: 64GB DDR5-6000 G.Skill Ripjaw System disk: Crucial P5 M.2 2TB
CPU: AMD Ryzen 7 7800X3D PSU: Corsair HX1200 PSU Monitor: ASUS MG279Q, 27"
CPU cooling: Noctua NH-D15S Graphics card: MSI RTX 3090Ti SuprimX VR: Oculus Rift CV1
 
  • 2 weeks later...
Posted

I seem to be working my way from one rats-a-frats to the next :cry:.

 

So I've got my default.lua set up pretty much the way I need it and assigned the switches to the functions I want. In general everything seems to be working great :thumbup:.

 

.... except for when I start a mission with the motor already started and in-sim switches suddenly go off when I click the Fly button huh.gif.

 

These are the switches on the Throttle-unit involved:

 

EAC OFF (down): K-14 Gyro Motor: OFF

EAC ARM (up): K-14 Gyro Motor: ON

APU OFF (down): Fuel Shut Off: OFF

APU START (up): Fuel Shut Off: ON

ENG OPER L - MOTOR (down): IGNITION OFF / PRIMER OFF

ENG OPER L - NORM (middle): IGNITION BOTH / PRIMER OFF

ENG OPER L - IGN (up*): IGNITION BOTH / PRIMER ON

ENG OPER R - MOTOR (down): FUEL BOOSTER OFF / STARTER OFF

ENG OPER R - NORM (middle): FUEL BOOSTER ON / STARTER OFF

ENG OPER R - IGN (up*): FUEL BOOSTER ON / STARTER ON

* springs back to middle

ENG FUEL FLOW L - OVERRIDE (down): GEN DISC.

ENG FUEL FLOW L - NORM (up): GEN ON

ENG FUEL FLOW R - OVERRIDE (down): BAT DISC.

ENG FUEL FLOW R - NORM (up): BAT ON

FLAPS DN (down): IDLE CUTOFF

FLAPS MVR (middle): RUN

FLAPS UP (up): EMERG F RICH

 

 

So just before I click the "Fly" button, I adjust Prop and Throttle, and turn to ON: GEN, BAT, FUEL BOOSTER, IGNITION BOTH, FUEL SHUT OFF, and Mixture Control to RUN.

 

Then I click "Fly" and in-sim the throttle is full-forward until I move it a little, and GEN, BAT, and FUEL SHUT OFF all go to OFF/DISC. The switches which are in the correct positions are Mixture Control: RUN, IGNITION BOTH and FUEL BOOSTER ON.

 

If I leave all switches in their down positions--everything turned off--and click "Fly" then the throttle is still on full, and Mixture Control changes to IDLE CUTOFF.

 

So the FLAPS switch is recognized in all positions at "Fly", but the throttle is always full forward and the dual-position switched do not have their states recognized.

 

Does anybody else have these issues?

When you hit the wrong button on take-off

hwl7xqL.gif

System Specs.

Spoiler
System board: MSI X670E ACE Memory: 64GB DDR5-6000 G.Skill Ripjaw System disk: Crucial P5 M.2 2TB
CPU: AMD Ryzen 7 7800X3D PSU: Corsair HX1200 PSU Monitor: ASUS MG279Q, 27"
CPU cooling: Noctua NH-D15S Graphics card: MSI RTX 3090Ti SuprimX VR: Oculus Rift CV1
 
Posted (edited)

Thanks Zabuza, that kind of works :). It also means that the option kind of doesn't :huh:.

Edited by Captain Orso
mis-spelling

When you hit the wrong button on take-off

hwl7xqL.gif

System Specs.

Spoiler
System board: MSI X670E ACE Memory: 64GB DDR5-6000 G.Skill Ripjaw System disk: Crucial P5 M.2 2TB
CPU: AMD Ryzen 7 7800X3D PSU: Corsair HX1200 PSU Monitor: ASUS MG279Q, 27"
CPU cooling: Noctua NH-D15S Graphics card: MSI RTX 3090Ti SuprimX VR: Oculus Rift CV1
 
  • Recently Browsing   0 members

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