Jump to content


Photo

Call of Duty: Infinite Warfare


  • Please log in to reply
69 replies to this topic

#1 DPI Wizard

DPI Wizard

    Advanced Member

  • Wizards
  • 1,987 posts

Posted 06 November 2016 - 01:42 AM

299
300


#2 DPI Wizard

DPI Wizard

    Advanced Member

  • Wizards
  • 1,987 posts

Posted 06 November 2016 - 01:39 AM

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:

hexultracod.png

 

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.

hexnpcod.png

 

The calculator only calculates the sensitivity for horizontal movement, but enter the same value for the vertical sensitivity to make them feel the same.


  • Drimzi likes this

#3 Drimzi

Drimzi

    Member

  • Premium Members
  • PipPip
  • 114 posts
  • LocationNew Zealand

Posted 06 November 2016 - 02:04 AM

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?

 

I noticed the calculator is a tiny bit out for the prior CoDs anyway compared to what is shown in Call of Duty 4 when using the console command "cl_showmouserate 1" and "cg_fov xx" and then moving the mouse with the extended console open "shift + ~". For example, 1.00 sensitivity and 90 FOV, CoD 4 will say the mouse rate is 1.569686 but the calculator says it is 1.571160.


Edited by Sintek, 06 November 2016 - 02:18 AM.

| Logitech G900 | 1400 DPI | 3/11 WPS | 2560x1440 | Viewspeed Matched |


#4 DPI Wizard

DPI Wizard

    Advanced Member

  • Wizards
  • 1,987 posts

Posted 06 November 2016 - 02:21 AM

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.



#5 Drimzi

Drimzi

    Member

  • Premium Members
  • PipPip
  • 114 posts
  • LocationNew Zealand

Posted 06 November 2016 - 02:36 AM

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


Edited by Sintek, 06 November 2016 - 02:42 AM.

| Logitech G900 | 1400 DPI | 3/11 WPS | 2560x1440 | Viewspeed Matched |


#6 luxa_pan

luxa_pan

    Newbie

  • Premium Members
  • Pip
  • 1 posts

Posted 06 November 2016 - 02:56 AM

I don't know how you figure this stuff out but bravo!!!  Thanks for all the hard work!



#7 DNAMTE

DNAMTE

    Assistant Wizard

  • Premium Members
  • Pip
  • 79 posts
  • LocationAUSTRALIA

Posted 06 November 2016 - 02:57 AM

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


#8 DNAMTE

DNAMTE

    Assistant Wizard

  • Premium Members
  • Pip
  • 79 posts
  • LocationAUSTRALIA

Posted 06 November 2016 - 03:50 AM

The new notepad++ doesnt support hexeditor?


- V I E W S P E E D - ​Unifying Crosshair Speed


#9 DPI Wizard

DPI Wizard

    Advanced Member

  • Wizards
  • 1,987 posts

Posted 06 November 2016 - 03:52 AM

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.



#10 DPI Wizard

DPI Wizard

    Advanced Member

  • Wizards
  • 1,987 posts

Posted 06 November 2016 - 04:18 AM

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 :)


  • Drimzi likes this

#11 Drimzi

Drimzi

    Member

  • Premium Members
  • PipPip
  • 114 posts
  • LocationNew Zealand

Posted 06 November 2016 - 04:37 AM

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 :)

 

Awesome!

 

Modern Warfare Remastered is exactly the same as Advanced Warfare. Sensitivity 1 - 30, but it is not a slider, it is like consoles where you select 1, 2, 3, etc. The campaign is locked at 65 FOV and Multiplayer goes to 90 FOV. It uses the 4:3 FOV.

 

The FOV in the config is seta 0x8572B2C7 "90". If you try add it to the campaign config, it deletes it.


Edited by Sintek, 06 November 2016 - 04:55 AM.

| Logitech G900 | 1400 DPI | 3/11 WPS | 2560x1440 | Viewspeed Matched |


#12 DPI Wizard

DPI Wizard

    Advanced Member

  • Wizards
  • 1,987 posts

Posted 06 November 2016 - 05:27 AM

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 :D

 

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.



#13 Drimzi

Drimzi

    Member

  • Premium Members
  • PipPip
  • 114 posts
  • LocationNew Zealand

Posted 06 November 2016 - 05:49 AM

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 at 90 FOV.

 

edit: I changed both CoD and CSGO to 50 FOV and did another 180 swipe test to check if it scaled correctly. CSGO was much faster. Your calculator gave 1.333333 when converting from CoD 65 FOV to CSGO 90 FOV and that value was correct for the rough 180 swipe test. I then checked 120 FOV in both games, and CoD was much faster this time. They scale the FOV differently.

 

edit edit: The new calculator is perfect. I guess CS:GO just doesn't scale the sensitivity the same way when changing the FOV, still have to change the sensitivity according to FOV. Converting from CoD 50 FOV to CSGO 50 FOV gives 1.317522 which is perfect.


Edited by Sintek, 06 November 2016 - 06:03 AM.

  • DPI Wizard likes this

| Logitech G900 | 1400 DPI | 3/11 WPS | 2560x1440 | Viewspeed Matched |


#14 DPI Wizard

DPI Wizard

    Advanced Member

  • Wizards
  • 1,987 posts

Posted 06 November 2016 - 05:58 AM

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 :)



#15 Drimzi

Drimzi

    Member

  • Premium Members
  • PipPip
  • 114 posts
  • LocationNew Zealand

Posted 06 November 2016 - 06:16 AM

The calculator broke.

 

EPpGecX.png

 

By the way, you could possibly add some Aim Down Sight presets to the calculator. For all CoD games, it has consistently been 50 FOV for Assault rifles and 55 FOV for SMGs iron sights. The other guns and sights vary a bit across games. All FOV values for the weapons are here: http://denkirson.pro...ttachment-stats


| Logitech G900 | 1400 DPI | 3/11 WPS | 2560x1440 | Viewspeed Matched |


#16 DPI Wizard

DPI Wizard

    Advanced Member

  • Wizards
  • 1,987 posts

Posted 06 November 2016 - 06:21 AM

The calculator broke.

What would I do without you? :D

 

Fixed it!

 

I'll look into the aims.



#17 DNAMTE

DNAMTE

    Assistant Wizard

  • Premium Members
  • Pip
  • 79 posts
  • LocationAUSTRALIA

Posted 06 November 2016 - 08:17 AM

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


#18 Drimzi

Drimzi

    Member

  • Premium Members
  • PipPip
  • 114 posts
  • LocationNew Zealand

Posted 06 November 2016 - 08:33 AM

I tried to do this hex edit but I don't think it is correct for my file. I have an empty sensitivity slider for both horizontal and vertical, so the config file should have the same value for both, but they are different. I don't know what to do lol.

 

edit: My address is different. Changed those and it works.  :D

 

ErXOR4J.png


Edited by GLiSN, 06 November 2016 - 10:22 AM.

| Logitech G900 | 1400 DPI | 3/11 WPS | 2560x1440 | Viewspeed Matched |


#19 DNAMTE

DNAMTE

    Assistant Wizard

  • Premium Members
  • Pip
  • 79 posts
  • LocationAUSTRALIA

Posted 06 November 2016 - 09:50 AM

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 by DNAMTE, 06 November 2016 - 10:25 AM.

- V I E W S P E E D - ​Unifying Crosshair Speed


#20 Drimzi

Drimzi

    Member

  • Premium Members
  • PipPip
  • 114 posts
  • LocationNew Zealand

Posted 06 November 2016 - 10:34 AM

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,

 

Going directly from Windows/Desktop to IW using the monitor distance calculator seems to produce an incorrect value. It resets back to 00 00 a0 40.

 

Go from windows/desktop to CoD AW first at the FOV you want, then convert CoD AW 360 to IW. That gets a value that doesn't reset.


Edited by GLiSN, 06 November 2016 - 11:51 AM.

| Logitech G900 | 1400 DPI | 3/11 WPS | 2560x1440 | Viewspeed Matched |





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users