Input Lag - Unreal Engine specific


(Amerika) #1

@MissMurder

-edit-
Adding for clarification.
Vsync off (game and system)
1 frame delay off
120+ FPS average
All graphical effects that can be turned down or off within the UI has been done

Now I know most people won’t have this issue as it’s kind of specific to my setup but I do know it’s an issue with many Unreal Engine games. My mouse setup is pretty old school Q3-centric and I play all FPS games like this. A 180 for me requires around a 10-12 inch swipe. I play with my arm and not my wrist and I do this partly because I have issues with fine motor movement with my wrist and partly because it’s just a great way to play an FPS and remain consistent.

Anyway, due to this low sensitivity setup I have noticed that in many Unreal Engine games there is a minor amount of mouse lag. Especially when zommed in with Vasilli. This happens in some games like the original Bioshock, Legendary and Deus Ex: HR but not in Bioshock Infinite or Unreal Tournament 2004. So there is definitely something there which is being tweaked that removes the latency for people who are using low sensitivity in the latter two games that isn’t being done in the others I mentioned.

It’s not that noticeable and you can get used to it when playing normally but I do notice it quite a bit when playing as Vasilli. I understand that this might not be a huge issue to Splash Damage since the amount of people who do this is pretty slim but if it’s something that could be looked into I would appreciate it.

Also, it’s not my mouse, mouse drivers or anything. Mouse acceleration is fully turned off on my system and this is a non-issue in many of the other games I play. If you google the games I mentioned you’ll see the issues. Especially the first Bioshock and Legendary. Both were virtually unplayable at my settings.


(Zenity) #2

Just to run down the obvious:

VSync is off?

One-frame delay is off?

Your FPS are high and consistent (let’s say around 100 at least)?

I tend to be quite sensitive to any form of input lag (and yes Unreal Engine games tend to be the worst offenders), but it seems fine to me so far in Dirty Bomb. I’ll play a bit more with Vasilli to see if I notice anything.


(Zenity) #3

Also I would try turning off any form of post-processing if you haven’t already.


(Amerika) #4

Sorry, I should have included that Vsync is off all around and 1 frame delay is off. I average over 120fps as well and I have almost every graphical setting turned down. I added that info to my original post.


(son!) #5

I’ve seen a few mentions on the ut forums about pixel skipping on max zoom, haven’t confirmed if it’s there in DB though, and can’t as I decided to not unlock vasilli.

latency though is likely there as it appears to be an engine problem that is even in the new ue4. the UT4 dev team is implementing some fixes though, which has improved latency compared to what it was 6 months ago, but it’s still a far cry from csgo/quake live.


(Amerika) #6

Yeah, that’s the thing. CSGO and Qlive, both of which I play (15 year Q3 vet now) and they are perfect. But as I mentioned there are UE games that do not have the lag with my setup so there is definitely something those devs did to fix the issue for their games. Perhaps it’s a default setting with the engine that most likely isn’t caught during testing because I’d wager most don’t playtest with my particular setup.


(fubar) #7

Try “RawInputUpdateTest True”, seems a little smoother to me.


(Amerika) #8

@MissMurder I got to thinking and you guys might want to fix this during closed beta sooner rather than later. Because whatever fix SD implements might make everyone’s sensitivity a bit off after the update and it would be better to only expose the beta players.

I know there is a fix for it and it’s quite possibly an easy fix. Other UE games have fixed it in the past.


(Khrode) #9

I noticed this too, it seems most noticeable for me when playing as Vasilli especially when going for flick shots. It just dosent feel right.


(Darkcola) #10

it throws off my shotgun aim.

esp with (wait for it)---- the wiimote.
this is good to hear though, calculating input lag for the wiimote emulator is tough enough- amusingly I have it working 1:1 no delay in the Unreal 4 engine Tournament game. At least that is improved?


(Litego) #11

I don’t have Vasilli unlocked but I do play at a much lower sensitivity and don’t have issues with other mercs.

But is it latency or is it simply lost input? I know Unreal Engine has issues with rounding errors on low sensitivities. And since sensitivity scales with FoV, meaning you have lower sensitivity while zoomed in, the sensitivity is much lower than what you set it in-game.

So if you were to move your mouse very slowly while zoomed in, are you turning or does perhaps nothing happen? If nothing happens, is that perhaps what feels like latency, because when you start moving your mouse it moves to slowly to register. Or is there actual latency regardless of this?

You could also try to set your DPI to 200 or as low as your mouse allows and increase your sensitivity to compensate, this should reduce the issue if it is lost input.


(Amerika) #12

It’s lost input. I could demo it pretty easily by putting a cam on my mouse while showing in game. If I scope with Vasilli and move slowly I get lost movement. So if I am trying to make micro adjustments then it can be pretty rough. As I’ve played Vasilli more and more in some situations this is getting to be a bigger issue for myself. I don’t have the issue as much outside of scoped rifles.

I tried this and it didn’t change anything. I can still move my mouse slightly, which works in other games and windows, and the movement will not register in Dirty Bomb. I can go almost half an inch before the crosshair will move.


(Zenity) #13

Wow, this is interesting to say the least (and hopefully will be fixed). Have you tried using a low DPI setting on your mouse then with a higher ingame sensitivity as Litego suggested? And what is your current ingame sensitivity? Let’s find out which settings are affected.


(Amerika) #14

Running 400 DPI and 2 in game sensitivity. So I can’t go much lower on the DPI and this is a known UE issue that has been fixed in other UE games. And it doesn’t happen in QLive, CS:GO or TF2.


(Zenity) #15

Running 400 DPI and 2 in game sensitivity. So I can’t go much lower on the DPI and this is a known UE issue that has been fixed in other UE games. And it doesn’t happen in QLive, CS:GO or TF2.[/quote]

:o :o

Are you serious? With those settings my view barely moves after moving my mouse over the entire mouse mat. I turn maybe 20 degrees or so? Could it be your Windows mouse settings or something which affects this as well? I would hope DB ignores that, but perhaps not. What is your sensitivity in cm per 360 degrees turn? Mine is around 40cm, and that’s with 1800 DPI and a sensitivity of 2 or 2.5 (still tweaking).

In any case, I was also able to reproduce the issue with the sniper scope, while moving the mouse really slowly. This is a rather big deal, and I hope it will be fixed soon.


(humaneBerry) #16

Running 400 DPI and 2 in game sensitivity. So I can’t go much lower on the DPI and this is a known UE issue that has been fixed in other UE games. And it doesn’t happen in QLive, CS:GO or TF2.[/quote]

:o :o

Are you serious? With those settings my view barely moves after moving my mouse over the entire mouse mat. I turn maybe 20 degrees or so? Could it be your Windows mouse settings or something which affects this as well? I would hope DB ignores that, but perhaps not. What is your sensitivity in cm per 360 degrees turn? Mine is around 40cm, and that’s with 1800 DPI and a sensitivity of 2 or 2.5 (still tweaking).

In any case, I was also able to reproduce the issue with the sniper scope, while moving the mouse really slowly. This is a rather big deal, and I hope it will be fixed soon.
[/quote]

Forgive me but I gotta ask something here.
I’ve only ever played casual fps games and never been into it 100% but i gotta make sure i follow you here.

In order for you to turn your crosshairs 360 degrees, that is a full circle, you have to move your mouse 40 cm? that is like a third of my desk.

Please dont take this the wrong way, im not questioning your judgement of distance but since i have never been into high lvl gaming I don’t quite follow these mouse related measurements.


(Zenity) #17

Running 400 DPI and 2 in game sensitivity. So I can’t go much lower on the DPI and this is a known UE issue that has been fixed in other UE games. And it doesn’t happen in QLive, CS:GO or TF2.[/quote]

:o :o

Are you serious? With those settings my view barely moves after moving my mouse over the entire mouse mat. I turn maybe 20 degrees or so? Could it be your Windows mouse settings or something which affects this as well? I would hope DB ignores that, but perhaps not. What is your sensitivity in cm per 360 degrees turn? Mine is around 40cm, and that’s with 1800 DPI and a sensitivity of 2 or 2.5 (still tweaking).

In any case, I was also able to reproduce the issue with the sniper scope, while moving the mouse really slowly. This is a rather big deal, and I hope it will be fixed soon.
[/quote]

Forgive me but I gotta ask something here.
I’ve only ever played casual fps games and never been into it 100% but i gotta make sure i follow you here.

In order for you to turn your crosshairs 360 degrees, that is a full circle, you have to move your mouse 40 cm? that is like a third of my desk.

Please dont take this the wrong way, im not questioning your judgement of distance but since i have never been into high lvl gaming I don’t quite follow these mouse related measurements. [/quote]

Yes, that’s correct. Of course you never do a 360 turn in game, so that’s just a theoretical measure. Which means that to turn around I have to lift the mouse a lot, which is fine. It’s more important to be accurate with targets in front of you.

I am still tweaking my sensitivity for this game though, but that’s roughly in line with what I have been using for other games as well.


(Zenity) #18

@Amerika did you say at the other thread that you are using mouse accel? That would explain your low settings of course. And I guess that could exaggerate the issue and also mess even more with your motor memory.


(Amerika) #19

I don’t use mouse accel anymore. I talked about how I did in Q3 and still do in Qlive but not any other game because no other game has proper settings for it. And no, I don’t have mouse accel on in windows or my mouse driver and this is a non-issue for every other game. This truly is a UE issue and it can be fixed as other UE games don’t have the problem.


(Zenity) #20

Yeah it definitely needs to be fixed. I’m just genuinely wondering why our settings are so different. You say in the other thread that it takes you about 30cm for a 180, but when I try 400 DPI with sens 2, it takes me about 70cm (that’s more than twice the length of my mouse mat), which I don’t think anybody could possibly play with. :slight_smile: