RedX

Gamers Nexus FPS Benchmarks Are Flawed: Introducing Animation Error | Engineering Discussion Has anyone used PresentMon? if so, did you find value in using it to increase performance? And or LMT measurements?

chatGPT isn't reliable with math. Lawyer cites fake cases generated by ChatGPT in legal brief I'm not trying to give you a hard time, I'm just trying to warn you of it's limitations. It might be better with math with the wolfram alpha plugin. But something like this.. it still might not be able to figure out what equation to use.. @Skwuruhljust wondering but what is .5 represent in the equation? @DPI WizardWhat does 2 represent in the equation?

thanks for the explanation. ChatGPT is a predictive text model. It doesn't' have problem solving capabilities. And it doesn't understand math. Like if you what is 1 + 1 = ? If it gets the answer right, it's only because that's the most common text after 1 + 1. It often fails, while sounding very convincing. There are plugins for chatGPT, like wolfram alpha. But your basically using wolfram alpha at that point.

You can increase your CPI as you lower your sensitivity to maintain the same sum of speed and distance per inch. As an example with enhance pointer position off 400 CPI * 14 WPS (2) = 800 DPI 800 CPI * 10 WPS (1) = 800 DPI 1,600 CPI * 5 WPS (.5) = 800 DPI With all these combinations, moving the mouse 1 inch results in 800 DPI of movement in windows. Older mice can have significantly more drift at higher speed, and with higher CPI. But that doesn't seem to be an issue with newer sensors like a focus+ . Which seems to have 90%+ accuracy at low, or high speeds of movement, even with a high CPI. I know this is old, but I use to wonder about this. WPS 6 is a multiple of .6. So what happens is you move your mouse 2 CPI, and you see the cursor move 1 pixel. And you brain doesn't realize you moved 2 CPI. Your brain just thinks you've moved 1 CPI. The results is the same at any CPI. If you want to see skipping. What you'd want to do is set a multiplier that's 2 or greater. For instance 16 WPS is a multiplier of 3. Which makes it very easy to see pixel skipping in windows. And again, this is going to happen regardless of CPI. All of this is CPI to DPI. It's different in FPS games, because your going from CPI to Rotation. You can't have half a pixel, but you can have half a degree. And at greater distances, even a half of a degree can be a significant difference. As you lower your rotation, can increase your CPI to maintain the same speed, and sum of rotations.

What value are we supposed to be inputting as a value for arctan? And what makes the result the perfect FOV?

I loved the original MX518 and MX500. The mouse was great out of the box. And it had a ton of buttons. I kept buying Logitech mice, but the mice just started feeling weird. I ended up switching to razer. And the mouse just felt right out of the box. Like even if you could re-create your ordinal setup. Like same mouse, same dpi, same windows sensitivity, same game, same game sensitivity, same monitor. If you've been doing some thing else for a while, or your body has changed, it might feel weird now. But if you knew all those details.. You could try translating them to your current setup.

I'm using a razer viper 8k. Which is a focus+ sensor, and has Motion Sync. The sensor seems to have better tracking in general, including at faster speeds. I haven't herd of any mouse smoothing issues with it.. I'm also using dedicate a USB 3.0 controller just for the mouse to reduce latency. (something I picked up from the BlurBuster forum) I've also made many of the suggestions in Calypto 8k latency guide to try and reduce system latency. I could probably do more, but I haven't lobotomized windows. But I haven't gotten to buttery smooth 8k. It might be a limit of my CPU, but I still have a few things to try. It might be interesting to try that test with q3a, and then trying to ask John Carmack about the results.

It's an interesting test, but I wonder if there are other factors they're not considering like mouse clicks and mouse movements might be read at the time. Weapon attributes like cast time could effect where a shot is fired. Some games interpret input between frames. Or how a human can't go from x+0 to x+125 in a single step. In the case of a real fast swipe, your going to be seeing 6ms+, or 10ms+ behind. And your click isn't going to register instantly. So in a real swipe, would you really expect to be seeing dead center before the click? Like wouldn't you be seeing before dead center? Mouse tester agrees with The Noob Police 800 at 1000Hz 7500 at 1000 HZ 7500 at 4000 HZ Personally, I think Windows UI for mouse settings is kind of dated. It obfuscate information making it needlessly less functional. Users should be able to easily see, and set the multipliers for mouse sensitivity. As more people use higher DPIs, they're is going to be an increased need more granular control of mouse sensitivity settings. If they're worried about confusion, they could always hide it in an advanced button, or something. It would also be nice if it acutely showed PDI * sensitivity = ePPI.

Is there a go to formula to calculate inches per 360? something that takes FOV, yaw, extra, into account?

Would you try it? 40 USD seems high.

Low latency mode can make the CPU a bottleneck, so if your computer is having heavy CPU , it might effect performance in some situations. Having poor FPS can effect aim. 8k on a 1k game can cause lag Testing This seems like something that could easily be tested with Sensitivity Matcher, or program a teensy to act as a mouse. Like configure Sensitivity Matcher to do a 360 in CS:GO, and other games. And then test with with Reflex Mode off, on, low latency. And see if it makes any difference. Not sure how to test this in a safe way in csgo, sense they have anti cheat. And it might see this as cheating. FPS Some games are effected by FPS. q3a bridge jump, MH jump required 125 FPS. Apex Legnds tricks like Supper Jumps, seem to work better at 180 FPS. Early versions of q3a used object collection which was effected by FPS. They later switched to a server side math based approach. Some games might not consider what's happening between frames. So having a bunch of frames, even if you can't see them, might be useful in some circumstances. I can't find the reference to it, but I seem to remember overwatch making a big deal about how their game considered mouse position and clicks between frames.

Just a FYI, Even if you had perfect conversion between between DPI / Sensitivity; Mouse sensors perform differently at different DPIs, and at different velocities. IE: 400 DPI @ 2 Windows Sensitivity = 800 CPI 800 DPI @ 1 Windows Sensitivity = 800 CPI 1600 DPI @ .5 Windows Sensitivity = 800 CPI 3200 DPI @ 0.25 Windows Sensitivity = 800 CPI For instance with the above table for a G304: at 400 CPI, 10 IPS, it's 419.74 CPI = 839.48 at 800 CPI, 10 IPS, it's 837.57 CPI = 837.57 at 400 DPI 10 IPS, 9.33 offset = 18.66 50 IPS, 16.54 offset = 16.54 at 800 DPI 10 IPS, 9.2 offset = 18.4 50 IPS, 10.93 offset = 10.93 Going higher IPS, and higher DPI, depending on the mouse the differences can get much more dramatic. There usually a 'sweet spot' where the mouse seems to have the least amount of error.

I don't think there is a GWTEST for that specific mouse. But the pmw 3389 is also used by: MM710, Hati HT-M, XM1, Pulsefire Pro, Pulsefire Surge. And they have tested the XM1 with upgraded firmware. Unless the rocat has some issues, it might have similar results. GWTEST test for XM1: 400 DPI: 10 ips @ 91.22% , 30 ips @ 90.92%, 50 ips @ 87.11%. 800 DPI: 10 ips @ 91.06% , 30 ips @ 91.39%, 50 ips @ 90.89%. So it seems that pmw 3389 performs better at 800 DPI, then 400 DPI.

Looking at their chart, it seems like they're talking about a difference of up to 11.7 ms of latency. (17.11ms vs 10 ms) ((400 dpi vs 1600 DPI)) At faster speed, the difference drops to 2.05 ms of latency. At 120 fps, that's like .24 to 1.32 frames. Or at 360 fps, .73 to 3.96 frames. I think your theory makes sense, but has any one tested it? It might be interesting to see if both DPI stop at the same time. Just to bring up an additional point about higher DPI. Have you seen the GWTEST results? (look at the circle results) At 400 DPI, moving at 50 ips, it looks like the mouse is 75.05% accurate. At 50 ips, the mouse accuracy goes up to 91.67 @ 800 DPI, 92.65 @ 1600 DPI, and 94.17 @ 2400 DPI .