So, you’re really thinking they shrink from 50ms to 5-6ms? I highly doubt it although I think is possible about 8-10ms within certain circunstances. Also at 400fps your each about 2.47-2.53ms, about 394-396 you get 2.6 at 412 about 2.3 and 423 about 1.8. I measured on the radeon adrenalin on the second screen, the game didn’t “Handled” the extra frames for whatever reason but registered the 1.8 on SIM at 423 accounted frames on adrenalin and 2.47-2.53ms at 400fps also. That I reached on RX 6900xt LC(OEM) with fast timming memory. As reference this model is slightly higher clocked version of rx 6950xt with the 18gbps output and stuff like that.
Weirdly enough Nvidia Reflex affects the SIM value on gtx 1080. Maybe on newer doesn’t but in there does. When enabled makes the gtx 1080 SIM values behave oddly btw, with huge spikes and huge drops. Also cutting roughly 30-40% their OG values for whatever reason.
His framerate on 360hz was like 260-280fps. He would decrease visual latency on Monitor not exactly PC itself. If you see the hud you will notice:
fps (273fps)
Render Present Latency (1.2ms)
Render latency (0.8ms)
Mouse latency (2.6ms)
PC+Display Latency (22.9ms)
System latency (25.5ms)
In game SIM would be about 4.6ms under 273fps. At 400 is 2.3, a bit lower than 400 2.5, 423fps about 1.8ms. So, SIM = both renders(1.2+0.8)+CPU(2.6ms). His measurement were: SIM+MOUSE+DISPLAY
Also when he changed at 71fps (reflex off to on) he left from 21 render latency to 15 render latency. Which would effectively affect the render latency and his SIM.
SIM often is about PC Latency on Reflex, which is part of the calculation. Which would be in KARQ’s case 2.6+1.2+0.8 at 273fps. Meaning 4.6ms PC latency(CPU+GPU). Add the display you get +18.3ms on top of it the mouse about 2.6ms reaching the 25.5ms value final or parse of 22.9ms without mouse
If on their rtx 4090 recording they reached 550 would mean about 1.2-1.4ish + mouse which would reflect their mouse in about 3.1-3.3ms. aligned with most mouses They showed 5.5-9.6ms oscilating a ton during the gameplay. My guess they simply picked the SIM+mouse(2.6ms). Which could be near the measurement I had. I got 423fps reaching 1.8ms in game. Which 438 they got 7.2ms and at 366fps got 9.6ms.
Their video:
at 506fps has 5.8ms
https://www.youtube.com/watch?v=lbcYFgQJOLM&t=8s
at 485 has 5.6ms
https://youtu.be/lbcYFgQJOLM?t=9
My guess the discrepancy is about the mouse being wireless and the pc having more “delay” on cpu side because of it.
5.5 - 1.6ms(SIM) = 3.9ms mouse (Roughly 505fps) then, the display about 3.2 leaving again to 8.7 ms pc latency.
So the mouse most likely would be:
https://www.rtings.com/mouse/reviews/roccat/kone-pro-air
due:
https://www.nvidia.com/content/dam/en-zz/Solutions/geforce/ada/news/play-competitive-games-with-rtx-40-series-and-reflex/nvidia-reflex-new-latency-analyzer-mice-september-2022.jpg
They simple are using “Mouse+SIM on the top left”
https://www.nvidia.com/content/dam/en-zz/Solutions/geforce/ada/news/rtx-40-series-graphics-cards-announcements/geforce-rtx-40-series-nvidia-reflex-sub-10ms-system-latency-latest.jpg
I found the mouse of the pic:
https://www.rtings.com/mouse/reviews/logitech/g-pro-x-superlight
3.1ms(mouse)
400fps = 8.6ms-3.1 = 5.5ms which would be about 2.3 SIM (pc latency). Leaving to 3.2ms the display:
https://www.nvidia.com/content/dam/en-zz/Solutions/geforce/news/reflex-low-latency-platform/nvidia-reflex-end-to-end-system-latency-terminology.png
Their claim about 8.6ms system latency can hold the ground if you consider SIM as PC latency, add mouse and monitor latency.
basically:
3.1 ms from mouse
2.3 ms from cpu+gpu
3.2 ms from display
8.6ms system latency claim
So, they improved the cpu+gpu time with more fps and improved the display due the frequent 360hz+ delivery.
My bet:
PC latency = SIM
System latency = Display+SIM+Mouse
which would reflect their 8.6ms claim of system latency and in game 366fps got 9.6ms. 9.6-3.1 = 6.5ms (SIM would be about 3.3ms) leaving the display again 3.2.
The margin error most likely would be about 0.2-0.3 to SIM/Display on the wired mouse and on the wireless one on cpu due the “receiver”.
That’s my guess on the situation