Talking about the "Unquantifiable frame time value" on 3600Literal evidence bhi provide kar dein please. DF and VG Tech only please
Is it a bigger yikes than having more VRAM and STILL disabling RT on PS5? I don't think soAs long as game changing RT is disabled. Yikes!
Oh right, my bad . Didn't notice the green line intersecting with the white graph. 66.66ms is still a big yikes thoTalking about the "Unquantifiable frame time value" on 3600
But I have RT and VRR enabled on PS5Is it a bigger yikes than having more VRAM and STILL disabling RT on PS5? I don't think so
Imagine preferring inconsistent input latency when you're already above 200ms+ at best. Yikess!!But I have RT and VRR enabled on PS5
Okay then. Chandoo playing a "big yikkkkess" version, or disabling RT even on higher VRAM. Yikes all around
Imagine thinking the PC version has lower latency when it is dictated by animation priooority. As seen in the case of RDR2, higher frame rates don't do much
Refresh rates and frame rates, CerebralTiger. Refresh rates and frame rates. You're playing the game 60Hz. Surely you wish a 120Hz mode was implemented? Now imagine that going even higher on a PCImagine thinking the PC version has lower latency when it is dictated by animation priooority. As seen in the case of RDR2, higher frame rates don't do much
Neither do much to overcome animation priooority tho. It's an inherent design choice
10% deadzone is literally next to no deadzone as far as I'm concerned. I use the same setting in pretty much every shooter I playAnd having the immediate response from a kb+mouse. No deadzone bs
They do alot to reduce the input latency, which is the goal
Its MASSIVE when there is none when I'm playing on a mouse + keyboard10% deadzone is literally next to no deadzone as far as I'm concerned. I use the same setting in pretty much every shooter I play
RE Engine games generally don't exhibit high input latency tho. A majority of that 200ms value seems to be animation priorityThey do alot to reduce the input latency, which is the goal
Makes sense for mouse/kb and gyro, but 0% (or even 5%) deadzone on an analog stick can lead to inadvertent movementIts MASSIVE when there is none when I'm playing on a mouse + keyboard
So now NXGamer doesn't know how to measure input latency. Got it.A majority of that 200ms value seems to be animation priority
Makes it the best control method to play this as wellMakes sense for mouse/kb and gyro aim, but 0% (or even 5%) deadzone on a controller can lead to inadvertent movement
I mean, games have deliberate startup delay for movement to allow smoother animation transitions and add some inertia to physics. That is factored into NXGamer's measurement. Alex measured input latency and came to the same conclusion for RDR2So now NXGamer doesn't know how to measure input latency. Got it.
And the less time in end to end latency the better. That's just a fact.I mean, games have deliberate startup delay for movement to allow smoother animation transitions and add some inertia to physics. That is factored into NXGamer's measurement. Alex measured input latency and came to the same conclusion for RDR2
).
Input latency can always be reduced and the lesser, the better, since that is something the players can control (on PC atleastI'm not defending RDR2's design choice to prioritize realistic animations and physics over responsive controls (too much of realism isn't great for games
I'm saying that a majority of that 200ms value determined by NXGamer is likely to be due to an inherent delay and not engine-related input latency. The latter can be reduced by playing at higher a higher frame rate, the former can't, as Alex has demonstrated in his RDR2 latency test
). Surely, CerebralTiger feels display lag is a crucial measure when buying a TV, regardless of what the engine latency is for a game 
I had included the game in my to-buy list once I finished with my existing library of PS5 games.
Please refer to:Where is the stealth video with later enemies?
Aaaaaand we're done here as well
Aciel:
Aciel:
Necrokiller:
Necrokiller:
XPremiuM:
XPremiuM:
