DPI Wizard

This is down to how the different FOV's feel different, and personal preference. What you should do if the 360 hipfire conversion feels good (that is 0.14 in H1Z1 to 0.021562 in PUBG), use the PUBG sensitivity as input for all the aims. So for any scope you select PUBG as input game, and enter 0.021562 as sensitivity, and convert to all the other aims/scopes using Viewspeed.

That should be right, but can you screenshot the input and output for one of the scopes, say the 8x one? Just want to make sure everything is correct.

Sorry, I was a bit quick to say it was correct. You should switch from 360 Distance to Viewspeed, then you'll be ok. You will get almost the same number for all calculations, since PUBG handles sensitivity very close to what Viewspeed does

Yes, you will get huge 360 distance numbers on the scopes and that is correct. Monitor Distance and Viewspeed matches the movement relative to what you see on your monitor, so the 360 distance will not match unless the FOV is identical.

Enter your BF1 numbers in the Convert from game as you have done, and select PUBG (In-game) as the Convert to game. What match method feel best is a personal preference, but try with Viewspeed first (in the box that says 360 Distance). Then select the different aims for PUBG to find the best match for each, and set those values in-game.

That is correct, and you can't change FOV in PUBG yet. I think they plan to add this possibility in the future.

Done!

Updated with both hipfire and aim sensitivity for this game now. View full update

With viewspeed the chord length is used to match the sensitivity, but it does not indicate how far you have to move your mouse to move the entire chord length. Monitor Distance 100% is from the center of the monitor to the edge btw, not edge to edge. But yes, the rest will be a bit off. This is the same for any conversion method.

You are doing it correct, but if you want the edge movement to be identical, select Monitor Distance 100% instead. With Viewspeed the match will typically be around 60-70% Monitor Distance (depending on FOV etc). As you can only match to one point between different FOVs, this means that there will be a slight different when moving to 100%.

Strafe is up!

Added with in-game sensitivity. View full update

Have you tried making the file read-only? Does it happen if you just start the game and exit, without applying any settings in-game?

So I took a look at CSGO and fov_cs_debug now. And sure enough, when I change FOV, the base sensitivity changes. Just changing to 91 makes a huge difference in 360 distance. But changing from 91 to 100 scales like expected. So I was a little bit confused, as I think people would have noticed this... Then I tested on another machine with a brand new CSGO installation, and there it scales like expected and according to the calculator; changing to 91 makes just a very small difference. The CSGO installation that scales wrong have been used for a lot of r_input testing, analysis with different variables and so on. So I have somewhere set a variable or switch that makes FOV scale differently. I'll look through the config file and see if I can find the cause, but unless you have the same "problem", the calculator is correct.

Correct, I'll update the notes to be clear about this.

You're not the only one! I've been wanting to get the tests done since the first video, but I simply haven't had the time to put together a video and presentation of the results yet. As mentioned in another topic I've done a lot of improvements to the machine, and are aiming to publish some tests before the end of the month. I currently have lined up Logitech G900, Zowie EC2-A, Razer Mamba 16000 and the new (currently unreleased) mouse with a 3360 sensor for testing.

Just tested Dishonored 2 again, and there's still a huge problem with acceleration. I know the base unaccelerated sensitivity, but in its current state any calculation I provide will be invalid because it depends on how fast you move your mouse and your DPI. Arkane, please fix! PS! For other requests in this thread, I'm gonna go through them soon. But the focus now is to iron out any bugs and issues with the currently published games, as well as updating the calculator to support all variations of sensitivity, multipliers and FOV types. But don't hold back on your requests, highly requested games will get priority.