DPI Wizard

Consoles man, blame the consoles!

Usually this I recon. The default FOV is probably what they developed the game for.

Yes

90 Hdeg 16:9 FOV is quite low for Apex, 90 Hdeg 4:3 (i.e. 106.26 in 16:9) is more common. Use that instead. Make sure that the config FOV in the calculator matches what you have in the games.

It's not the FOV, the difference is that the "All" conversion uses "ADS (AR, LMG, Sniper)" and not "1X Scope / ADS (SMG, SG, Pistol)" (they use the same sensitivity but are different).

It's nothing new, it's always been like this. The perfect 360 match has never been 83, but 83.33333 (1/0.6*50).

Let me just comment on this, eDPI is completely useless concept. It's only slightly relevant if you compare it in a game such as CSGO where the FOV is locked, but it can in no way be used to compare absolute sensitivity. Games have sensitivity ranges from the negatives to the thousands (including 0!), so multiplying the sensitivity with your DPI gives you a value that says... nothing

It's good that devs care about motion sickness etc, but that's easily fixed by just having a camera bob option and adjustable FOV. Reducing the FOV by 4% makes no sense, I think it's just a bad implementation. Probably something like in Apex, where a multiplier and the FOV doesn't add up.

No, the actual FOV in the calculator is correct.

My FOV didn't change with that file (had it set to 89, was still 89 after I replaced the file). If you try deleting the fov line, does it re-appear? I suspect it might be an old config line no longer in use.

Strange, I don't have this option in the file. I tried adding it manually, but it didn't do anything. Could someone upload their file?

They scale completely differently, so it's impossible to match them. Very bad game design... As for the MouseSensitivity=50, just leave it yes.

That depends, the MouseYawSensitivity and MouseSensitivityMultiplierUnit values must be the actual values you use in the game. The first one looks more correct based on your conversion.

Yes, and use the same multiplier. The ADS uses all four values, so the XFactor value will be calculated based on the other three.

The 360 distance is so different because the FOV is different, and the conversion setup is set to MDH 0%. This will match the tracking speed between the games, and not the 360 distance. If you set ADS in conversion setup to 360 distance instead you will get the same distance, but Destiny will feel a lot faster since the FOV a lot higher.

Shoulder Aim is tagged as ADS (as you can see with the blue highlight in the conversion setup), so in your example it is set to match MDH 0% and not 360 distance. That's why FOV affects it. If you set it to 360 distance instead it will work like you want to

Both of them should, or at least did, change FOV. Have there been an update to this lately?

This is the zoom sensitivity based on your settings in the calculations and the conversion setup.

Select 360 Distance in the conversion setup for ADS.

The FOV Type is not related to your aspect ratio, it is just a way of measuring FOV. But the easiest way to get the same FOV is to leave it at the default 4:3 type and use the same value as in ww2. Then they will be identical.

Just keep the FOV Type to the default value if you are using the FOV numbers from the game. Make sure that the "Config FOV" in the output matches exactly your configured FOV in the game. Using other FOV Types is for converting between different types.

If you want the same degrees, i.e. same 360 distance, that would make it insanely sensitive and probably out of range for the values.

The assault rifle scope have half the FOV of targeting, hence twice the 360 distance. Your last screenshot should work though, since the targeting FOV and R6 ADS are almost the same FOV.

No, it uses the Mouse Scope sensitivity.

Not wrong here technically, but the targeting aim from Fortnite has the same FOV as hipfire. So they are technically identical, the camera only moves closer to the character when you ADS. So it's not an ideal source for a conversion since it's basically the same as hipfire.