tuphac

Are you kidding me? For every game I need to:
Buy it (if not free) Download it Potentially play a bit Analyze movement Reverse engineer sensitivity formula Measure FOV/reverse engineer it Analyze potential aims and reverse engineer them Potential issues with acceleration/smoothing or similar needs to be worked out or worked around and so on Then it needs to be tested and verified to work as intended with The calculator Different DPIs Different FOVs Reporting rates Resolutions Aspect ratios Windows settings and so on. Adding a game can take anywhere from a few hours to many days. It's a bit more work than adding a game name to the calculator... And premium members usually gets priority.

Analyzed this game a bit further now, and there is a file you can set the sensitivity accurately in. It requires a hex editor and to find the correct bytes in the file. Added it now, see the notes for some instructions

DPI Wizard is one of my heroes.
 

It just turns on acceleration, so the sensitivity is directly tied to how fast you are moving your mouse. In other words no method that can be replicated.

lol thats true, we need to see a real life photo of DPI wizard to think otherwise
 This game looks really promising though!

I don't understand how you are so quick. I see you as an entity and this point. 

Name: Wolfenstein: Enemy Territory
Website: https://www.splashdamage.com/games/wolfenstein-enemy-territory/
Status: Release
Release date: 28 May 2003
Availability: Free

Bullets Per Minute gameplay
Yes please. I need this conversion

Name: BPM: Bullets Per Minute
Website: https://store.steampowered.com/app/1286350/BPM_BULLETS_PER_MINUTE/
Status: Release
Release date: September 15, 2020 
Availability: Purchase 

Requesting Tannenberg
http://store.steampowered.com/app/633460/Tannenberg/

20-40 cm/360° should do most people for most games that want to be accurate but still turn fast(ish), you can pretty much chose inside that range based off of comfort, but you can adjust to any sensitivity over time. Also, your mousepad size might play into it, you should really be able to do at least a 180° turn across your mouse mat and if you have a very small mouse mat then that might make your cm/360° less than 20.
If today I were to choose a cm/360 for 103° FOV (ish) for all FPS games after lots of experience with 40 cm/360° in CS:GO and 0% monitor distance match and used it in other faster paced games like overwatch I'd choose about 34 cm/360° if you care about my opinon 😛

http://www.wolframalpha.com/input/?i=c%3D1800;+x%3D-20;+c%2F(1+-+x+1%2F30)
If you use this link instead, you just need to put in CPI. Then in the shoot the beat! output parameters, you put the CPI result in there.
I also changed the scaling, as -30 seems to be a lot closer to double the distance rather than -20. I did a crude check. I screenshotted 0 and -30, and scaled -30 by 200%, and the center background portrait thing was pretty much the same size.

Yes, 4200, or just use convert to Aim Lab first to see what the sensitivity is with more decimals, and put that in to the wolfram calc. Then you can convert from Aim Lab to Shoot the Beat's registry value.
It's not the same scaling as 56.25%. It's scaling proportionately with the camera distance, so it would be more like 0%.
 

I'll take a look at it a bit later today.

It does seem to scale in the way I assumed.
I'm assuming -100 = 4294967196 ?
Tried that and it seemed as good as it could get, but it is a new experience having the camera orbit like that.
You can put your CPI, cm/360, sensitivity, or whatever in here, with whatever distance, and it will tell you what to use: Calc for distance at 90 FOV
c = cpi, sens, or whatever
x = distance

@DPI Wizard Overwatch Update  ADS settings on PTR server today.
 # Increased the precision of the Relative Aim Sensitivity While Zoomed slider. This can be found under Options > Controls > Hero > Widowmaker. 
Can you update the calculator when you get the chance please? Thanks!

Ok, so you just need to enter everything into the Input.ini file again, it is cleared after the update.

this game is pretty awesome! thanks for introducing it to me!!!! 

thanks. this worked! I decided to switch to 125 hz polling rate as my default after testing that my aim was alot more stable. 

Select Overwatch as the sensitvity engine instead of Aim Lab
then change the Field of View to  70.5328   =   103 fov in overwatch. this is 100% match.
you can then just enter your overwatch sens. if you need the scope in FOV to be 51 like widow maker let me know//

Thank you @DPI Wizard. I just want to say I love you and I love your work. I admire the fact that you are using your gift and talent to benefit and be of service to so many people specially me because you have no idea how much pain and struggle I go through with my obsession of  becoming a great FPS aimer. Similar to how I used to obsessed over basketball and practicing endlessly to become good at one thing. this tool has really help my aim in Overwatch.  I would try so many different conversion method and learned about the mathematics side things from reading post int he forum. Finally, I was able to find a conversion method that worked for me personally.    I went from a hard stuck Diamond scrub to now almost GM Thank you!. Thank you! Thank you!!!