DPI Wizard

Since Legacy MW is based on a specific FOV, you have to use this FOV as the source for your conversion. So do like this, and just change the game you are converting to.

You can get this by adjusting the scale for the monitor distance: https://www.mouse-sensitivity.com/?share=e20f1e522e878525dc93e1f798609eb5 There are a couple of scopes which this doesn't work for, since their FOV is not correct in relation to the sensitivity.

Yes, I'm using HxD.

Correct, 1 is MDV 100%, and you can't set it above 1 even in the config file.

See the game notes for instructions on how to disable smoothing. View full update

Added! Based on the demo, it's not the same as the first Ghostrunner.

It's updated with all the weapons and config file now.

No option as of now, you have to select which one you want to use.

Farlight is third person and the FOV is a lot lower even when set to max, so all this makes the crosshair feel different even though the 360 distance is the same.

Zoom sensitivity is added... ...and the FOV is updated.

Farlight is updated now.

I think it's always on now, I'll check.

Scoped Mosin Nagant is also added now.

I've added everything I have access to except Scoped Mosin Nagant now. Getting these snipers ain't easy! The FOV Type for "Maintain X-Axis FOV" is also updated to Hdeg 16:9.

It's all updated now.

About 20-25 TB.

I've got about 1200 games installed, it was already patched and ready to launch

More, a lot of games struggle especially with polling rates over 1000 Hz, some even struggle with 500 Hz. I just tested War Thunder on PC now though, and there's no issue with up to 1000 Hz. I did not test above that.

It does indeed work, I've updated this along with the minimum in-game value now. So the config value is now much more accurate. Negative acceleration basically means that the game misses/drops packets from the mouse, resulting in a movement shorter than it should me. Settings such as DPI and polling rate might also affect this.

Yeah, it's directly converted the config file value, but with better precision. Hard to say, it might be because of optimization issues and negative acceleration or something, or it might just be that it actually is different. This game is quite hard to accurately measure because the aim tilts upwards more and more the faster you move.

Aimlabs (and pretty much all the other calculators) have just copied the work I have done. 1.14 is the in-game sensitivity, which is impossible to set to that precision. I see that it doesn't go lower than 5% now, so I've updated that. It might very well be that the Linux client is different, I have only verified the calculations for the Windows client.

These four are added.

The sensitivity slider is not accurate, expect some discrepancy. View full update