DPI Wizard

So the multiplier 1 value does not change in the calculation when you enter a value into the box? I know some people are having this issue so the problem is being investigated, but it's really hard to track down the cause when it can't be replicated. Here's how it should look:

Are you testing in Battle Royale or Save the World? I haven't had any issues in BR, but STW has been a bit unstable. Was mostly fixed last time I tested though.

First do the hipfire conversion where you preferred 360 distance like this: Then convert from Scope Assault Rifle to Widowmaker, since these have the closest FOV: Since you have hipfire and scope sensitivity very different you can't use a method directly from hipfire to scope, but doing it this way works as well. I used Monitor Distance 0% since this is the slowest match and your ADS is a lot slower than hipfire.

What surface tuning setting are you using? The preset hard and soft settings are extremely sensitive to height. Try the factory setting if you're not already using it.

Hipfire and sniper sensitivity added.

Done.

Since it's 0.05 in-game it seems like the cloud file is read correctly. How far in cm/inches is your 360 in Overwatch and Fortnite respectively with these settings when you test?

Try 23 for Relative Aim Sensitivity While Zoomed.

This also looks correct. As Drimzi asked, do you have a Logitech G keyboard or mouse?

This looks good, what is the sensitivity in-game when you look at the sliders?

First of all you need to figure out what conversion method feels more natural for you for the hipfire sensitivity. Since these games have both different FOV and perspective it can be hard to match them. For Overwatch try these three and see which one feels best: 360 distance: 10.94 100% monitor distance: 14.09 0% monitor distance 16.39

Can you post a screenshot of your config file?

I'm curious how this works; is the macro making the sensor send the signals directly, or is the macro simply emulating mouse movement like Logitech LUA? I mostly use Logitech LUA now, and there's DLL's etc in between the macro execution and the actual movement so it has some drawback when it comes to analyzing acceleration and packet loss etc. I also use a Teensy, but it's a bit tedious to use. Lots of nice features though!

Fixed!

ADS is actually just the camera moving closer. The FOV is exactly the same so the sensitivity is also the same.

I'm on it!

I'm currently rewriting a lot of code to allow for multi-calculations (i.e. calculate all aims instantly). I'll look into this down the road

In csgo you can do this with the m_yaw and m_pitch values. Not sure if it's possible in Aim Hero.

It's 1:1 in Dirty Bomb. PUBG is fixed btw, there's a vertical sensitivity setting there now that defaults to 1 which is 1:1.

Too much acceleration in this game to be added, but the devs are aware of it and will hopefully fix it in a future patch.

This game will be checked tomorrow.

Yes, if you don't intend to use the scopes anyway keep it at 1.0

This explains a lot! I never even considered this to be the issue, but when I was analyzing CSGO and how it scales with FOV a long time ago I got really weird results. I deleted the config file and suddenly the scaling made sense. I realize now that the reason it was weird is because I had the zoom_sensitivity_ratio to something other than 1. The question is if there's a demand for a calculation where this value is applied to hipfire for those who want to change FOV and use values other than 1 for zoom?