Southpaw

Can you show man an example of how you'd do it in say, Overwatch? Will your x and y sensitivity not be different in Windows as well? If I can just find a way to only change the Y axis sensitivity in Windows (like the mouse pointer speed setting but not adjusting X axis), I can cancel out the separate Y axis sens that rawaccel brings on desktop but still keep that effect in game.

Right, but I mean that say, you calculate for jedi's trick both horizontal and vertical, converting from windows/2D. It'll now give you a higher vertical sens than horizontal, but only in game. You then change the Y-axis sens on your mouse cursor in RawAccel so you can get that different X and Y in game to achieve these numbers. However, now that you've done that, the previous calculation that was made with your original windows cursor sensitivity is inaccurate to your new one, since RawAccel also made your windows cursor higher sens vertically, not just in game. So now while your in game sens conversion is accurate to your original say, 800 DPI (both X and Y), it's now inaccurate to your new 800 DPI (same X-axis but now like, 900 DPI Y-axis). Hopefully I'm coming across clearly.

Wouldn't doing this also change the cursor's vertical sensitivity, making the calculation inaccurate anyway? Only way for this to be effective for games that don't natively support x/y separate sens would be to manually set your rawaccel y axis ratio every time you get into game, and turn it back off whenever you're out of game, but for some games like PUBG where you're constantly using your cursor while playing, this would just be a hassle. Perhaps there's something I'm misunderstanding about this idea.

While this is true, it doesn't seem to apply when zooming all the way in. also, if not moving all the way to the sides, the center portion feels like it remains the same sensitivity, as though there's a specific threshold of pixels that you have to hit to kick in the slowing, as opposed to a gradual and consistent change. Maybe by zooming in/sticking to the center, you could derive a sensitivity from it? Again I could just be completely wrong

It's probably just an arbitrary value, but I've been curious about how Google Maps does it's sensitivity, because I've been searching for the best possible Desktop->in-game conversion (I know it's not possible to be perfect but I my brain needs to try), and Google Maps when you hold down left click to drag around the camera, it feels really good and the cursor stays mostly in the same spot as you turn the camera over the scenery. If it's possible to calculate exactly what the sensitivity is, that'd be cool to test out imo, at least with my limited knowledge on the topic. Here's an example for you to try for yourself: https://www.google.com/maps/place/Eiffel+Tower/@48.8567906,2.3034103,3a,75y,322.33h,111.64t/data=!3m7!1e1!3m5!1s5vdF22gFapcAAAAGOvMT8g!2e0!3e11!7i2840!8i1107!4m7!3m6!1s0x47e66e2964e34e2d:0x8ddca9ee380ef7e0!8m2!3d48.8583701!4d2.2944813!10e5!16zL20vMDJqODE

psa?

As the title suggests, I'm curious as to the typical application of settings like 100% MMD in both horizontal and vertical, as well as 0%. My understanding is that 100% MMD Horizontal is used to match flicks to the horizontal edges of the screen, while 100% MMD Vertical is meant to match flicks to the vertical edges of the screen. 0% would be the same for both, being the match for tracking, or directly on the crosshair. Though I'm wondering, if I were to want to match my in game sens to have a similar feeling to my desktop DPI, what monitor match setting would best emulate that?

I attempted this, and it appears you were correct. The sensitivity doesn't alter due to the config file, but at least I was correct about the FoV lol. Thanks for working this out with me, I hope they allow more precise settings in the future.

Just showing how it works, as I stated, it's a demonstration.

I apologize for the cutting out, new mic and I haven't adjusted the noise gate threshold to compensate. You still get the gist of what I'm saying.

I haven't found this to be the case. After setting the file to Read Only, any change I make within the game hasn't altered the GameUserSettings file. I just attempted what you stated by changing my sens from 1.485 (displayed in game settings as 1.5, of course) to 1.7 and saved the changes. I closed the game, checked the file, and it still showed 1.485. Launched the game again, and my sens was still being displayed as 1.5. Not sure why this isn't happening for you, so I'm going to stream this in a little bit and send the VOD in case you'd like to see my PoV.

I attempted to post it, but it just kept buffering and would flat out deny the gateway, so I guess when that issue solved it self, it all of the posts that I attempted at once. Trying to delete the others. The config editing did work for me. Not sure what DPI Wizard is referring to, or perhaps they've allowed it since that last respond.

This file allows you to adjust settings for Halo: Reach, such as sensitivity settings beyond the tens place in a decimal, such as allowing 1.65 rather than just 1.6 or 1.7. It also allows you to go beyond the default max FoV of 120 (Multiplier) up to 150. Make sure to set GameUserSettings file to "Read Only" by right-clicking it and pressing properties. Check the "Read Only" box, then apply, and you're good to go. File path: C:\Users\YourUsername\AppData\LocalLow\MCC\Saved\Config\WindowsNoEditor\GameUserSettings

Yes, change your OW widow and Ashe scope sens to the values I specified.

If you want your tracking to be the same, 46.04 is the best you're going to get for Ashe. For flicking similarity, you're gonna want 53.35. Widowmaker and Ana, not much you can do there with the calculator. Just going to have to feel that one out. I'd try 40.02.