Jump to content

What do "Match At" percentages mean?


Recommended Posts

Posted

I am just trying to match desktop sensitivity of 7 to overwatch.

 

I am at 1080p 1920/1080, DPI 1800,

 

But there is a variable called "match at" with percentages that drastically change the suggested sensitivity for overwatch... What does this mean and can anyone help me figure this out?

  • Wizard
Posted

Check out this video if you haven't already:

 

 

In short, the "Match At" percentage is where on the screen between your cross hair and monitor edge to match the sensitivity. If the FOV is different in the games you are converting between, you can only perfectly match it to one point.

 

The Viewspeed conversion is a dynamic version of Monitor Distance, which usually lands between 60% and 70%. It converts using a constant arc length.

Posted

Okay i understand it up to a point. For matching different fovs.

 

But i am unsure of what match at percentage to use for desktop to overwatch.

 

What would you suggest be the best to pick for desktop? Or the best way to do it.

  • Wizard
Posted

Okay i understand it up to a point. For matching different fovs.

 

But i am unsure of what match at percentage to use for desktop to overwatch.

 

What would you suggest be the best to pick for desktop? Or the best way to do it.

I would suggest trying Viewspeed for all conversion, as that method adjusts itself based on FOV or desktop.

Posted

I would suggest trying Viewspeed for all conversion, as that method adjusts itself based on FOV or desktop.

 

So if I'm using 5 in windows with 400 dpi and want to convert it to CS:GO sensitivity with Viewspeed conversion, do I use m_rawinput in CS:GO or do I still use 5/11 windows with the sensitivity it gave me?

Posted

Since you are converting from 400 DPI 5 WPS, and raw input bypasses WPS, the output game will need to have 6 WPS in the calculator.

 

I also wouldn't recommend using 5 WPS as it makes it feel inconsistent since the OS will drop every 4th count. Feel free to use other WPS below 6 though.

Yeah, but I mean, does it calculate the cs go sensitivity as raw_input ON or OFF?

with 400 dpi, 5wps viewspeed conversion to Cs go will give me a sensitivity of 2.18~ but I do not know if it's calculating with rawinput ON (skipping wps reading directly from mouse, which mean 6wps) or OFF.

 

That sucks since 5 wps feels very good for me and 4 would be too slow and 6 would be too high =/

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...