DPI Wizard

Sens is still the same from what I can see.

Just tested now, and no. It still reads the %LOCALAPPDATA%\Unreal Engine\Engine\Config\UserInput.ini file and applies the bEnableFOVScaling variable from it. This folder (%LOCALAPPDATA%\Unreal Engine\) can safely be deleted or renamed as far as I know, it's not used for anything.

Great info!

Awesome, hopefully the devs notice this now. For a game this popular it's amazing it's been out for 4 years without proper scope sensitivity.

Setting the FOV does work indeed, even beyond 120 It does ignore the decimals though, but that's a minor issue.

Good point, added Memory Editor to both.

Correct, it's very apparent at higher FOV where 120 in-game is barely over 114 if you measure it.

Like so, check the output for the Config FOV for Halo:

Thanks for the video! Really not showing it working though, since the numbers are so close, the sensitivity difference is only 1%. Try what I wrote and see if it still works. You need to measure exact counts with Kovaak's or something to make sure the correct sensitivity is applied. Set it up like this and it should do a perfect 360 with 1.485: For 1.5 replace in/rev with 10.8.

Try this: Make the config file writable. Start the game and set the sensitivity to 10 and apply. Exit the game. Open the config file and change the sensitivity from 10 to 0.1. Save and make it read-only. Start the game. Go into a game without checking the in-game settings. You now either have a really fast sensitivity (10) if the sensitivity wasn't applied from the file (it will show 0.1 in-game still), or really slow (0.1) if it was applied. On my system it's fast and whatever I put in the file is not applied, only visually in the menus.

Still the same issue here. The value you enter is not read by the game. For instance if you have it to 1.6 in-game, exit and set the sensitivity in the config file to 1.312272 (which is 12345 counts for a 360) and save it, enter the game and check the 360. It is still what 1.6 would indicate. And if you change any setting in the game, like change the FOV and apply the change, you'll see that the config file sensitivity is changed to 1.300000.

Google Cloud (where the site is hosted) had some SSD issues causing about 2 hours of downtime. Nothing to worry about, we didn't disappear

I've added it to the front page, no need for me to make another report as it's better to focus everything on this one

Big thanks to @Purestone for translation and access help!

It's close to 100%, but not exactly since the FOV is calculated in a weird way.

Updated some translations

I'll see what I can get done tomorrow!

I can write a technical paper describing exactly what the issue is. Where would you like the link exactly?

Added both zoom levels. And as always, a different sensitivity and FOV scaling yet again!

Hipfire and scope sensitivity added.

No, it's working like intended, but the lack of decimals and the similar scaling between the scopes makes the calculation change very little. If you convert to zoom or vehicle, make sure you enter your current hipfire sensitivity.

What is your zoom_sensitivity_ratio_mouse and fov_cs_debug values?

There's no numerical value to the slider, nor a config file. And the slider can't be moved in steps with the keyboard etc, so this one can't be added.