Jump to content

Recommended Posts

Posted

I've read that sever people have also had issues with Logitech Gaming Keyboards, specifically that assigning key-presses to the G-Keys doesn't work.

 

For example I program the lower set of 6 G-Keys for adjusting trim:

 

G-Keys:

<G13> - <G14> - <G15> -

<G16> - <G17> - <G18> -

 

Programmed key-presses:

<RCtrl><z> - <RCtrl><:> - <RCtrl><x>

<RCtrl><,> - <RCtrl><.> - <RCtrl></>

 

However, in game DCS doesn't seem to recognize any key-presses, for example when I try to use <G13> and <G15> to adjust rudder trim.

 

If I go into DCS Keyboard setting and try to use the G-Keys to set a function, for example 'Trim Rudder Left' and press <G13>, settings recognizes <RCtrl>, but not the <z>.

 

I've read the suggestion to program macros for this. The issue with that is that each pressing of a G-Key then translates to pressing for example <RCtrl><z> for an exact number of milliseconds and then releasing, which is really bad for adjusting trim.

 

If you theoretically press <RCtrl><z> through pressing <G13> programmed for 1/4sec each press causes only a very small adjustment. If you press multiple times, the keystrokes of course will not be quicker, plus they will buffer if you press quicker than 1/4sec when you stop pressing, the buffered key-presses will continue coming.

 

I'd like the G-Keys to work like they should, translating to a key-press for exactly as long as I press the G-Key and not a programmed length of time.

 

Does anybody know a solution?

 

Many t(h)anks in advance.

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

Had issues with the logitech G keys and dcs a while ago.

I ended up with changing the DCS key commands, so that the commands I wanted on the G keys, did not use any modifiers.

 

So if the command I wanted on the G key was "Ctrl + z", then I would change that to just be "z".

 

This is the only thing that worked reliably for me. To bad if this still doesn't work as it should.

Runi. "IceCat"

Printable A5 F/A-18C Checklist

Win 10 Pro 64bit, ASUS Maximus XI Hero, Intel Core I7 9700K @4.7 - 4.9 GHz,

Nvidia Asus GeForce GTX 1080TI 11Gb, G.Skill TridentZ RGB DDR4-3200 C16 DC - 32GB (2x(2x8Gb)), Samsung 870 NVME + Multiple Samsung 850 & 860 EVO SSDs, Dell P2414H & U2414H Monitors.

Posted

Thanks runibl, that is probably what I'll wind up doing.

 

I don't even know if the issue is with DCS or Logitech, and beyond 'workarounds' I've never heard anybody actually even try to find out what the actual issue is.

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...