DPI Wizard

That probably means it uses 0% as a default, but others who know for a fact might chime in. I will analyze it and add it next!

To a certain degree, but for precision on the entire monitor in 3D a 3D trainer with the same FOV as the game you aim to be good at is best. 2D to 3D can only be perfectly converted to one specific movement and not over the entire monitor.

Updated with all weapons. View full update

Done!

No, just the sniper scope as far as I know. Haven't tried many other weapons yet though.

Try using 360 distance for hipfire and Viewspeed (v1) for the scopes.

Only if you then have 1000 DPI for Overwatch and 800 for Paladins. If you increase both to 1000 the only thing that changes are the distance calculations. Remember that the sensitivity represent a specific amount of counts/degree. 2 in Overwatch = 27272.27 counts/360 degrees. When you increase DPI from 800 to 1000 you only change the physical distance to move this amounts of counts from 34.0909 inches to 27.2727 inches. The same goes for Paladins, if you are converting 360 distance you get 1.441792, which again equals 27272.27 counts/360 degrees. And as long as the Paladins DPI is the same as the Overwatch DPI the sensitivity calculation remains exactly the same.

If you have the same DPI for both games, changing the DPI will have no impact on the calculated sensitivity. Note that the DPI for the input game will be copied to the output game unless you have specifically entered a DPI for the output game. If you have different DPI settings for the games, changing either of them will result in a different calculation.

The irony is that Fortnite used to have the sensitivity in the config file in plain text with 6 decimal accuracy. The removed it a few months ago for some unknown reason. It works by uploading the config file to Epic's cloud, which then is used by the game. So you need to enter your account details into the third-party program for it to access your cloud files. I haven't heard of any issues with account details being lost (the program is open source so people can check the code for malicious content) or Epic banning people for editing the file, and I have used it extensively myself. But things can change so use it at your own risk.

It should be the same as 100%. Haven't added it yet, but I will do it in the next update. This auto method has some quirks though, especially in that you absolutely need to use the same baseline for your conversions. For all the other methods It doesn't matter what you use as a baseline as long as they all stem from the same conversion method. I.e. with Monitor Match 75% you can convert A -> B and A -> C with the same result as B -> C (disregarding rounding limitations). This will not work with the auto mode as B -> C will yield a slightly different result than A -> C (more different the higher the FOV difference).

Select "Savefile" in the Location box for Fortnite: This will give you a new more accurate sensitivity calculation, but you need to use a third-party program to edit the file. The link to the program is in the Game Info notes (also here). Pay attention to this Location box in all games, it may include Config File, In-game, Console or Regedit. I'm not quite sure why they went with this model, but it's quite easy to use at least. All the sensitivities do exactly the same math-wise, but is affected by the FOV of the different scopes. In other words, if you set all the sensitivities to the same value, you will have a 100% Monitor Match sensitivity. CSGO is by far the most used baseline actually. You might have a different preference for 3rd person though. Even with everything equal (FOV and 360 distance) 1st and 3rd person might not match up to your liking, you might prefer one of them slower or faster.

In your first conversion there's a -7.378% discrepancy due to the lack of decimals in the Fortnite sensitivity. In the second conversion to the scope the discrepancy is only -0.0114% because the lack of decimals can be countered by the scope multiplier to get it more accurate. Both these discrepancies are showing you the difference between CSGO and Fortnite. In the last conversion however you are converting from the Fortnite sensitivity that is -7.378% off compared to CSGO, and the scope sensitivity is matched to this value directly, and not the CSGO value. That why you get a ~7% difference in the conversion (0.86 vs 0.92). For Fortnite I would recommend the editor for the cloud config to set the sensitivity accurately. I hope that clears it up!

Both games have a bit of negative acceleration (mouse smoothing), and it's 1st person vs 3rd person so they are most likely gonna feel a little different even with the exact same sensitivity.

Scope is in!

Space survival added!

90 FOV in CSGO means 90 horizontal degrees in 4:3 aspect ratio. If you are using a wider AR, the extra width is added on resulting in 106.26 horizontal degrees for 16:9. And yes, 73.74 is what you need to match this in games that use vertical FOV.

Ok, so you just need to enter everything into the Input.ini file again, it is cleared after the update.

Downloading the update now, will fix it when done.

ADS and scopes are usually 0%, 75% or 100% monitor match (assuming 16:9 resolution) when there's no slider. A lot of exceptions though.

It probably is the same, but I need to verify it. Not sure about console, will check it.

Simple mode is just that, simple. A lot of options are removed/pre-selected to make it simpler, so it naturally comes with some limitations. Hence it is not a replacement for advanced mode, and since a lot of options are missing some conversions are not available. I will look into adding the special option(s) to the simple mode to allow for more usability, or another way of adding the possibility to change perspective mode etc.