DPI Wizard

MDV 0%, it's basically the opposite of this you mean I guess (you move and the target stays still):

Set the sensitivity in the console for best accuracy. View full update

Serious Sam 4 is in the works!

70 in the config is 56 hdeg 4:3 and 110 in the config is 90 hdeg 4:3 and it scales linearly between those two points.

PM sent!

It's not actually Hdeg 16:9, it's a multiplier based on Hdeg 4:3 to almost mimic Hdeg 16:9. That's why there's a slight difference.

Yes, but since you are converting using "All" the main adjustment is done in the "Look Sensitivity" value which goes from 2.1 to 0.2. The targeting sensitivity is a multiplier to the look sensitivity, so it's still unable to adjust it to your preference. If you instead keep 2.1 and set the DPI to 5000 it would work: https://www.mouse-sensitivity.com/?share=fcf773a6154e9ce47dca3b53377f18c8 But this obviously makes the look sensitivity wrong so you need to have a DPI switch when targeting for this to work properly.

Everything seem to be correct with this game, what in particular is not working for you? Note that changing FOV seems to require you to restart the game to take effect.

Sending you a PM!

That would be great! Sending you a PM.

Yes, thanks! I'll have a beta page up soon where you can check it

Sent you a PM!

Excellent, sending you a PM!

No, that would be terrible, especially for the powerful scopes. They would be insanely sensitivity and practically impossible to aim with. What you get with those settings is the same tracking speed for all scopes: This would be the same 360 distance, but it's a different setting for each scope, and for many of them it's not even possible since it requires a sensitivity out of range: https://www.mouse-sensitivity.com/?share=a961ca584af0818a5e14bdee3796bc98

0 for coefficient yes. 1 for the ADS Sens. Multiplier.

The game scales all the scopes according to your Monitor Distance Coefficient configuration, and at 1.0 they are all exactly what your coefficient is. Then you can scale high and low up or down if you prefer.

The calculator is using the real FOV of the aims regardless of their name. That table is not listing the actual magnification btw, it's listing the relation between what a hipfire FOV of 80 hdeg 16:9 is in 4:3 (64.366444) and the scope FOV in 4:3. This relation will change if you change FOV. Also it is not how optical magnification work. For example the 4.0x is listed as 2.57x, this is derived from 64.366444/25. But the true optical magnification of this scope is 2.84x if your configured FOV is 80. If your FOV is 120 however, this is suddenly a 5.86x scope. And at FOV 100 it is actually a 4x scope.

Here's an example on how you should translate a game. Copy the game data text from this page and use the "Paste as plain text instead" (or paste with CTRL-SHIFT-V on Windows) to avoid messy formatting. Add a dash to the end of the lines you want to translate and enter the translation. Just leave any lines you aren't translating as they are. Some lines might be identical, you only need to translate one of them. Even if it's just the game name you have a translation for that is really useful! ------------ Game: Crossfire HD - 穿越火线高清竞技大区 Aims: All Hipfire Scope In-game sensitivity location: Settings -> Controls -> FPS Mouse Sensitivity - 设置 -> 控制 -> FPS鼠标灵敏度 Sensitivity 1 (99 is just a sensitivity value placeholder, translate around this): General Sensitivity 99 - 一般灵敏度 99 Multiplier 1 (99 is just a multiplier value placeholder, translate around this): Scope Sensitivity 99 - 开镜鼠标灵敏度 99 FOV (99 is just a FOV value placeholder, translate around this): Field of View 99 FOV Notes (if you get multiple identical lines you just need to translate one of them): Not possible to adjust.

The framework for translating the entire calculator is finally done, and your help is needed! Any language is welcome as long as it makes sense to translate to it. There's two parts to this translation. Calculator translation Part 1 is the calculator itself. This part consists of about 240 lines of words and phrases that needs translating. For consistency and to keep it manageable this part needs to be translated by a single person with knowledge of relevant words and phrases (i.e. gaming related terms etc). Send me a message if you want to translate. Anyone helping with this part will get a small compensation as a thank you. As soon as someone is translating a language it will be shown as "In progress" so no more help will be needed for that language at the moment for this part. Chinese translation done! Russian translation done! French translation done! German translation done! Spanish translation done! Brazilian Portuguese translation done! Japanese translation in progress! Italian translation done! Polish translation in progress! Korean translation in progress! Turkish translation done! More languages are welcome! Game translations Part 2 is translating game names, aim names, settings and other stuff for specific games. Anyone can partake in this, just go to this page and select the game, then all data for that game will be shown. Copy it into a post here with the translation (or send me a PM if you want). See the post below this one for an example. Common questions regarding the translation Do the abbreviation if it's a term understood in your language. When you have reached the maximum of saved entries a box will pop up telling you that you need to delete entries to add more. So the this popup box only have one button to close it that says "Got it" as in "I understand" or "ok". Path as in folder path on the computer where the config file is located: Counts is a bit tricky, it refers to one unit of movement from the mouse and can be used in the same manner as centimeters or inches. DPI (Dot Per Inch) is technically wrong, it's actually called CPI (Counts Per Inch). So if a mouse is set to 800 CPI is sends 800 count for every inch moved. A lot of languages probably lacks a proper word for this. Here is an example of the context:

It's not bugged, it's the game that lacks the range to match your preference. At 100 (which is max) it's already really slow compared to hipfire.

It only does that if you calculate horizontal hipfire for in-game sensitivity. If you do the "All" conversion it will instead use the default values and adjust the sensitivity with the MouseSensitivityMultiplierUnit since it's way more accurate.

No, you don't need to change it unless your calculation is out of range. Using the default value will work perfectly fine in most cases.

They probably keep it in for a couple of reasons I can think of; to read the old value and convert it to new, and while they had the test server up the same config file had to work with both versions. When you convert to any aim that have more than one value, you have to provide an existing value to the calculator. It will in most cases fill in the default value as a placeholder since it can't know what your value is. Just replace this placeholder value with your actual value if it isn't correct. Using the "All" aim will calculate several of these values for you, so it's generally recommended to use this. But even with the "All" conversion you have to provide some existing values, but the default values will work fine in most cases.