DPI Wizard

379 380 381

Added Halo 5: Forge, Aim Hero and Desync. View full update

Use the the game you feel has the perfect sensitivity for you as a base. CS:GO is the most used game here, as a lot of people have a favorite setting that feels good. For consistency you should use the same game and settings as the base for all calculations. What conversion method feels best is up to personal preference however. 360 distance will only make sense if the FOV's are very close between the two games. Monitor Distance converts the movement to a certain point on your monitor to be the same (if the FOV's are different, it's only possible to perfectly match it to one point). And Viewspeed matches the arc lengths between different FOV's. It typically will be between 60% and 70% Monitor Distance.

Yeah, I updated the notes on the config file settings earlier. The MouseSensitivity= value has no effect other than visually displaying the number in the game menu. It's the LastConvertedMouseSensitivity= value that actually sets the sensitivity.

What conversion method are you using? I would recommend trying Viewspeed if you're not doing it already.

Started adding now, and have split the game in two in game selection, one for in-game and one for config file. Will add them continually as I get them analysed. First one added is config file calculations for ADS (Targeting) with rifle.

Updated config file calculations, make sure to read the notes.

Ok, so the "MouseSensitivity=" is just the visually shown sensitivity in the in-game setting, while the LastConvertedMouseSensitivity= is the actually applied sensitivity. Will update calculator asap!

Actually, use the in-game setting instead, I see now that the config file is not reading correctly even though the in-game value changes. I will see if you need more values edited.

You have to change the "MouseSensitivity=" value in the config file, not the "LastConvertedMouseSensitivity="

I tried that, but I come to think about it I have a script binding on the right mouse-button that probably messes it up!

No, when I right-click it just locks the view, it's not zooming in.

ADS/scopes are not working for me, is it a bug or a something I have to do?

Updated with first person view calculations. Note that all scopes now have a different FOV as well. View full update

PlayerUnknown's Battlegrounds is on the way! Unless there's something weird with the sensitivity settings, it will be added today.

These I just had lying around actually I have not analysed what causes the drift yet, other than it seems to be the sensor going to far in one direction compared to how far it's physically moved. Some tuning might be possible. 1. 11 inches pr. second. Not very fast, but decent (accuracy may suffer though). 2. Everything should be pretty flat, but I'll take that into consideration on the next tests, to make sure the mouse isn't ever so slightly tilting because the grabber lifts it.

It should be possible to add the outline of the circle in post production maybe (if it's not too much job). Or even better, maybe find a perfect circle in-game and track around that? I can do this circle thing with scripting mouse movement as well, which eliminates all other factors.

A Razer Mamba 16000 Chroma and a ZOWIE EC2-A are on the way for a showdown with the G900 Chaos Spectrum!

A lot more mice, and a lot more different tests. This was a simple comparison to see if the system works. And it does! It seems like G900 is a damn good benchmark for all others, so I will first put that one through a lot of different tests so we have a baseline for what's good.

This is a quick test to demonstrate using an AxiDraw V3 to analyse mouse sensors. Full article here: http://www.mouse-sensitivity.com/forum/topic/604-mouse-sensor-accuracy-test/ View full update

Didn't get access!

Check it now

Absolutely Fixing the calculations now, viewspeed offline while I work on it.