DPI Wizard

For Rainbow Six and a few other games, you need to enter one or more sensitivity values for the calculation to work. This is because the sensitiviy is a product of several variables. You can enter enter the default value if you haven't changed it. The output shows you what value you need to enter, and the accepted range: Enter sensitivity 1 (MouseYawSensitivity=[1-100]) The Multiplier 1 value (MouseSensitivityMultiplierUnit) will then be calculated based on this number.

You need to enter the value of your MouseYawSensitivity in the box, and the correct multiplier will be calculated.

Check your pm!

View full update

This is a perfectly fine conversion to test, and should work. If you try with 1.01 it works like it should. What happens here is propably a small discrepancy due to rounding, making the calculated number something like 0.99999, thus too low. I'll look closer into exactly what's going on here.

When converting to and from 2D, 360 distance and monitor distance 100% is the same. Since osu! plays on a 4:3 part of the screen, you can use monitor distance 75% to match the movement to edge of the osu! play area. Viewspeed 1 and 2 will be very close as well.

They did. Really amazing.

Yes, it just expires when the gift card is depleted.

FOV is the same.

You can use the default values of 50.

No, they are currently divided into the tags above which should be fine. What I'm wondering about is what you guys see as the most universal conversion methods between the different tags. For instance from Normal 1st person to scope, what should be used as default? 75% monitor distance, viewspeed 1, viewspeed 2, 0% monitor distance?

Since the calculator is getting more and more complex, a simple mode is definitely needed for a lot of users. For this to work, a lot of decisions have to be made default, and I need some feedback here. Here's the most likely options that will be hidden and pre-selected in the simple mode: Input mode: Sensitivity All sensitivity and multiplier options that do not need to be calculated will be set to the default values. Special Options will be set to a pre-selected one. WPS will be set to 6. FOV Type will be set to the game's default. Location will be set to in-game where available, then config file. So all these options will be forced and not shown to simplify the layout. Now for the part I need some input with. For the calculations to work, a pre-selected conversion method must be hard-coded. All aims are already tagget with either Normal (i.e. Hipfire or Default), ADS (up to 1.25x), Scope or Desktop. Normal is also differentiated by first person and third person. So we end up with a table like this (MD = Monitor Distance): From \ To Normal FPP Normal TPP ADS Scope Desktop Normal FPP 360 Distance 360 Distance 75% MD 75% MD 100% MD Normal TPP 360 Distance 360 Distance 75% MD 75% MD 100% MD ADS 75% MD 75% MD 75% MD 75% MD 75% MD Scope 75% MD 75% MD 75% MD 75% MD 75% MD Desktop 100% MD 100% MD 75% MD 75% MD 100% MD So my question is how would you fill out this table to be best suited to work for "everyone" (i.e. not you specifically)? What I've filled out is just an example. Any monitor distance or viewspeed is accepted.

Done

The default setting is the same as desktop. Other than that, it's not easy to match this game to anything because of how the game mechanics work. I have the formulas though, but it doesn't make much sense compared to other games.

If you use Viewspeed or Monitor Distance, the 360 distance will be different. The difference depends on the FOV, since these methods only match what you can actually see on the monitor.

Hi! If you select "In-game" as location for Fortnite, you will get the scopes as well. For scope to scope conversion, do not use 360 distance. Try Viewspeed or Monitor Distance. Edit: Unless you are talking about Save the World mode, where there is no scope sensitivity currently in the game. The ADS calculation is the closest you get.

Seems to be correct, what exact values are you using?

I'll verify it. Are you setting the same FOV in Aim Hero as in OW?

I'll change things around a bit, the template for the light colors was using yellow by default. Blue sounds better indeed!

No, not for the in-game sensitivity. The LastConvertedMouseSensitivity value in the config file works like this however, where 0.025 @ 800 DPI is the same as 0.05 @ 400 DPI.

I will make a basic and advanced version in the next major release

Yes, USA is a great feature to use. You can convert from BF1 4x to PUBG 4x fine, but note that they do not have the same FOV even though they are both 4x.

I kinda forgot it was there It is already based on AR ADS, but you do not have a separate sensitivity for it in the game. It uses the same settings as hipfire, so use this calculation if ADS is more important than hipfire/360 to you.

Hipfire and 1X in BF4 are not the same in terms of 360 distance with default settings. They are close however if you use Scaled ADS or default FOV, but very different with high FOV and Scaled ADS off. Scoping in PUBG has a fixed FOV of 70, so it's a bit narrower than the default in BF4 which is 79.32 (assuming a 16:9 monitor). So you could either match 1X in BF4 directly to scoping in PUBG using 360 distance, or try one of the FOV based methods like Viewspeed or Monitor Distance (75% is the same as the default USA 1.33 in BF4).