Joystick input lag (FFB related?)

[Turkey]

I guess it is a DCS core related issue. I experienced very same problem on F-14B and MiG-15Bis, but any other aircraft works fine.

[Vertigo72]

Turkey, could you try the vjoy trick, and see if that also solves it for you?

[MAD-MM]

Have now same issue since last Patches for the Tomcat 2 Months ago probably, same thing with the MIG-15 since release..

Currently the only two Planes with that lagg Issue...have two FFB Sidewinder Sticks, both the same...

[martinistripes]

I've also experienced significant input lag in the Tomcat. Specifically in the guns and sidewinder tutorial. At times I pulled the trigger whilst my pipper was on the target and the rounds came out a second or two later causing me to miss. Also noticed it with roll and pitch input. My DCS install was recently cleaned and repaired after a fresh OS install. I do have VR Performance Mod now, but that's all. Haven't noticed lag with other modules. I don't have the MiG-21 so can't comment there.

[ViFF]

I am having the exact same issues with my MS SW FF2.

 

Its subtle and not easily noticeable, but there is definitely intermittent input latency of axis movements (its like small freezes in stick movement) and its visible on both the 3d stick in the cockpit and also on the controls indicator mini window.

 

The only thing I have to add to this discussion is that the the intermittent input latency in axis movements is more frequent and noticeable when mirrors are turned off (higher in game fps).

 

I will try the various recommendations here regarding vsync and changing usb ports.

 

Edit: I started experiencing this problem in one of the updates in June.

 

Cheers!

Edited August 4, 2020 by ViFF

[martinistripes]

Just to add. I was flying in 2D just now and using the NUMPAD to look around. Several times, I pressed a NUMPAD key (for example to look left) and there was lagged response. A few times, I held the key because there was no immediate response, then it would catch up and overshoot. Not sure how or even if this is joystick related now.

[fat creason]

This seems like a DCS input problem that happens rarely or is somehow related to user's hardware configuration. I've never seen it on my MS FFB2.

[bpremus]

I have noticed a few days ago an input lag on F14. Pressing esc to open a menu or moving a joystick has 1 to 2 sec delay.

With MS FFB2 on a flat screen only. Turning off FF in menu resolve input lag), also not reproducible on other airplanes.

In VR works normally

 

[-0303-]

Same problem UH-1H & other modules. Nothing to do with FFB since I don't have one. Fast logged response suggests not USB or stick hardware problem either (my tests, scroll down).

Question to 3rd party developers. Ping fat creason. Do you (or DCS) model "realism delay" and could this be a reason? In Bf 109 the pilot couldn't wrestle full deflection at high speeds. The F-86 has no direct stick to surfaces connection, they're moved hydraulically at whatever pace. A simulated "realism delay" wouldn't be improper. But regardless, the delay seen on ground in Spitfire, Bf 109, I-16, P-51, UH-1H etc is wrong. I know I can slam the stick to the side instantly in a real life small plane (glider). It doesn't take  close to a second.

Question:

• Is it the 3rd party developer that implements a "realism delay" (if that's a thing) or is it DCS? If 3rd party develops the flight model doesn't "realism delay" belong to the 3rd party developer?
• Could this just be delayed animation regardless if a "realism delay" is implemented or not?

My tests:

Thustmaster (TM) Warthog joystick, throttle and MFG Crosswinds pedals. IR head tracking. No FFB stick.

• Instant movement in TM Device Analyzer but stick animation and controls indication delayed.
•  Tried connecting only the joystick to USB (1 device instead of 4), no difference.
•  No difference running the CPU at 1.2GHz or 2.4GHz.
•  No difference springless FFB stick mode or default (the UH-1H "special" setting).

TM Device Analyzer logfile (five attempts):

226 ms
186 ms
173 ms
147 ms
203 ms

ie how fast I could move the stick full throw left (X = 32768 -> 0).
Example 16 datapoints 147 ms (X, HH:MM:SS:sss):

X,32696,11:50:07.721
X,31876,11:50:07.731
X,30672,11:50:07.740
X,29148,11:50:07.749
X,27442,11:50:07.759
X,25540,11:50:07.768
X,23354,11:50:07.779
X,20894,11:50:07.788
X,18244,11:50:07.798
X,14864,11:50:07.809
X,11948,11:50:07.820
X,9150,11:50:07.828
X,6590,11:50:07.838
X,3928,11:50:07.848
X,1948,11:50:07.856
X,0,11:50:07.868

Edited May 15 by -0303-