NilValue

And support for this is added now.

My bad, I thought they had moved everything to the GameUserSettings.ini file. I've fixed and updated everything now

Ah damn, game didn't actually apply the FOV settings, just noticed. Sorry, my bad
/closed

https://store.steampowered.com/newshub/app/359550/view/2753341823353650692

When checking for sensitivity in Prey by distance (i.e. entering a certain distance and reading the necessary sensitivity setting), the calculator provides only increments that are the same as the ingame setting. However, the config file setting can be set to far more accurate numbers than the ingame settings.
Example: I enter 36.015 cm / 360 with 793 DPI. I get as config file value 0.0006. However I can set also set this value to 0.0005588, which is far more accurate and the game recognizes correctly.

Probably in the config file

Reload the page
Config File config ASAP.

I'll be all over Halo when it's out!

Name: halo: Master Chief Collection
Website :https://store.steampowered.com/app/1064220/Halo_Reach/
Release date: 3 December 2019 / 1pm EST
Availability: Purchase

Name: Halo: Reach
Website:https://store.steampowered.com/app/1064220/Halo_Reach/
Status:Release in 20 Hours.
Release date: 3 December 2019
Availability: Purchase

+1 for MCC.

Name: Halo: The Master Chief Collection
Website: https://store.steampowered.com/app/976730
Status: Release Date - 12/3/2019
Availability: Purchase

I always measure sensitivity and FOV with scripts.
Aims that have blacked out the edges can be measured in two ways.
Either by figuring out how the game scales FOV and sensitivity through other tests. So for instance if the game scales sensitivity to 100% monitor match, I know that double the 360 distance equals half the horizontal FOV.
Or by measuring the distance visible in the scope. If only 40% (between the crosshair and edge) of the screen is visible, I can measure how far moving this 40% is, compare this to the 360 distance and calculate how many degrees I moved to reach 40% monitor distance. From there some more math to find the FOV.
The FOV in the calculator is for the entire screen regardless of what is blacked out.

If you set Windows Pointer Speed to 1 you should have plenty of room to measure even high DPI (16000 DPI moving 5 inches fits on a 2560x1440 monitor).
A 3D analyzer is interesting though, will look into it.

The analyze DPI feature is really nice, however, on higher DPI settings it is nearly impossible to measure accurately.
My proposal: Use a 3D scene inside the browser to measure real dpi, where you can measure nearly infinite distances.
Technology to look into: X3D / X3DOM, should be fairly easy to set up and is supported by Chrome.

If I enter 395 DPI (my mouse's real dpi at 400 setting) and 60.603 cm, I get 0.214025 as recommended sensitivity. That is incorrect. It results in an in game cm/360 of approximately 30 - 31 cm.
I think they must have changed sth there with the latest patch, because I remember the calculator being accurate.