Jump to content

Gray Zone Warfare

Use the config file for best accuracy.
Read more...

World of Shooting

See the game notes for instructions on how to disable smoothing.
Read more...

Robin Hood - Sherwood Builders

See the game notes for instructions on how to reduce smoothing.
Read more...

Gas Station Simulator

See the game notes for instructions on how to disable smoothing.
Read more...

Mortal Shell

See the game notes for instructions on how to disable smoothing.
Read more...

Call of Duty: Black Ops Cold War


DPI Wizard
Added with a limited number of aims, more will be added later!

User Feedback

Recommended Comments



  • Wizard
51 minutes ago, jericho246 said:

I found this on reddit, apparently someone found a "fix" to the god awful aiming in this game. https://old.reddit.com/r/blackopscoldwar/comments/jv2hiy/potential_fix_slippery_horrible_aiming_on_pc/

 

But as a console user with no access to any config.ini files, I guess there is no way of fixing it with just in-game settings? :(

Interesting, I don't have an issue with this setting but it's probably affecting people depending on their hardware etc then.

Link to comment
  • Wizard

A couple of notes just reiterating and confirming what the devs have said:

  • Hipfire is exactly the same as in MW.
  • Relative coefficient works exactly like in MW.
  • Scopes above 4X works exactly like in MW (meaning they have locked FOV not affected by anything), but they do not match in terms of their power, so a 4X in MW is not the same as a 4X in CW.
    CW uses correct optical zoom for the FOV based on a locked FOV of 80 (or almost, it's off by a tiny bit), while MW uses seemingly arbitrarily assigned FOV values.
  • Scopes below 4X and ADS have a very weird scaling when set to "affected", meaning they do not scale the FOV in an expected manner (they are less affected than in MW). This does however not affect the sensitivity, which still behaves as expected based on the FOV.
  • Legacy works differently, as it is simply MDV 0% calculated based on your FOV. In MW it is MDV 0% to an FOV of 65 in Hdeg 4:3. 
  • If you use Relative in MW you can use the exact same settings (including FOV) in CW and everything will be the same.
  • For those not experiencing the same sensitivity in MW and CW based on the above there must be a bug in CW affecting some users.
Link to comment

If I use the exact settings I have for Modern Warfare in the new Cold War game, my aim is all over the place. I had the same issue with BO4 so my guess is it's something related to how Treyarch is using the game engine.   Just do a quick search for "sensitivity" across the blackopscoldwar subreddit and you'll see both PC and console users have severe issues compared to Modern Warfare.

Link to comment
  • Wizard
18 minutes ago, wetmog said:

If I use the exact settings I have for Modern Warfare in the new Cold War game, my aim is all over the place. I had the same issue with BO4 so my guess is it's something related to how Treyarch is using the game engine.   Just do a quick search for "sensitivity" across the blackopscoldwar subreddit and you'll see both PC and console users have severe issues compared to Modern Warfare.

That must be down to what you expect to be the same. If you expect a 4X in MW to be the same 360 distance as a 4X in CW you will be disappointed. They are not the same FOV so their distance is different.

When you set a relative sensitivity of for instance 1.78 on a 16:9 monitor, every aim and scope in both games does exactly that, they have the same distance to move the crosshair to what's at the edge of the monitor. If you set it to 0 they will all have the exact same tracking speed. I've tested this extensively, and they're exactly the same.

So when you say your sensitivity is all over the place, I really wonder what you mean. Do you mean a 4X in MW is not the same as a 4X in CW in terms of 360 distance? Do you mean aims with the same FOV act differently? Is the relative sensitivity not consistent across aims? Because you are either encountering a bug in CW causing an inconsistency (entirely possible), or you have the wrong expectation of what constitutes the same sensitivity.

If you give me your exact settings in both games and expectation vs reality I can check it to see if it's off or not.

Link to comment

I went through all of my Modern Warfare and Cold War mouse settings and class setups, and in both games I'm using 2560x1440p @ 165Hz, and the in-game options below.  On Modern Warfare, I mostly use Iron Sights, one setup with Monocle Reflex Sight, one setup with G.I. Mini Reflex, and my 2 Warzone setups have the VLK 3.0x Optic.  On Cold War, most setups are using Iron Sights, a couple setups with Millstop Reflex, and currently have the Kobra Red Dot on my M16. 

 

It's certainly difficult to express the exact problem I'm having but in Cold War my aim is very inconsistent specifically when it comes to ADS tracking.  On the other hand, I have no issue in Modern Warfare across any of my Loadouts regardless of what gun I'm using.  I'm able to hipfire accurately and lock onto my targets quickly and accurately when I ADS.  To me it feels like there is some mouse acceleration or deceleration going on.  I did add a config option today on Cold War ("mouse_horizontal_look = 1") that some people had success with, and I was going to do some testing with 1.78 on Cold War to see if that matches up closer to what Modern Warfare feels like.

 

Mouse Sensitivity - 6.0 with all multipliers left at 1

ADS Mouse Sensitivity - Relative with both multipliers at 1, Transition Timing of Instant, and Monitor Distance Coefficient at 1.33

ADS Sensitivity Transition Timing - Instant

Mouse Acceleration/Filter are both at 0, and Mouse Smoothing is Disabled

Field of View - 100

ADS Field of View - Independent

Link to comment
  • Wizard
19 minutes ago, wetmog said:

Mouse Sensitivity - 6.0 with all multipliers left at 1

ADS Mouse Sensitivity - Relative with both multipliers at 1, Transition Timing of Instant, and Monitor Distance Coefficient at 1.33

Remember that the only metric that is equal with this setting is moving to 133% your vertical FOV. That means for a 16:9 monitor moving to 75% the distance between the crosshair and the edge. Any other metric, be it tracking, 360 distance or any other monitor distance, will be different. I've tried your exact settings, and it does exactly what it is supposed to. You can test this with a tool like Kovaak's sensitivity matcher. In you case setting the physical stats to 1000 DPI and 1.053 in/rev (so the left side says "One Revolution of 1053 counts") will make it move exactly MDV 133% (MDH 75%) on execution. This should move the crosshair to the exact same object at this distance regardless of aim, like this does for MDH 50%:

 

Link to comment

OK so it appears based on the Calculator I should be using .90 on Low Zoom and .82 on High Zoom for Cold War, is that accurate?  Also why does it change the multiplier 1 to something less than 1 when I select All on Modern Warfare?  When I check my config they are all set to a value of 1.  I appreciate your feedback thus far!

 

Ok0Dbqk.png

 

rvY1CrB.png

Link to comment
  • Wizard
2 minutes ago, wetmog said:

OK so it appears based on the Calculator I should be using .90 on Low Zoom and .82 on High Zoom for Cold War, is that accurate?  Also why does it change the multiplier 1 to something less than 1 when I select All on Modern Warfare?  When I check my config they are all set to a value of 1.  I appreciate your feedback thus far!

The calculator calculates the sensitivity based on the conversion setup, and it seems like you have left at the default setting of MDV 0% while your MW setting is MDV 133%.  So if you set the conversion to MDV 133% you should get 1 for all aims.

image.png

If MDV 0% is what you want you should use a relative coefficient of 0 instead of 1.33 :)

 

Link to comment
  • Wizard
1 minute ago, EndlessOneV said:

If i want mp in Cold war and apex be the same 360 distance is this right?

For 360 distance that is correct yes.

Link to comment
9 minutes ago, DPI Wizard said:

The calculator calculates the sensitivity based on the conversion setup, and it seems like you have left at the default setting of MDV 0% while your MW setting is MDV 133%.  So if you set the conversion to MDV 133% you should get 1 for all aims.

image.png

If MDV 0% is what you want you should use a relative coefficient of 0 instead of 1.33 :)

 

Ah gotcha so at that rate then both games are exactly the same as you previously stated.  They certainly don't "feel" that way, I have adjusted the one setting in the Cold War config file so will do some additional testing to see if that makes the game feel closer to MW.

Link to comment

Ok than 1.07 is the 360 distance for ads mp and ar is slower that is what im expect and want is that right? In mw i have 0.92310 as ads that is why im wondering

Edited by EndlessOneV
Link to comment
  • Wizard
1 minute ago, EndlessOneV said:

Ok than 1.07 is the 360 distance for ads mp and ar is slower that is what im expect and want is that right?

Sorry, misread your first post. This is not correct for MP, only for AR and TR. MP will likely be slightly different, the calculations for that is hopefully up tomorrow.

Link to comment

I think SOME  of what is going on with the odd ADS feeling is that there seems to be an animation bug/delay when attempting to ADS when you are in a sprinting state.

I've noticed that when I'm sprinting and I try to ADS at a target i always end up over flicking. To compensate this I've changed the Sprint Behavior to Hold instead of Toggle. When I want to ADS I let go of my sprint button at the same time I click MB2 and I am able to track and flick accurately.

This theory might explain why @DPI Wizard isn't able to replicate the sensitivity issues we are having, as he is likely performing these measurements when standing still, as opposed to run and gunning.

I could be wrong, but changing Sprint Behavior to hold instead of toggle seems to have resolved my issues (In addition to changing my monitor distance to 0%) This attached ss is a game or two after I changed the settings if it's worth anything.

lulez.png

Link to comment
On 11/16/2020 at 4:54 PM, DPI Wizard said:

A couple of notes just reiterating and confirming what the devs have said:

  • Hipfire is exactly the same as in MW.
  • Relative coefficient works exactly like in MW.
  • Scopes above 4X works exactly like in MW (meaning they have locked FOV not affected by anything), but they do not match in terms of their power, so a 4X in MW is not the same as a 4X in CW.
    CW uses correct optical zoom for the FOV based on a locked FOV of 80 (or almost, it's off by a tiny bit), while MW uses seemingly arbitrarily assigned FOV values.
  • Scopes below 4X and ADS have a very weird scaling when set to "affected", meaning they do not scale the FOV in an expected manner (they are less affected than in MW). This does however not affect the sensitivity, which still behaves as expected based on the FOV.
  • Legacy works differently, as it is simply MDV 0% calculated based on your FOV. In MW it is MDV 0% to an FOV of 65 in Hdeg 4:3. So it is impossible to exactly replicate the MW Legacy in CW unless you play with the FOV set to 80/81 (which will be very close but not exact).
  • If you use Relative in MW you can use the exact same settings (including FOV) in CW and everything will be the same.
  • For those not experiencing the same sensitivity in MW and CW based on the above there must be a bug in CW affecting some users.

"Legacy works differently, as it is simply MDV 0% calculated based on your FOV. In MW it is MDV 0% to an FOV of 65 in Hdeg 4:3. So it is impossible to exactly replicate the MW Legacy in CW unless you play with the FOV set to 80/81 (which will be very close but not exact)."

This is absolute garbage (no hate towards you 🙂) I'm so used to playing Legacy "7" with 1x multiplier w/Affected at 115 FOV and there are so many people like me on Reddit who are desperately looking for a fix and now it's impossible to get it working like MW. I have looked all over the internet and commented under so many Treyarch posts and Cod partners. Is there any way you I could get it to be like MW or is Treyarch ever gonna bring the MW Legacy scaling to CW?

Link to comment
On 11/19/2020 at 7:51 AM, DPI Wizard said:

Actually it is not impossible, I meant Legacy to Legacy re-using MW values in CW was impossible unless you have a specific FOV.

If you use relative you can match it like this:

https://www.mouse-sensitivity.com/?share=2bc860351597714a7ec7a6a0e796d470

So you're saying I can get it to work like Legacy in MW by using relative in CW and changing settings? " unless you have a specific FOV"-And I do play at a specific FOV, 115. I'm new to this calculator I'm not sure how to read these things. Some help would be lovely! 😊

Edited by I am Bluefire
Link to comment
  • Wizard
4 hours ago, I am Bluefire said:

So you're saying I can get it to work like Legacy in MW by using relative in CW and changing settings? " unless you have a specific FOV"-And I do play at a specific FOV, 115. I'm new to this calculator I'm not sure how to read these things. Some help would be lovely! 😊

Use the link I provided, and change the settings according to your setup. But leave the input game as MW and the FOV at 65, change everything else (DPI, resolution, sensitivity etc) and use the 115 FOV for the output game.

Link to comment
32 minutes ago, stereo3D said:

1.37x sights have the same FOV as ADS (AR, TR), but 1.25x sights zoom in slightly more than ADS (SMG).

I used 1.25x optic on all my weapons and they scaled hipfire and ADS 1:1. I also used relative with a 1.78 monitor coefficient. And tweaked the low zoom multiplier. Try around 1.2-1.25 it should sync up

 

Link to comment
On 11/19/2020 at 7:51 AM, DPI Wizard said:

Actually it is not impossible, I meant Legacy to Legacy re-using MW values in CW was impossible unless you have a specific FOV.

If you use relative you can match it like this:

https://www.mouse-sensitivity.com/?share=2bc860351597714a7ec7a6a0e796d470

On modern warfare I used 7.33 hipfire sensitivity and with 1 ads sensitivity at 90 fov with independent. I'm also confused and not sure if I should change it to or independent.

Link to comment



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

×
×
  • Create New...