philheath

Version 3.13 is out - Download link in video description:
- Added feature "Sens Multiplier" and "Y/X Ratio" from "RawAccel" driver. Allows you to set the sensitivity for each axis separately.
- Counter-Strike: Global Offensive renamed to: Counter-Strike 2

maybe try downloading markc mouse fix. 

Are you following the instructions in the notes? If you add any decimals it will revert to default settings:
Before you make any changes to the config file, you should first change the sensitivity in-game to a random value that is not 0, 100, or the default 50. Make sure this change causes the sensitivity value in the config file to have six decimal places. This is important because adding new decimal places will cause the file to become corrupt, which would cause it to reset when the game is launched.

maths geniuses on this website

maths geniuses on this website

=LOG((LastConvertedSensitivity/0,002)^50)

You have to increase your DPI if you want 11 cm with a lower pixel/count. If you double it from what you have now (and keep the 360 distance at 11 cm) you will get just about 1 pixel/count.

The pixel ratio is a function of the in-game sensitivity, the FOV, and the screen resolution only. No other variables affect it.

Given that it is not very convenient to change your screen resolution or FOV for this issue alone (given that there are pervasive consequences attached to those changes) you would simply reduce the game's sensitivity value instead, as this can be compensated directly for with DPI increase with the only other action requiring reduction in windows cursor speed slider if it bothers you.

 

OOOOOOOOOooooooooooo 😮😮😮 ok makes sense now cause when I played rainbow, and the pixel ratio was right my aim felt so smooth ok that makes sense thanks a lot guys im new to pc n mnk so I've just been a sponge for information apricate it 👍

It depends on the region settings in Windows actually, so I've updated the game notes.

My bad, it does work with decimals, but you have to use a comma and not a period as the decimal separator! I've updated the game now 

I can't see the decimals having any effect, they are just ignored and removed.
The sensitivity was completely changed from the previous version, it's updated now.

@DPI Wizard this game got an update on april 1st, it now allows decimal placings in FOV slider and sensitivity

It's a 16:9 display; so 178% is the vertical, 100% is the horizontal

Another way to look at this, is if you are at 100% horizontal monitor distance for 16:9 screen, but then swap your screen to a 4:3 one, then the match point is now outside the edge of both screen axes, but the sensitivity does not change because of this.

No, the calculation is nothing to do with the screen really, the same scaling applies to the FOV regardless.

The fact you're at 178% should be a first clue - you're already +78% over the top of the monitor. Just as the match point can be outside the edge of one side of your monitor, it can be outside the edge of both.

ChatGPT and math doesn't go well together unless you use a plugin 
They use this equation as you suggested (but not with exactly 27 and 25):
Horizontal: https://www.wolframalpha.com/input?i=2560%2F(27%2F25)
Vertical: https://www.wolframalpha.com/input?i=1440%2F(27%2F25)

Actually while the hipfire FOV stops scaling at 1.642857, the scopes continue to scale up until 1.7. So I've update the calculations and maximum FOV to support this now!

all my calculations wrong all this time

The game doesn't support it, 1.642857 is the maximum. Any higher will not make a difference in the game, but calculations will be wrong if you use it in the calculator, hence the strict enforcement of the range.

It definitely does not work by setting it in the config file on an unmodded version. I have not tried with a mod though, but if you can set in in the console, can you see a FOV change from 1.65 to 1.7?

Some Roblox games can't be added due to various issues:
SCP: Roleplay / Site 006 Roleplay - A lot of packet loss resulting in a very janky mouse input.

I've done some testing now to see exactly what's happening, and this is part a bug in the game and part mis-configuration.
The game maxes out at 105 no matter what you set in the config file and what is displayed in-game. So when you enter 106.990274 the calculations will be wrong since the actual FOV in the game is still 105. USA On will calculate the sensitivity based on what is actually applied in the game (i.e. 105), however USA Off will use the configured FOV (i.e. 106.990274) regardless of whether it is valid or not.
So in short, you need to use 105 as the game doesn't support any higher

All of them are updated and verified now

apex uses focal scaling, 0% coeffcient

93 will be correct in this case, the calculator assumes you use the default Hdeg setting in Oblivity, that's why the suggested config FOV is 109.