DPI Wizard

This is correct, since hipfire is affected by the coefficient, when you change FOV the game will automatically scale accordingly. The same goes for the max discrepancy, everything scales according to the FOV.

I can't find anything changed at first glance, what exactly doesn't match up for you?

There's a lot of games where you have to provide an existing sensitivity value to the calculator, since only one value can be calculated for each aim. The issue with this game in particular is that the monitor distance coefficient affects hipfire, so we need to know two values before it can be calculated, the coefficient and the general mouse sensitivity. The main culprit is the lack of decimals though, if the game supported 6 decimals or more this wouldn't be an issue.

If you mean the sensitivity values, that's because everything that is a scope has a completely different scaling than the ADS aims.

This is an existing value you have to provide to the calculator (in the "Sensitivity 1" field of the input game), it is not being calculated. You can change it from the default of 3 to perhaps increase the accuracy, as the game lacks a lot of decimals. I.e. try to set it to 1, 1.2, 1.3 etc to see if the discrepancy (as indicated by the color, red in your screenshot) gets better.

Fragsurf is added.

All zoom levels use the same sensitivity setting, choose the sensitivity for the zoom level you prefer to be matched. View full update

The last link includes everything.

This will be a mix of different methods, but here the hipfire is matched using Monitor Distance Horizontal 100% which will preserve the movement to the edge of the monitor, while the aims are the same as you have them in R6: https://www.mouse-sensitivity.com/?share=d7830c923f251ca32532f95c225b96d4

Is your aim sensitivity in R6 50 for all scopes?

100% will be quite a bit faster, but make sure to select the same axis for hipfire, ads and scope. Since the FOV in Fortnite is so low, it's basically like a 2x in R6, which is why it feels so slow when using monitor distance.

Updated the naming of some variables, other than that the English and Chinese clients are the same.

Verified that this is the same as the Chinese version, updated the naming of some variables.

Without seeing your conversion it's hard to tell if you are doing something wrong, but when you convert using Monitor Distance from R6 where you likely use a very high FOV to Fortnite which is locked to a very low FOV, there will be a significant difference in 360 distance. But the monitor distance you use in the conversion will be the same.

Already added based on the Chinese version. Will check for differences when the playtest starts.

Added.

Mecha BREAK is added!

Added with support for all striker settings! View full update

Thank you! It's really rewarding to see that my work and the contribution of these extremely knowledgeable members (plus more) has helped you getting the settings right. I strive to make all the sensitivity and FOV conversions perfect, so it's good to know someone is benefitting from it. FOV is probably an overlooked aspect, as when it isn't a standard method like vdeg or hdeg (either based on a fixed or actual aspect ratio), it can be very complicated to get right (or at least know what it is if it's not in the range your want). Cheers Have a great weekend!

They were linked to the original hidden post, so that's why they failed. I've re-uploaded them directly to this post now You have to be signed in though.

So here are the three steps required to calculate this! Step 1: Convert from your source to Brutal John hipfire: Step 2: Copy the decimal sensitivity value, then convert from your source to the "ADS (Decimal)" aim using the copied value as sensitivity 1: Step 3: Copy the aim sensitivity from the output, then convert from "ADS (Decimal Single)" using the copied value, to "ADS (Hexadecimal)" to finally find the hex value for the registry: Make sure to use the same FOV for Brutal John in every step, and disregard the distance calculation in the last step as the only thing we're after here is the hex value.

Actually I mixed this game with another one, the issue here is that the code currently does not support two hexadecimal inputs, which is needed in this case as the aim is a multiplier of hipfire. I'll see if I can a sort of workaround that requires multiple steps.