yinlad

Just to confirm (never did update this), my bluetooth keyboard going into sleep was 100% the cause of this for me.

One thing that had me over was in Options -> Misc, Force Feedback was checked. Unchecking that made my trim actually work

The issue I'm having with the trim is that even with the correct 'special' options, only my rudder "holds" once set. Watching the control trace I can see the red cross set for both cyclic and anti torque, but after releasing the controls the white diamond for cyclic goes straight back to dead centre away from the trim set position, while rudder is locked to to the red cross the force trim set. Any idea on what might be causing it?

Prices updated + Track IR now sold

Hey all, looking at offloading some sim gear I bought early this year but now don't have the time to use! I'm looking at selling the following, happy to ship within the UK and EU, but will need to discus shipping costs with buyer outside of UK. The Virpil stuff was bought in Jan of this year and probably has 50 hours of flight time on them. The desktop mounting plate, cams and springs will be included, they aren't pictured but are in the box. The Track IR bought new in Feb from RCSimulations in the UK. The TWCS throttle was bought used in Jan and I have since fitted a bearing sled mod for smoother operation. I will include the original sled, if for some reason you wanted to change it back. For Sale: Virpil WarBRD - £200 Virpil Constellation ALPHA-R - £200 TWCS Throttle - £100 Track IR with pro clip (and basic hat clip) - £170 shipped DM me if there's any further details you want to discuss etc. Cheers guys.

I've mentioned my wireless keyboard going to sleep to a few people now and I've had positive responses from people saying that devices going to sleep causes havoc in DCS. So I'm pretty sure that is what was causing my issue. I'll update the thread later tonight after more testing though.

Ok potentially found the issue. I think the small wireless keyboard I use enters a sleep mode if inactive for a while, at which point that interferes with DCS somehow blocking the inputs from the HOTAS buttons Will have to test more thoroughly later today but when I encountered the issue in flight I turned off the keyboard and I regained button inputs again so seems promising

Yeah it's the last thing on my list to try, which I will do today. But I don't see why A) Going into the menu and back into game would fix the issue (even if only for a few minutes) if it were a hardware issue. B) Why the game would continue to accept Axis inputs from the throttle and stick if it were a hardware issue.

So I created a thread in the F-16 forum thinking it was specific to that airframe but further tested has proved that to be false. I'm new to DCS and this issue has persisted for me since my first installation. The crux of the issue is at a seemingly random points in game, DCS stops registering button inputs from the HOTAS. Hitting ESC twice to open and close the menu temporarily fixes the problem, until it occurs again and I have to repeat the work around. I can go an entire session without it happening, but then sometimes it's every few minutes. It's not until I go to slew the radar, release a missile etc. that I know it has happened because nothing happens. During this time DCS is still responding to Axis inputs from the HOTAS so it's not as if the window has lost all focus as I suspected might be the case. I'm running a Virpil warbrd stick with a TWCS throttle, 2 monitors, 1 running DCS and the other just for general use. I'm running DCS via Steam. I have several other USB input devices plugged in, but disabled in the DCS settings. - I have tried disconnecting the second monitor with no success. - I have tried putting the no hot plug fix into autoexec.cfg with no success. - I have tried running in full screen mode with no success. - I have tried running DCS directly from the .exe, even with admin permissions, with no success. The last thing I can think of trying is to unplug all of my other USB input devices. Though they are disabled within the DCS settings anyway so they really shouldn't be making a difference whether they are plugged in or not. I've attached the log file from my latest test where it occurred and there doesn't seem to be any obvious indication of an error causing this etc. This is a game breaking issue for me as I am pretty much unable to do anything in game when all the buttons on the HOTAS suddenly don't work anymore. And having a keyboard on hand to enter and exit the menu potentially every 2 minutes while in combat is hardly a viable workaround for me. dcs.log

just confirmed its in the F15 too, so not a F16 specific bug

Ive always had it in the f16. Don't recall getting it in the fc3 F15 when I ran that a bit before the f16 but ill go back and do a few f15 missions to test. And Im not running the easy mode f16, no

ah no dice it has just happened to me again

initial test is promising. Ill update after a few more hours of flight today

thanks for the replies, I tried with discord closed anyway and still got it. But checked and had no bindings in settings. about to try the autoexec now

Not had any luck resolving this on my side but for some more context, I'm running DCS on my primary monitor, with secondary monitor displaying discord etc... During flight DCS just stops responding to all button presses from input devices that aren't mouse and keyboard. I thought it may be other programs pulling the focus from DCS but this still happens when DCS is the only program I have actively running on the PC. This happened before and after I started using Track IR and happens seemingly at random, but at least once every few minutes, forcing me to double tap escape with the keyboard to regain input presses from the HOTAS. As you can imagine when this happens during combat it's sub optimal to say the least. Wondering why missiles wont fire or uncage before realizing it's the bug and I need to reach for the keyboard etc.etc. I've yet to test in another airframe but will do that today to see if it's F16 specific or DCS in general