DPI Wizard

Definitely sounds like something is changed indeed. I will check it today

Ah, I see now. You should leave the input DPI for shootmania at 850, and only change the new DPI for reflex to 1100

I'll look into it. Can you take a screenshot of exactly what you are entering?

I would be all over this game... if I had access

It's in the infamous pipeline

Just added it

Defend the dungeon! Remember to check the notes on how to disable mouse smoothing. View full update

Doom 2016 is added!

Added! View full update

Updated with correct formulas for the release version! View full update

Downloaded it yesterday, will analyze it today And Doom tomorrow! I'll look into it.

I will!

Kill orcs! View full update

Haha, good to hear Thanks for your support!

No, that shouldn't be a problem as the sensitivity is (or at least was) unaffected by FOV. I'll re-analyze the game and see if they changed something

How so, is it completely wrong? There's been a few updates on Siege since I added it, so they may have changed something!

Since in a game you are moving around an axis with a spherical FOV, the calculation is only accurate for one distance. In other words, while the movement in Windows is 100% linear, it is not in-game. If you just measured say 10 cm of the screen, you will end up moving too short. What I'm planning is an option in the calculator to specify what on-screen distance you want matched. The calculator matches the sensitivity for half a screen-width. In other words, if you measure the mouse movement distance in Windows from exactly the middle of the screen to the edge, you should get the exact same distance as moving the cross-hair to the object on the edge of screen in-game (and obviously remember to turn off acceleration in Windows if it is on )

Hey! The first part is correct, games will be added over time, and the list of supported games will increase. The second part is unfortunately not correct, the way it works now is that the save function only takes a snapshot of everything currently entered into the calculator. If you select another game and enter new values, and then click save again, the previous save will be overwritten. And the load button always loads the last saved values. The idea is that you save the game you want to base all other games on, so you don't have to enter it each time. And then select whatever game you want to convert to. I do want to create a more permanent way for members to save all their games and settings, but this will require a complete re-write of the code so I don't know when or even if this will happen. The old calculators are only available so users had a fallback if they found something broken in the last major update. It will be removed soon, and you should only use the new one If you use the new calculator, your should get this output, is this not what you are getting?

0 should be no bar visible on the slider, does that not work anymore? Use the arrow keys to adjust it. If they changed something I need to update it!

That's really individual, I wouldn't aim to replicate other players sensitivity, but rather find your own sweet-spot. The TMS you refer to directly translate to a certain 360 degree turn distance, and if you find yourself coming up short on the turns, you should increase the TMS.

Correct, but do note the discrepancy of over 8%. This is due to the lack of granularity adjusting the sensitivity in-game. If you edit the config file instead, you get an discrepancy of just 0.0305%.

If you have not changed any default settings, you can use the "Hipfire (Simple)" option under aim. This calculation assumes all multipliers are default, and you can select the calculated sensitivity in-game and do not have to mess around with config files.