Jump to content

COD cold war: sensitivity calc is wrong


Recommended Posts

Posted

I've been trying to convert from overwatch to cold war and I keep triple checking my info and it's just flat out wrong. It switches from 3.66 in game with 1. multiplier to 12 in game with a .3 multiplier. Like what? 12 in game? That's going to make the hipfire wrong.

Ps idk why it won't let me post in supported games category but it lets me post here.  

  • Wizard
Posted
2 hours ago, FailsAndLuck said:

I've been trying to convert from overwatch to cold war and I keep triple checking my info and it's just flat out wrong. It switches from 3.66 in game with 1. multiplier to 12 in game with a .3 multiplier. Like what? 12 in game? That's going to make the hipfire wrong.

If you select an aim with multiple sensitivity values you need to provide your current sensitivity for all fields that are available in the calculator, as it doesn't know what sensitivity you have. So the default value will be filled out as a placeholder. The exception is when you use the "All" aim (which is always recommended), then missing values will be calculated (but still default values used for some fields).

 

2 hours ago, FailsAndLuck said:

Ps idk why it won't let me post in supported games category but it lets me post here.  

The supported games category has one topic for each game, so find the topic for the game you have a question about (just click the game name in the game info section of the calculator) and post in it :)

Posted
1 minute ago, DPI Wizard said:

If you select an aim with multiple sensitivity values you need to provide your current sensitivity for all fields that are available in the calculator, as it doesn't know what sensitivity you have. So the default value will be filled out as a placeholder. The exception is when you use the "All" aim (which is always recommended), then missing values will be calculated (but still default values used for some fields).

 

The supported games category has one topic for each game, so find the topic for the game you have a question about (just click the game name in the game info section of the calculator) and post in it :)

I did provide my current sens for all fields and the conversion was wrong. I also tried using the "all" aim and it was also not even close. You can try to chalk it up to user error but I think maybe you guys should take another look, because I'm not renewing my subscription until then unfortunately.

  • Wizard
Posted
2 minutes ago, FailsAndLuck said:

I did provide my current sens for all fields and the conversion was wrong. I also tried using the "all" aim and it was also not even close. You can try to chalk it up to user error but I think maybe you guys should take another look, because I'm not renewing my subscription until then unfortunately.

Can you provide a link to your calculation? Use the purple share button.

  • Wizard
Posted
1 minute ago, FailsAndLuck said:

How is this wrong exactly? This calculation provides you with the same tracking speed for all scopes. 

Just now, FailsAndLuck said:

sorry this one actually but in reality both are wrong. https://www.mouse-sensitivity.com/?share=0a5c3ac3f6c918ad8f4e50b5a0560536

Here you have not filled in your current sensitivity as I said, you have default values for both the Overwatch scope sensitivity (30, unless that's what you use?), and 12 for CW hipfire instead of 3.66.

 

1 minute ago, FailsAndLuck said:

OMFG it keeps resetting a different field to blank. Whatever your choice to check the tool idk man

The calculator can't know your exciting values from the beginning, any field that requires a value will load the default value when you select an aim the first time. Consequent aim changes will keep the value you provided as long as the field is the same.

Posted
5 minutes ago, DPI Wizard said:

How is this wrong exactly? This calculation provides you with the same tracking speed for all scopes. 

Here you have not filled in your current sensitivity as I said, you have default values for both the Overwatch scope sensitivity (30, unless that's what you use?), and 12 for CW hipfire instead of 3.66.

 

The calculator can't know your exciting values from the beginning, any field that requires a value will load the default value when you select an aim the first time. Consequent aim changes will keep the value you provided as long as the field is the same.

The result is essentially 3.66 in game and .75x for the scoped. 1st it doesn't even feel remotely close (I had both games open and then one at a time) and 2nd why would it be .75x scoped when default 1.0x is too low to be close? It converted it lower...

  • Wizard
Posted
1 minute ago, FailsAndLuck said:

The result is essentially 3.66 in game and .75x for the scoped. 1st it doesn't even feel remotely close (I had both games open and then one at a time) and 2nd why would it be .75x scoped when default 1.0x is too low to be close? It converted it lower...

What exactly is your expectation btw, what is your current aim sensitivity in Overwatch?

With the first conversion what you get is this, exactly the same tracking speed for every scope:

Now this isn't necessarily what works for everyone, so you need to adjust the conversion setup according to what you want. If it feels too slow and you instead want the same flick movement to say the edge of the monitor, set ADS and scope to MDH 100% instead:

https://www.mouse-sensitivity.com/?share=1f02f061cff46e7fa7bfa41386a667d5

 

Posted

Look i'm not sure what to tell you, maybe cold war is bugged in some way and you guys haven't compensated for it. I'm not sure either way it doesn't even feel close to the same 3.66 in game with 37.89 scoped widowmaker sense. I also tried the relative with 0 monitor coefficient to try and get a 1:1 and it's not that either. If you think it's right fine but for me I don't think so.

  • Wizard
Posted
2 hours ago, FailsAndLuck said:

Look i'm not sure what to tell you, maybe cold war is bugged in some way and you guys haven't compensated for it. I'm not sure either way it doesn't even feel close to the same 3.66 in game with 37.89 scoped widowmaker sense. I also tried the relative with 0 monitor coefficient to try and get a 1:1 and it's not that either. If you think it's right fine but for me I don't think so.

Feel is a relative term, it depends on what you mean by feel. Same tracking? Same flicking? Same 360 distance?

Try this one, hipfire here is Widowmaker with 3.66/37.89, ADS is the 6X scope from CW with 3.66/0 coeff/1 ADS sens and they have the exact same tracking speed:

https://www.3daimtrainer.com/mouse-sensitivity/?dpi=800&360dist1=49.1658&360dist2=166.3032&fov1=30&fov2=9.058387&pov=first

This is what the sensitivity in the games should be like. I haven't seen any bug in CW myself after hours and hours of testing, but if you encounter a bug there's not much we can do other than hope they fix it.

  • 2 weeks later...
Posted
On 12/2/2020 at 10:24 AM, FailsAndLuck said:

Look i'm not sure what to tell you, maybe cold war is bugged in some way and you guys haven't compensated for it. I'm not sure either way it doesn't even feel close to the same 3.66 in game with 37.89 scoped widowmaker sense. I also tried the relative with 0 monitor coefficient to try and get a 1:1 and it's not that either. If you think it's right fine but for me I don't think so.

Mouse sens isn't a mystery or a black art. It's either the correct amount of yaw/pitch per x number of counts sent from a mouse, as per the method you are choosing to match, or it isn't. "Feel" is irrelevant to that process.

This just sounds like you haven't yet decided what the best way for you to match ADS is for your own preference, but you should also check that your mouse software doesn't have an automatic profile for a game that has a different dpi set.

You should also note that different games have other mechanics that can make aim feel different, such as the camera viewport position in both z axis and y axis vs it's pivot point (some games tie the camera physically to a character models head which then moves as per the character animations, which usually sets the camera slightly forward of its pivot point, others position the camera and pivot directly within the character's centre mass vertically and the character model just bobs around it), and also strafe movement speed can play a huge part because people rarely aim when completely stood still. Some games also scale during ADS transitions differently, and since you don't usually aim then turn, but rather aim *and* turn simultaneously, this can also massively change how aiming feels even at exactly the same sensitivity.

The calculator can match the mouse sensitivity, FOV and resolutions in a multitude of fashions you can select, but not all the other facets of the game - you still need to learn / adapt to play the "new game" somewhat.

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...