Leaderboard

Time to convert! So where do you start? First of all, do you want to calculate the sensitivity for a game based on a 360 distance, or do you want to calculate the 360 distance and sensitivity based on existing settings? A key point either way is that all the sensitivity calculations for hipfire (for the output game) and aims (for both games) will be based on the hipfire or distance for the input game. For this reason it is highly recommended that you always use the same source for all your calculations to maintain the best consistency. All numbers and selections in these instructions are examples only, you need to find the correct ones for your games. Using distance as input Select "Distance" in the "Convert from" dropdown, and enter the 360 distance you want in the "Distance" box. This distance will either be inches or centimeters depending on you unit selection. Select a game and aim, enter your DPI and set the special options (if any) to match your settings. Make sure the resolution is the same as you are using, and input the FOV as you have it configured in the game. Finally select the location you want the sensitivity calculated for if there are multiple options. If you select an "All" aim, the hipfire sensitivity will be calculated to match the distance, while all the aims will be matched to this hipfire sensitivity using the conversion methods in the setup. If you select an ADS or scope aim, the calculation will show you the sensitivity for this specific aim to be the distance you input. Converting to a game is the same for both distance and sensitivity input, so that will be covered in the next section. Using sensitivity as input The most common way to convert sensitivity is by using the settings from a game you are happy with the sensitivity in, so you want this transferred to other games. Start by entering all the settings from the game you want to use as a source, then select an output game and fill in the necessary information. FOV is again very important to get exactly right, either enter the FOV exactly as you have it in the game, or calculate the FOV and configure it in the game. In the this example the FOV's of the games are matched, which is highly recommended when it is possible. But for games with a very narrow FOV range or no FOV options at all, beware that everything is matched to hipfire of the input game, so in this case: The Targeting and Scope sensitivity in Fortnite are not matched to Fortnite hipfire, but CSGO hipfire. This way the scopes will feel the same as in CSGO which is what you want for consistency.