DPI Wizard

I don't quite understand your question. IPS?

Config file doesn't seem to work with the release though, don't think it's possible to set the sensitivity accurately anymore unless I find another way.

Yeah, it's really only important when you swap to a new mouse, as the difference on the same DPI setting might be quite significant.

You don't really need to test it at high DPI, the offset will usually be about the same across the range (with exceptions of course). So I would recommend testing it at 400 DPI moving 4 inches.

Unless you have a terrible mouse the DPI will be constant, but what it is exactly will normally be slightly off what you set it to. You can test the real DPI in the DPI Analyzer.

Excellent! It's great to see developers here, and see that they take the small things like this seriously Is the FOV directly tied to your speed value? Some prefer a constant 360 distance for the sensitivity, but others might prefer a sensitivity based on the FOV. So I can make the calculator accept the speed as an input that affects the FOV, so if they for instance enter a speed of 180 the FOV will be calculated based on this, and any FOV based sensitivity calculation will work accordingly. (I've put you in the game developer group so you can test everything).

If will always show you the actual HFOV and VFOV in the output, you can use this in Kovaaks.

If it doesn't tell you in-game it's a limitation of the game. There are other aim trainers with better control of the ADS.

Can you please just edit your post instead of replying 6 times with different posts? Makes it a bit tidier... Anyway, you can calculate zoom sensitivity in Kovaaks by selecting the Scope aim. Any limitations in Kovaaks I can't do anything about.

Yes, they don't do it correctly.

That depends on when you did the calculation, it has been correct since February or so.

The ADS will be identical for both of them, the different values are just to account for the different hipfire sensitivity.

Since you have the monitor distance coefficient set to 1.33 you should set the ADS and scope to 133% like this: https://www.mouse-sensitivity.com/?share=c308d0ee5799e2cfb0079619453145e2 The only question is if you would like the hipfire at FOV 120 to match the 360 distance to 100 (like the link above) or follow the same MDV 133% scaling like this scopes: https://www.mouse-sensitivity.com/?share=c0136fbed6fbcb23614637c6f62444b7

Can you please share your conversion with the purple share button so it's easier to see exactly what you're doing? Cheers!

The config file doesn't work anymore, seems like they have removed support for it. https://www.mouse-sensitivity.com/forums/topic/730-escape-from-tarkov/?do=findComment&comment=38776&_rid=2

It's just a newer version of Unreal Engine 4, not really a whole new engine. And it's exactly the same as before, it even uses the same config file. It does lack per scope sensitivity for now it seems like, but other than that nothing has changed.

I would recommend using the DPI your are most comfortable with in Windows so you don't have issues when using the pointer in games doing inventory management etc.

Added.

Aim racer added! View full update

As already mentioned, DPI isn't what causes pixel skipping. Pixel skipping is only related to the sensitivity in the game, FOV and resolution.

I've made a quick video going through the settings. Nothing particularly special about this game, but it might be useful for some.

It's the horizontal sensitivity in CSGO. And most games do not support a different vertical and horizontal sensitivity, which is why stretched is a bad idea to begin with.

It will show in the calculator if set up properly, like here: https://www.mouse-sensitivity.com/?share=367ac5b7116c0faa87ed6d7b0c2b767c CSGO 16:9 to 16:10 stretched resulting in a different m_yaw sensitivity. What 2nd question?

YES. As I said before this will impact the relation between horizontal and vertical. One of your axis is now stretched to cover a different distance, so of course the sensitivity will be different. From 16:9 to 16:10 (or the other way) this impact is minimal. From e.g. 4:3 to 16:9 it is quite significant.