November 6, 20169 yr Wizard Take a backup of the file before you begin! If you mess up you can always delete the file and it will be re-created when you start the game, but all the settings in it are lost. The sensitivity for this game is in the file C:\Program Files (x86)\Steam\SteamApps\common\Call of Duty - Infinite Warfare\players2\settings.zip.iw7 (default location). This is not a regular text file, but a file in HEX format. To edit the sensitivity in HEX format, you first need a HEX editor. Notepad++ (version 6.8.X, not out for 7 yet) has a HEX editor plugin that's free, and a paid option is UltraEdit. To install the plugin in Notepad++, go to Plugins -> Plugin Manger -> Show Plugin Manger, scroll down to "Hex-Editor", check the box and click install. Once installed, open the file, and press Ctrl-Alt-Shift-H to switch to HEX mode. If you're unfamiliar with the hexadecimal system, it goes 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, a, b, c, d, e, f. Uppercase or lowercase letters are irrelevant, they have the same value. UltraEdit will show the cursor position in HEX format, but Notepad++ will not, it will show the line and column. Unfortunately the position of the sensitivity is not fixed, so you have to manually find it in your file. If you have both horizontal and vertical sensitivity set to the same, it should be quite easy. It will most likely be towards the bottom of the file, and you are looking for two identical 4 byte blocks divided by 2 bytes. In UltraEdit, the position for the sensitivities in this example are byte d8b, d8c, d8d and d8e for horizontal sensitivity and byte d85, d86, d87 and d88 for vertical: In Notepad++ you can see the line number in HEX on the left, but not the position in HEX. So the sensitivities are all on line 217, horizontal in column 12, 13, 14 and 15, and vertical in 6, 7, 8 and 9. The calculator only calculates the sensitivity for horizontal movement, but enter the same value for the vertical sensitivity to make them feel the same. Join the community on Discord!
November 6, 20169 yr Author Wizard Your calculator drifts out the tiniest bit, by the time I reach 15 sensitivity in a prior CoD, it is 16 sensitivity in IW. Maybe it's because the new sensitivity slider is for 80 FOV 16:9 instead of 65 FOV 4:3. Are they actually using a different formula for the sensitivity and FOV scaling? Yes it's a different scaling, but I don't have it perfectly calculated yet. It is 99.999% good (as your numbers show), but needs a little tweaking for all CoD game to be perfect. Join the community on Discord!
November 6, 20169 yr I don't know how you figure this stuff out but bravo!!! Thanks for all the hard work!
November 6, 20169 yr So nice of them to make it easy to match mouse sensitivity.... I was trying to move the dam slider whilst looking through a microscope.... checking my 360 each time. At least I can revert back to my normal dpi after editing. - V I E W S P E E D - Unifying Crosshair Speed
November 6, 20169 yr The new notepad++ doesnt support hexeditor? - V I E W S P E E D - Unifying Crosshair Speed
November 6, 20169 yr Author Wizard The new notepad++ doesnt support hexeditor? Perhaps, I'm on an older version (6.8.3). Maybe it isn't out for version 7 yet. Join the community on Discord!
November 6, 20169 yr Author Wizard Since they changed the FOV to 16:9 recently, I would assume the sensitivity that you configure is for 80 FOV 16:9 (64.37) instead of 65 FOV 4:3. In COD 4 with 1.00 sensitivity, setting the FOV to 64.37 results in the sensitivity being 0.987910. Hopefully that helps your calculations in some way. http://i.imgur.com/yvRXYZw.jpg I figured out what the CoD games do now, they match the sensitivity at 0% monitor distance between FOV's. Need to update the formulas, but it will be perfect when I'm done Join the community on Discord!
November 6, 20169 yr Author Wizard mouse rate is 1.569686 but the calculator says it is 1.571160. In COD 4 with 1.00 sensitivity, setting the FOV to 64.37 results in the sensitivity being 0.987910. Hopefully that helps your calculations in some way. Fixed all the older CoD games now (MW 1, 2, 3, AW and Ghosts), check again and see the perfection IW is a little different though, still working on that. BO3 also has a default FOV of 80, so it's probably the same as IW. Join the community on Discord!
November 6, 20169 yr Author Wizard Very nice. Converting from CoD to other Quake engine games is still way out though. I'm pretty sure CS:GO, Quake Live, etc use the exact same sensitivity as CoD. For example I put 1.00 sensitivity, 90 FOV for CoD and then convert to CS:GO and it gives me 2.092914 which is way, way too fast. If I convert between CoD instead, and reverse the scaling by doing 90 FOV to 65 FOV, it gives me 1.569686, which is correct for CS:GO, Quake Live, Black Ops 1&2, and World at War in my 180 swipe tests. Thanks for the check. I used the res based FOV in the calculation instead of the 4:3 one. Should be better now Join the community on Discord!
November 6, 20169 yr Author Wizard The calculator broke. What would I do without you? Fixed it! I'll look into the aims. Join the community on Discord!
November 6, 20169 yr Really appreciate the work. it would be great to be able to compare cod ADS to other games. iv been using my own way of monitor distance matching but a calc would be sweet. - V I E W S P E E D - Unifying Crosshair Speed
November 6, 20169 yr i changed the same values and everytime i load up the game they get reset back to default values. Note: desktop to Infinite warfare calculator options, Edited November 6, 20169 yr by DNAMTE - V I E W S P E E D - Unifying Crosshair Speed
November 6, 20169 yr Author Wizard edit: My address is different. Changed those and it works. Damn, so the address is not fixed It should be towards the end of the file, and you should see the pattern with 4 equal bytes (if horizontal and vertical is set to the same) divided by "42 05" at least. Join the community on Discord!
November 6, 20169 yr Just to confirm. As glisn stated before using the calc from desktop to infinite warfare provides an invorrrct hex value. If you go desktop to advanced warfare then AW to IW it works great. My address was in the same spot as glisn. Thanks for the work i can use my normal DPI again! - V I E W S P E E D - Unifying Crosshair Speed
November 6, 20169 yr Just to confirm. As glisn stated before using the calc from desktop to infinite warfare provides an invorrrct hex value. If you go desktop to advanced warfare then AW to IW it works great. My address was in the same spot as glisn. Thanks for the work i can use my normal DPI again! Can you please explain how do i do it? I can't seem to wrap my head around it. It ends up resetting the values everytime. I'm trying to get the same sensitivity as i use in Overwatch. Much appreciated thanks!
November 6, 20169 yr Hmm, I did everything right and the sensitivity is a little bit off, a little bit faster than from BO3, I have 0% - 0cm discrepancy. BUT it is a bit faster, if I lower my dpi for a 100, it's still too fast, but -200dpi and it's too slow. Seems like the calculator isn't 100% correct.
November 6, 20169 yr Doing good work, looking forward to more updates on CoD IW. Will the hex edit also work with lower sensitivity results than "1" and will it stay or does the game reset it? Edited November 6, 20169 yr by M K_2384
Create an account or sign in to comment