DPI Wizard

I don't know if you answered this, but is the mouse cursor in the menus etc also really slow?

Added DMR (3X) and Sniper (5X), Needle rifle is 2x. Also did an important update to the FOV calculations. The FOV value in the game isn't the true FOV, it's a multiplier of a 4:3 FOV (where 110 in the game is equal to 90 in 4:3 as in CSGO). It doesn't make a huge difference in the calculations since the game lacks decimals, but now it's at least 100% correct.

This is correct. The default FOV Type selected when you choose a game is what the game uses, but as it differs a lot between games you can do this to calculate the correct value. Do note that some games have very limited or no FOV options though.

Definitely match the FOV if possible, that makes everything more consistent.

Same thing it seems like, it just ignores the decimals and removes them.

I'm not familiar with the SteelSeries driver, but it should have profile (configuration) support: Would be weird if it switches to something unknown though.

If your cursor is also really slow in the game, it might be the mouse driver switching profiles or something.

Done

Use config file or console sensitivity for best accuracy.

I've got the game installed and just need a qualified account. PM the details if you want to share

What do you mean it's the same? Same as what? How far was it? Calculations for CSGO are 100% correct, no question. The sensitivity formula is very well known and used by multiple games. You can try Kovaak's Sensitivity matcher to eliminate any issues with the mouse.

This game does not seem to have any option to change the sensitivity...

Done

An old horror shooter is in!

Added now under Roblox

Since they are very different in FOV and perspective it can be hard to get right, but try with MDH 100%.

Survarium is not using a real FOV as the value, but a multiplier. If you want true 105 FOV, set the FOV Type to Hdeg Res and enter 105, then check the output for the correct Config FOV to get this FOV in the game. Base length is value the calculator tries to match when using viewspeed. It's derived from a formula and used to calculate the discrepancy.

It doesn't really have one, but would be the equivalent of 1/45.

Not quite sure what I'm looking at here. I'm measuring FOV pixel-perfect with scripts.

When you are in the game and in a menu, measure how far you have to move the mouse to move the cursor all the way from the left to the right edge. Move as straight as possible.

The FOV should be spot on, it based on horizontal degrees locked to 16:9. What numbers are you testing with?