Based on Alex's test, running at 60fps still results in a baseline latency of 181ms (not counting animations), which indicates there is likely some induced latency to ensure animations get enough of a window to startup, as he notes as well. What reading did you get?
Alex did not use the test case that you suggested is the best. And I just carried it out as well. I will average out and post my findings. Safe to say though, that it's nowhere near 181ms.
That was literally his first test. For his other tests, he mentioned taking animations into account, as he was testing the time taken for the action to be performed. Test 2 and 3 were input latency + animation frames.
Hes using the LT button to start up the aiming animation. "Weapon draw"
You should also test the LT-to-startup-aiming animation to see if you get the same result as him at 30 or 60fps.
But this limitation is true for anyone who tests using the controller. There is no indication whether NX gamer or DF use a different method.You should also test the LT-to-startup-aiming animation to see if you get the same result as him at 30 or 60fps.
Also, for the shooting test, remap the input to the shoulder button (RB) for more accurate results. Trigger input leads to reading errors.
Edit: yeah, this is inaccurate.
There's no telling at what threshold the trigger takes your input. The gun fires before you even fully press the trigger.
Also, God of War (2018) has a performance mode which will have big improvements over the input latency on graphics mode if it bothers anyone that much.
lmao, I should check this on my base PS4 again. You know, the console that the vast majority owns.
just posting relevant pointers to the discussion going on
Your analogy was terrible and made in haste. No need to stick with itI'm also never complaining about input latency
Buttons can be re-mapped from the PS4 OS. Plus RDR2 might have an in-game option to remap aim/shoot to L1/R1. Can't remember if it did. Either way, this is a non-issue. DF and NX gamer were most likely aware of this and tested accordingly.
Did you make gifs? I'd like to see them.
Yeah, well, it's known that animation priority is the main culprit in the case of RDR2, and Rockstar's stubbornness when it comes to running animations in their full "glory".
Expect threads to take wild U turns when Necrokiller's around
Heres one.
Assuming it's the CTRL key that triggers gunfire, I'm seeing visible signs of the gun firing at the 13th frame, and of the gunshot hitting the target at the 15th frame.
My capture is also at 120fps. This is important for the measurement.Assuming it's the CTRL key that triggers gunfire, I'm seeing visible signs of the gun firing at the 13th frame, and of the gunshot hitting the target at the 15th frame.
13 x 16 = 208ms. That said, I believe Alex conducted his test using a 120fps camera, so it's probably 181ms.
Interesting. Though, ideally, one ought to be repeating the test a number of times and average out findings to get more precise data. Regardless, it gives a good rough idea.
displaylag.com
As a game like RDR2 is proof enough, the quickest or best case scenario is not indicative of real world perceived lag. As with RDR2, we might see a lower figure depending on a different action but Kratos still doesn't feel responsive to control and data backs that up.
XPremiuM:
XPremiuM:
That's still higher than it's total play length. A 5 hour campaign for a $50 game is downright scammy.Necrokiller said:Hellblade 2 has a lower peak player count than Redfall
Necrokiller:
The cross gen era really made people think 60fps would be a new standard lolLegacyGamerGuy said:
Necrokiller:
Chandoo:
Score 1 for game pass. I wouldn't pay full price for this at retail either.LegacyGamerGuy said:
XPremiuM:
BTW, i started Ghost of Tsushima, and it got me hooked within the first couple of minutes. I...
