Jump to content

Recommended Posts

Posted (edited)

I am suffering from this bug ever since I got my Reverb G2. I launch DCS from within the WMR Cliffhouse and normally everything works fine. However, when I join a certain multiplayer server or a mission reloads, there is a chance that I will lose my keyboard. Only Num5 (VR center) and Alt-Tab keys still work. Mouse and joystick also still work. But nothing else, including keystrokes generated by Thrustmaster TARGET. I can't use Esc or Alt-F4 to exit DCS, so I must close it from the taskbar (and confirm with mouse). I don't think this ever happened in SP missions or when I was flying with Oculus Rift before.  

 

Edit: Windows and other programs still work fine. DCS definitely has focus. I tried Win-Y to no avail. Repaired/updated multiple times. Latest Open Beta.

 

I attached my logs if someone could have a look. Thanks!

dcs.log

Edited by impalor

12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR

Posted

Sorry I have no help but can relate. I had issues with keyboard not responding in one particular MP server, couldn’t figure it out and then it stopped. Sorry for no help, but wanted to chime in that you’re not alone with experiencing this at some point.  

Twitch Channel

 

[sIGPIC][/sIGPIC]

Virtual Thunderbirds, LLC | Sponsored by Thrustmaster

 

Z390 Aorus Xtreme, i9 9900k, G.SKILL TridentZ Series 32GB, 1080ti 11GB, Obutto R3Volution, Thrustmaster HOTAS Warthog, TPR, Cougar MFDs, FSSB R3L, JetSeat, Oculus Rift S, Buddy-Fox A-10C UFC, F/A-18C UFC, Tek Creations F-16 ICP

 

  • 2 weeks later...
Posted

Well, today it happened three times in a row on the same mission as a month ago (in my TAW squad 'mandatory'). I can send that mission file to @BIGNEWY in PM and I attached fresh logs. The mission used Moose scripts. The only other server I remember having this problem does not use Moose, but still uses some custom LUA scripts.

 

Just an idea about possible cause: I generate lots of keystrokes with Thrustmaster TARGET, with modifiers including RWIN. Maybe it gets 'stuck' logically in DCS? I do not have RWIN on my physical keyboard, so I cannot 'unstuck' it. Other people at TAW are not having my problem. I can fly all other servers and SP missions. 

 

I will keep bumping this thread until Devs look into it. My goal is to fly competitively and this bug is thwarting this. ((

Logs.rar

12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR

Posted (edited)

I've had problems, though not a bad as yours, as I had lots of key bindings mapped to HOTAS switches via Joystick Gremlin. This caused some funny things to happen - like self deploying airbrakes. This problem seems to have disappeared/lessened when I reduced the number of "keyboard" entries generated by the HOTAS. I suspect that there is some sort of keyboard buffer which can get confused and swap keystrokes. Try mapping more things directly in DCS rather than via third party software and see if that helps.

BTW Also G2 but Virpil and Joystick Gremlin

Edited by SQINTO
Posted

I had this problem on some modules.

During key binding I used the command delet all setings.

This delets also your keyboard bindings and ingame you are not able to get into the menue,

 

So can only solve this in the game menue by resetting the keyboard bindings in the concerned module.

i7-8700K / 32GB RAM @3000 / 1TB M.2 SSD / Asus RTX 2080 Ti OC

VR- Gamer: Valve Index

Flight Gear: Thrustmaster HOTAS Warthog / Thrustmaster TPR / 3x Thrustmaster MFD / Jetseat

[sIGPIC][/sIGPIC]

Posted

I am not losing keyboard bindings or having problems with every mission. Only TWO particular MP missions WITH LUA SCRIPTS consistently make my DCS unresponsive to keyboards (virtual or physical). I have only one TARGET profile and I modify key bindings in DCS for each module to work with it. For many many years this worked very well, and I am not sure it is TARGET's fault. I the last such case, after full PC reboot and joining the troubled MP mission, all it took is to autostart an F18 and the keyboard was gone! I doubt the buffer was overflown by that single keystroke.

12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR

Posted (edited)

Another and more often occuring problem in MP is that I lose only comms menu functionality. Yesterday after 30 minutes into the mission I could no longer rearm etc. F menu would not come up at all, and using Vaicom took 10-15 minutes of waiting (twice on different airfields), but worked eventually. Some people in my squad confirmed they also lose comms menu sometimes on servers. I'd really really like to understand what is causing this! @BIGNEWY

Edited by impalor
  • Like 1

12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR

Posted
5 hours ago, BIGNEWY said:

I have not experienced this, are you using unofficial mods?

Yes, 3Dmigoto VR mod, because without it spotting is very hard in VR. It's a shader mod, I doubt it affects comms menu but I can try without it. More suspect is Vaicom, because it directly integrates with comms. But it is an official mod?

12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR

Posted
Another and more often occuring problem in MP is that I lose only comms menu functionality. Yesterday after 30 minutes into the mission I could no longer rearm etc. F menu would not come up at all, and using Vaicom took 10-15 minutes of waiting (twice on different airfields), but worked eventually. Some people in my squad confirmed they also lose comms menu sometimes on servers. I'd really really like to understand what is causing this! @BIGNEWY
Sometimes it seems VAICOM gets a delay with the ordinary comms. Cycling the keyboard shortcut for the comms, sometimes triggers it. Haven't had issues in MP though.
When you have trouble, may I suggest the "options" and "take x" commands?
Cheers!

Sent from my MAR-LX1A using Tapatalk

Posted

"options" also did not work. now trying to not use Vaicom for some time, to see if it helps

12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR

Posted

I've had similar, but not exactly the same problem. Right after updating to 2.7, I had trouble with MP chat window. I had a hard time hiding as well as displaying the window. And I cannot type anything in the chat box many times. Anyway, my keyboard wasn't working properly in other scenarios either, but I can't put my finger on it.

I think after reinstalling VoiceAttack, things are back to normal. I don't know why.

  • Recently Browsing   0 members

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