Jump to content

Recommended Posts

Posted

Hey folks,

 

I already searched the forum but haven't found this problem (maybe i'm too stupid) so far and i'm not sure if this is Hornet related. But i've only experienced it with the Hornet (Viper and FC3 is fine) so i put this here.

 

My problem is, as soon as i touch down on an airfield, i loose control of my keyboard and stick mappings. The axis are still working, just the buttons and the keyboard is gone. Only way to get them back is switching to Win by ALT+Tab and then back to DCS and voilá, got full control again.

 

The weird thing is, it's not always the case, i'd say 8 out of 10 landings. And only airfields, carrier is good as well. Also this started to happen after i began to use the TARGET GUI instead of DCS mappings.

 

Rolling back to DCS mappings is not an option, since the TARGET GUI provides way more mapping options (f.e. Master Arm ON/OFF on one switch) and i don't wanna miss that. I got used to it a bit, but since i crashed into another player waiting on the cross taxiway because of that, i thought this should be solved..

 

Does anyone experienced that as well, or knows how to solve this annoying issue?

 

cheers

 

VpR

Phanteks EvolvX / Win 11 / i9 12900K / MSI Z690 Carbon / MSI Suprim RTX 3090 / 64GB G.Skill Trident Z  DDR5-6000 / 1TB PCIe 4.0 NVMe SSD / 2TB PCIe 3.0 NVMe SSD / 2TB SATA SSD / 1TB SATA SSD / Alphacool Eisbaer Aurora Pro 360 / beQuiet StraightPower 1200W

RSEAT S1 / VPC T50 CM2 + 300mm extension + Realsimulator F18 CGRH / VPC WarBRD + TM Warthog grip / WinWing F/A-18 Super Taurus + F-15EX / 4x TM Cougar MFD / Slaw Device RX Viper V3 / HP Reverb G2

Posted

That's a weird one! Is the phenomenon triggered by touch-down (weight on wheels) or by a command you use just after touch-down?

The standard recommendation with such a strange issue is "run repair!" Have you tried that?

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Posted

Yeah, absolutely weird. Hmmm, that's a good question... literally there are only 2-3 commands i use after airfield touch down: wheel brake, rudder/NWS and, depending on runway length, sometimes speed brake. i was sure it's triggered by weight on wheels, but now that you ask it might be related to one of these commands, since i don't use these with carrier landings and it never happens there.

 

I'm a bit in a hurry now, but i will try to reproduce (resp. try w/o any commands) the issue later, run a installation repair and will then report the result.

 

For now, thank you very much for the reply

 

cheers

Phanteks EvolvX / Win 11 / i9 12900K / MSI Z690 Carbon / MSI Suprim RTX 3090 / 64GB G.Skill Trident Z  DDR5-6000 / 1TB PCIe 4.0 NVMe SSD / 2TB PCIe 3.0 NVMe SSD / 2TB SATA SSD / 1TB SATA SSD / Alphacool Eisbaer Aurora Pro 360 / beQuiet StraightPower 1200W

RSEAT S1 / VPC T50 CM2 + 300mm extension + Realsimulator F18 CGRH / VPC WarBRD + TM Warthog grip / WinWing F/A-18 Super Taurus + F-15EX / 4x TM Cougar MFD / Slaw Device RX Viper V3 / HP Reverb G2

Posted (edited)

Too many simultaneous inputs maybe?

 

Some input device are not very good at buffering, or playing well with others...

 

Example: In the mustang when temps are an issue I use LALT+A and LALT+S on my very cheap keyboard, to open flaps on the oil cooler and radiator. If I'm holding both at the same time (they must be held for several seconds to fully open), the trim inputs from the 4 way switch on my CH Combat stick are ignored until I stop holding down those keys on the keyboard.

 

I don't use target so I don't know how it drives inputs.

Edited by Paganus
typo
Posted (edited)

Hi and sorry for the late answer, but social life keeps me very busy these days.

 

So i tried to reproduce the issue and what i found out is, that it's somehow related to holding down the speed brake button in combination with weight on wheels. The pedals have nothing to do with it. I doubt it to be a fault with too many input signals at one time, since only the spd brake triggers it. Holding down other buttons has no negative effect. Strange is, that it only occures with weight on wheels. In flight i was unable to reproduce it. I found out that i can also solve the problem by only releasing the speed brake button. Same effect as if i keep holding down the spd brake button and switch to win and back to dcs. I'll run a installation repair as LeCuvier recommended and see if that helps. If not, i guess i have to live with it and/or avoid the spd brake during landings. Not the best solution, but at least i know what to do instead of pressing ALT+Tab.

 

Thanks a lot for your help guys,

 

cheers

Edited by VpR81

Phanteks EvolvX / Win 11 / i9 12900K / MSI Z690 Carbon / MSI Suprim RTX 3090 / 64GB G.Skill Trident Z  DDR5-6000 / 1TB PCIe 4.0 NVMe SSD / 2TB PCIe 3.0 NVMe SSD / 2TB SATA SSD / 1TB SATA SSD / Alphacool Eisbaer Aurora Pro 360 / beQuiet StraightPower 1200W

RSEAT S1 / VPC T50 CM2 + 300mm extension + Realsimulator F18 CGRH / VPC WarBRD + TM Warthog grip / WinWing F/A-18 Super Taurus + F-15EX / 4x TM Cougar MFD / Slaw Device RX Viper V3 / HP Reverb G2

  • Recently Browsing   0 members

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