Search the Community

I was confused at first but then I found out that the calculator changed the native resolution from 1920x1080 to 1926x927 which caused the HFOV to display as 111 even tho I set it to 103. Manually setting the resolution solves the problem. It's easy to forget tho.

I'm trying to convert Titanfall 2's sensitivity to F.E.A.R. and the webpage hangs for me. It just does not update and it's almost like it has frozen. Converting to other games is fine but it only happens to F.E.A.R. from what I've seen, so I'm submitting this as a bug report!

Hi, I purchased a subscription hoping I could get some support calculting CSGO to Modern Warfare 2 / Warzone 2.0 When scoped in with a sniper rifle I want the sensitivity to be exactly like the first and second zooms of an awp, first below or equal to a 8.0x zoom, second greater than or equal to this. I am dissapointed that the calculator suggests I cut the zoom sensitivity. Doing manual testing with a ruler the right value should be somewhere between 1 and 1.5 zoom multiplier using a monitor distance coefficient of 1.33. I am using a DPI of 800 a 16:9 screen, a zoom_sensitivity_multiplier of 1 in CSGO and a sensitivity of 1 in CSGO. Similarly my hipfire (nomal) sensitivity in Warzone is 3.33. Can I kindly ask for some support in this as the zoom sensitivity values for Modern Warfare are blatently wrong. I have found it very difficult to find the right information to assist with this issue. The results of the output are below, I don't know why the calculator chooses to use the 0.82 zoom_sensitivity_ratio_mouse when I want it to use the default value of 1.

In the instructions it says that games supporting Monitor Distance Coeffiecient automatically add the fitting placeholder value. Using the exact same games/inputs of the example shown in the instructions (see pic) I can not get a placeholder value of 133.33 to appear, it just stays blank. Am I doing something wrong or was this changed?

noticed this happening the past couple of days whenever i open the site it does not properly load my saved values , works fine after reentering a value https://www.mouse-sensitivity.com/?share=300688773e0886306acd33aa881a2a73 @DPI Wizard

So I've been trying to figure out what the CM/360 of an old shooter I used to play was. The game was called Alliance of Valiant Arms (it's not online anymore). I still had the settings saved, but after inputting the values I noticed that changing the aspect ratio impacted the CM/360. Changing resolution but keeping the aspect ratio was fine though. Is that intended? I tried many of the other shooters I play and for none of them it seems to be the case that aspect ratio affects this. Now I'm just confused.

Converting to Minecraft outputs a higher than equal sensitivity. Flicks FAR overshoot their target, I have not experienced this in any other converted sensitivity.

Rust released an update changing the way FOV now works when ADS. It is now proportional to your normal FOV.

Changing the FOV to 90 in game will result in a different multiplier than the one on here.

I have no idea why but almost every update Warframes 360* calculation changes. Matching everything in the calculator, the in game rotation is off. I don't know if this is a bug or just the games weird FOV making the 360* rotation different. Please any help would be appreciated

So I was trying to convert from Overwatch sens to Warframe, and then I saw that with whatever way I convert with it tells me that my new max dpi (850) needs to be higher then what I currently have (800)... Even if I change the dpi in the destination as it tells me. My settings: Overwatch 4.2, 800 DPI Warframe 78 FOV

See attachment 2018-10-14 23-44-15.mp4

@DPI Wizard So when I create a profile in the Calculator Settings and I save it with a different WPS option other than 6/11, when I go to load it again or even just refresh the page, it reverts back to 6/11. It''s a small bug but it's really been bugging me. I've had this problem for a while, and I thought I might as well point it out. Here is a gif showing exactly what happens:

So, I was trying to use the calculator today, and setting sensitivity for Battlefield 1. The Uniform Soldier Aiming Coefficient is set to the default 1.33, but if I try to set it to 0, it just uses 1.33. Works OK for other numbers, just 0 seems to be broken.

the value suggested for the config file is now incorrect due to the latest updates to the game, for example in the config file my suggested value is 00 00 c0 ff and ingame it's suggested to use a value of 16 on the slider. however, using the suggested hex edit, up/down and left/right are flipped. the ingame value still seems correct, so my guess is either the calculated value is wrong, or the instructions on where to locate the desired address range is wrong and needs to be updated. also on a side note subnautica now has a FOV slider and my suspicion is a value in the config file as well.

Hello, unfortunately I cannot use this site's calculator in chrome for some reason. It wont let me select a game and it gives me this error: chrome://version Google Inc. Copyright 2017 Google Inc. All rights reserved. Google Chrome 55.0.2883.87 (Official Build) m (64-bit) Revision ad0be09aa3ca814168d079b52825f6f80e22f0e8-refs/branch-heads/2883@{#723} OS Windows JavaScript V8 5.5.372.32 Flash 24.0.0.186 User Agent Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Command Line "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --flag-switches-begin --flag-switches-end Executable Path C:\Program Files (x86)\Google\Chrome\Application\chrome.exe Profile Path C:\Users\Atemu\AppData\Local\Google\Chrome\User Data\Default Variations 6a89113b-a7aa8ed 90757ebb-3f4a17df 3095aa95-3f4a17df 8364a5c2-ca7d8d80 7c1bc906-f55a7974 2a33b90e-3d47f4f4 ba3f87da-45bda656 f15c1c09-ca7d8d80 9e201a2b-ca7d8d80 5274eb09-3f4a17df 5e3a236d-4113a79e 93731dca-3f4a17df 9e5c75f1-c16ec2e6 6b121ae7-ca7d8d80 f5dd6118-2f5721af f79cb77b-3d47f4f4 b7786474-d93a0620 868bda90-ca7d8d80 4ea303a6-ecbb250e 7aa46da5-669a04e0 fe9bec35-186f5907 9736de91-ca7d8d80 69bf80fa-f23d1dea 867c4c68-ca7d8d80 b2f0086-93053e47 99c41f12-3f4a17df 6844d8aa-669a04e0 f47ae82a-86f22ee5 3ac60855-486e2a9c f296190c-72d8285f 4442aae2-e1cc0f14 ed1d377-e1cc0f14 75f0f0a0-e1cc0f14 e2b18481-6754d7b7 e7e71889-4ad60575 828a5926-ca7d8d80 Compiler MSVC 2015 (PGO) Idk what I could do, I already reinstalled chrome.

Hello. Tom Clancy's Rainbow Six Siege doesn't work normally several days ago. This game has three settings. But only MouseYawSensitivity is calculated without MouseSensitivityMultiplierUnit. I can only input Sensitivity1(MouseYawSensitivity). Multiplier1 doesn't work. Would you fix it?

My CS: GO Sensitivity: 1.22 DPI: 650 Monitor Size: 24 in. The problem is that the sensitity is zero which does not work in the options.