Input lag

[Mandoble]

Playing in singleplayer mode, FPS going from 150 to 60. In many cases clicking the trigger (single shot) results into nothing, in some others pressing the trigger results into a delay of up to 1 second for the first shot and then a noticeable degradation in the rate of fire (substained), not only in the time between tracers, but also in the time between shot sounds, control response seems to be affected as well. This happens frequently (almost all the time) in the middle of dense combats, very rarely in 1 vs 1 situations. When this happens I can perceive that the graphics are not very fluid, but checking FPS I still see 80, 90, 100, while the visual perception is more similar to 30 fps.

 

i7 16GB RTX2060 6GB (latest drivers), game running on SSD (520 MB/s).

[-DED-Rapidus]

@Mandoble, try resetting the video driver settings to the default settings, see what your power scheme is in the system settings - maybe power-saving mode set in the settings?

[Mandoble]

4 hours ago, -DED-Rapidus said:

@Mandoble, try resetting the video driver settings to the default settings, see what your power scheme is in the system settings - maybe power-saving mode set in the settings?

Of course no power saving mode, quite the opposite. I suspect it has no relation at all with the video driver but with how the game works internally, when the game reads the inputs and when the game executes them. It is totally missing joystick trigger clicks. It never happened to me before in any game, and currently it happens only in this one.

[Monksilver]

I'm getting a similar issue since last update. First in 109-F2 in Moscow career (I thought might be a quirk of the F2 as only just started with it) and now Tempest on BOBP career. Usually fine but every now and then when I pull the trigger I get an unexpected result being a) nothing, b) a single bullet then nothing or c) several bullets then nothing, I then have to release trigger and pull again to resume normal service but I usually lose at least 1second before bullets come back. Each time I have ammo and usually no damage to my plane.

 

Not connected to any frame rate issue as my monitor limits me to 60fps anyway. NO problem with other flight controls so far as I've noticed.

[-DED-Rapidus]

@Monksilver, @Mandoble, ok, I'm interested in the game launch mode (full screen or windowed mode), which input devices, and what else works in the background from apps.

If there is an accompanying video it will be even better for the report.

[Mandoble]

7 hours ago, -DED-Rapidus said:

@Monksilver, @Mandoble, ok, I'm interested in the game launch mode (full screen or windowed mode), which input devices, and what else works in the background from apps.

If there is an accompanying video it will be even better for the report.

Fullscreen 1080P, Thrustmaster T16000M+TWCS+Pedals. As said before, it doesn't happen with any other similar game where the inputs are always immediately read and executed (DCS, MS FS, Elite Dangerous, ...), I tested also with MS Windows joystick tool, which reads the inputs immediately as well, not a single miss, not a single delay. In the background I have the default Windows 10 processes, normally Steam is running as well while IL2 is not the Steam one.

 

I've found this issue is not new, check here.

 

EDIT: I've found that setting a target FPS number in something different than deactivated increases the problem even more. You asked for a video as well, but in a video you would never "see" when I'm pulling the trigger, moving the joystick, pedals, etc.

 

While setting the target FPS to a number makes the problem even worse, I suspect it is mostly a CPU related issue as it happens in situations with dense mix of units fighting while not necessarily drawn on the screen (I have the career options set to "Hard" and "Dense"), perhaps most people with the career not set to Dense would never notice the effect and I guess the effect in MP is gone if the CPU is not loaded handling many AI units. Remember as well that not only the input is affected, also the rate of fire and the "delays" of the gun's sounds when substaining the fire. This effect is present with FPS above 60, so it looks the input is not read synchronized with frames drawn, it "seems" like instead of reading the input buffer the game is reading the input states at a particular time and missing what happened between previous state read and last state read, but reading the states in a frequency way lower than the frames drawn per second.

 

 

Edited September 25, 2020 by Mandoble

[Monksilver]

16 hours ago, -DED-Rapidus said:

@Monksilver, @Mandoble, ok, I'm interested in the game launch mode (full screen or windowed mode), which input devices, and what else works in the background from apps.

If there is an accompanying video it will be even better for the report.

Full screen

TM16000M, keyboard and mouse

normally nothing else is open but sometimes internet page (actually this site). I have just done  a couple of missions in career one with this page open and one without and no problems at all. But I had first gone into task manager and shut down some background apps eg Microsoft Teams and a VPN that is for work but although closed was showing up in task manager but none of it taking up much of the CPU, but I do wonder if that was the issue. I will keep an eye on it and let you know if it happens again - or if I stay trouble free with keeping on top of this background stuff.

[Monksilver]

On 9/25/2020 at 3:23 AM, -DED-Rapidus said:

@Monksilver, @Mandoble, ok, I'm interested in the game launch mode (full screen or windowed mode), which input devices, and what else works in the background from apps.

If there is an accompanying video it will be even better for the report.

 

On 9/25/2020 at 8:29 PM, Monksilver said:

Full screen

TM16000M, keyboard and mouse

normally nothing else is open but sometimes internet page (actually this site). I have just done  a couple of missions in career one with this page open and one without and no problems at all. But I had first gone into task manager and shut down some background apps eg Microsoft Teams and a VPN that is for work but although closed was showing up in task manager but none of it taking up much of the CPU, but I do wonder if that was the issue. I will keep an eye on it and let you know if it happens again - or if I stay trouble free with keeping on top of this background stuff.

 

Ok so this is still an issue after all. It isn't every time but it is happening sometimes. But I have just come off a career mission in BOBP when there was some gun misfire during flight but the interesting/worrying thing was at the very end after I landed and turned off the engine and there was a clear stutter in the sound from the engines of other planes.  I have recorded this but no idea how to convert the recording into something I can upload here - any tips?

[-DED-Rapidus]

@Monksilver, Did you record the track? or video?

[Monksilver]

47 minutes ago, -DED-Rapidus said:

@Monksilver, Did you record the track? or video?

 

a track within the game's recording system. Would it work if I sent the track file to you - but it is over 5mb so can't upload here.

[Slangen]

Hi guys. First posting here ?.

Just started playing FC 1, and am experiencing terrible input lag.  Affects both flight controls and guns (i.e. joystick). I use the Logitech G940 system, and it works very well in DCS and MSFS2020, so I know my hardware is ok.  I notice already on ground that stick input will suddenly lag, for example watching the aileron and moving the stick, I'll get no reaction for about half a second, and then suddenly the input is registered. Then it can work ok for a few inputs on the stick, before the lag is repeated. The same lag is noticed when firing guns.  This breakes the immersion completely, and more or less ruins the game for me.  Any suggestions?

[WWDarkdiz]

I'm having a similar issue.  I can be in pretty much any flight regime, and without warning the game does not recognize any input from my controls.  After several seconds, the game seems to catch up, but this has only recently begun happening (since the last update to 4.605b).  Most noticeable on a winter Moscow map flying the F2 in multiplayer.

No control issues in other games (DCS).

It FEELS like a stall, when you pull a little too hard and the aircraft freezes and is unresponsive for a second.  However, easing off the turn does nothing, even going full deflection does nothing, until the input catches up, and then of course you snap to the current input.  The world still goes by (scenery is what you would expect to see), but for anywhere from 3 to 5 seconds the aircraft remains in whatever attitude it was in when the input ceased.

[Mandoble]

On 12/1/2021 at 6:37 AM, WWDarkdiz said:

I'm having a similar issue.  I can be in pretty much any flight regime, and without warning the game does not recognize any input from my controls.  After several seconds, the game seems to catch up, but this has only recently begun happening (since the last update to 4.605b).  Most noticeable on a winter Moscow map flying the F2 in multiplayer.

If would be the very same issue If during these few seconds the controls still respond, but with lag. But if your controls simply don't respond until few second later, then the issue would be different.

[Enigma89]

I am getting the same issue. 

 

Here is what I am seeing:

 

1) As soon as I start IL-2, all Discord audio goes to shit. Not packet loss, just everything starts to crackle.

2) When I try to play, my Joystick is totally fine. My Virpil throttle has about a full 3 second input lag. I move my throttle from 0% to 100% then nothing happens and then in game about 3 seconds later the throttle goes to 100%.

 

Have not made any changes to my system or any updates. Everything works fine in DCS but not in IL2. I validated that hardware is all okay.

 

 

EDIT:

@-DED-Rapidus please check PMs also for this.

Edited December 8, 2021 by Enigma89

[-DED-Rapidus]

@Enigma89, where was the problem? in the control device configuration interface or already in the mission?

[Enigma89]

5 hours ago, -DED-Rapidus said:

@Enigma89, where was the problem? in the control device configuration interface or already in the mission?

The problem is not resolved in the public version of the game. Everything looks fine on my end but when trying to play the input lags for 3 seconds. As I mentioned in the tester forum, this problem doesn't happen on the beta version of the game. 

[Enigma89]

This issue is gone due to the latest update

[Enigma89]

This issue has returned all of a sudden. Still not present in any other game.

[Enigma89]

I fixed this issue. It was bios update that was needed on my mother board.