Leaderboard

Name: Arena Breakout: Infinite Website: https://store.steampowered.com/app/2073620/Arena_Breakout_Infinite/ https://www.arenabreakoutinfinite.com/en/ Status: Closed Beta Release Date: 5/8/24 (Closed Beta); Full Release TBD Availability: Free

I don't currently have access, but will add it as soon as I do!

Name: Marvel Rivals Website: https://store.steampowered.com/app/2767030/Marvel_Rivals/ Status: (alpha, closed beta) Release date: TBD Availability: (invite only)

Name: MULLET MADJACK Website: https://store.steampowered.com/app/2111190/MULLET_MADJACK/ Status: Released Release date: 15 May 2024 Availability: Purchase

Name: Marvel Rivals Website: https://store.steampowered.com/app/2767030/Marvel_Rivals/ Status: (alpha, closed beta) Release date: TBD Availability: (invite only)

Hi, the devs just released patch 3.23 with a bunch of FPS weapon improvements and bug fixes related to sensitivity settings. Could you please check it out and update the calculator if possible? Also should I ask in this topic for updates or go to new game request?

pls

Name: Project L33T Website: https://www.playl33t.com https://store.steampowered.com/app/2866540 Status: alpha Release date: 2024 Q2 Availability: purchase

These are added.

Got released into early access today, available on steam for 35$

Name: Gray Zone Warfare Website: https://store.steampowered.com/app/2479810/Gray_Zone_Warfare/ Status: In Development Release date: 2024 Availability: /

This is updated now. Only for in-game settings though, as the hex conversion does not currently support multiple inputs.

https://store.steampowered.com/app/2111190/MULLET_MADJACK/

Added.

combat Champion

The camera has to be able to be tilted all the way down so you look straight ahead. It's not possible to analyze the FOV otherwise.

If that is the case and since it's Unreal Engine based from what I can gather, the correct factor is likely ~0.37718 or ~0.37714 depending on how they implemented the sensitivity. Once I get access to the game we will know for sure

I’ve been told that Marvel Rivals is essentially OW2 sens multiplied by .375 for anyone trying to do a somewhat accurate conversion while we wait. Example 4 sens in OW2 would be 1.5 in Marvel Rivals

Hipfire is added, aims coming soon! View full update

All aims are added now!

I wonder if the ADS Scaling Setting now works better if you want 0% feeling.

Name: Arena Breakout: Infinite Website: https://store.steampowered.com/app/2073620/Arena_Breakout_Infinite/ https://www.arenabreakoutinfinite.com/en/ Status: Closed Beta Release Date: 5/8/24 (Closed Beta); Full Release TBD Availability: Free

Name: Arena Breakout: Infinite Website: https://store.steampowered.com/app/2073620/Arena_Breakout_Infinite/ https://www.arenabreakoutinfinite.com/en/ Status: Closed Beta Release Date: 5/8/24 (Closed Beta); Full Release TBD Availability: Free

hello, I feel like this game's sensitivity changed, and now the game feels much different than what it says it is

The new sensitivity sliders are added now

Both these are added.

Both of these have the same issue with frame rate affected sensitivity, and none of the usual Unreal Engine 4 fixes solves the problem. So neither can be added.

Foundry is added.

Name: Wild Assault Website: https://store.steampowered.com/app/2827230/Wild_Assault/ Status: easily accessible closed beta (request access on steam) Release date: not yet mentioned, but pretty much everyone who applies for the beta on steam and gets in through discord gets into the beta Availability: Free

At the top of the calculator, make sure the mode is on 'Default' or 'Advanced' and enter '178' in the Monitor Distance - Vertical section. Also, don't forget to input your R6 Siege FOV in the calculator or else the ADS results will be wrong.

It is, I've added instructions to disable it. Also updated to FOV range.

These are not constants, these values will be different as they use centimeter in the formula. For example, these are the values I got in CoD:MW Jedi's Tick - Horizontal ≈ 107%MDV, 60%MDH; 107*(9/16)=60.1875%MDH Jedi's Tick - Vertical ≈ 68%MDV, 38%MDH; 68*(9/16)=38.25%MDH

Hipfire is updated for the new test. Note that scopes seems somewhat bugged at the moment, as ADS, 3x and 4x are all the same.

Name: EARTH DEFENSE FORCE: WORLD BROTHERS Website: https://store.steampowered.com/app/1497950/EARTH_DEFENSE_FORCE_WORLD_BROTHERS/ Status: Released Release Date: 27.05.2021 Availability: Purchase

Name: Ghost of Tsushima DIRECTOR'S CUT Website: https://store.steampowered.com/app/2215430/Ghost_of_Tsushima_DIRECTORS_CUT/ Status: In Development Release date: May 16, 2024 Availability: $59.99

It still the same as far as I can tell. Make sure ADS - Zoom Scaling Enabled is set to No though.

Some games cost close to $100 and requires days of work to analyze. There's over 1200 free games here, and still people using the site for free have the audacity to complain about ONE new game that currently is not free. If you don't like it GTFO.

no this method is close to 65 % MDV

Name: S.T.A.L.K.E.R. 2: Heart Of Chernobyl Website: https://store.steampowered.com/app/1643320/STALKER_2_Heart_of_Chernobyl/ Status: In Development Release date: 28.4.2022 08.12.2022 Dec 2023 Q1 2024 5 Sep 2024 Availability: Preorder

Do you know if it is possible to match Ironsight sensitivity with regular sensitivity? used to be done by the fIronSightsFOVRotateMult command in FO4 yet it does not seem to work in 76

Let's go from 10" monitor to 20" monitor. Both have 1920x1080 pixels. First assumption will be to match the distance it takes to move the cursor from one side to the other side, AKA move 1920 pixels. This is what the calculator does. Let's extrapolate this idea to a 1" screen and a 1000" screen. If the distance it takes to move the mouse results in the cursor moving 1" in one case, and 1000" in the other, will it feel the same? Personally it wouldn't to me. Instead of matching the quantity of pixels displaced, you want to match the distance displaced. Figure out how big a pixel is. (rounded for simplicity) 10" monitor: Every pixel is 0.0045" 20" monitor: Every pixel is 0.0090" If it takes 1" of mouse movement to move 1920 pixels on the 20" monitor, then 1" of mouse movement correlates to 17.4". This is a ratio of 1 : 17.4, or a gain of 17.4. It doesn't matter what units you measure, whether it is mm, cm, inches, kilometers, it doesn't matter. 1 unit of mouse movement correlates to x unit of cursor movement. This is what you convert, not the pixels displaced. It will become inconvenient to move the cursor from the start menu to the system tray if the screen was 1000" wide, but that has nothing to do with the sensitivity of the mouse. For convenience, you can change the sensitivity to reduce that distance, but that is just preference. Let's take it to 3D. In the above explanation you can see that pixels don't matter. The monitor is acting like a window. You are keeping real-world distances. The same applies to 3D. Imagine you are playing a game like CS:GO. You crop the aspect ratio from 16:9 to 4:3. Does the perceived sensitivity change? Is it like some kind of optical illusion where replacing some of the rendered game world with blackness changes the perception of sensitivity? It personally isn't to me. What if instead of blackness, you just change to a 4:3 monitor. You effectively reduced the horizontal angle of view from 106.26 degrees to 90 degrees, but the perceived sensitivity did not change. If it feels the same, why would you scale the sensitivity by the change in angles, ie. 90/106.26, which is what 'monitor distance match' is doing. So at the moment, the angle of view (or FOV) is changing, but the cm/360° is not and it feels good. So maybe it is because the vertical angle of view is still 73.74, so that's why the sensitivity didn't change? Wrong. Since CS:GO enforces a specific angle of view, let's just place black paper on the monitor to 'crop' it, let's reduce the effective vertical angle of view to a low number, will the sensitivity appear to change? If you answer no, then you can see that the angle of view has no bearing on the sensitivity. The focal length remained constant, the angle of view changed, so the answer is the focal length. Here is 90° (4:3) at 20" and at 10", overlayed You can see that they are both different. They have identical angle of view, but the focal length is completely different. If you convert from the 20" to the 10", then the 10" needs to reduce the angle of view to maintain the same focal length. 20" has 90° (4:3), 10" has 53.13° (4:3). Here is 10" converted to 20". 10" has 90° (4:3). 20" has 126.87° (4:3). The first scenario, where the game enforces 90° (4:3), the game sensitivity value doesn't change. However, the CPI did change, by a factor of 2 if you keep the same 2D sensitivity. This is because the 20" is twice the size of 10". The focal length has also changed by the same factor. So the change in CPI results in the change in cm/360°, even though the FOV is the same. If you didn't want your cm/360° to change, you would have to use a lower angle of view on the smaller monitor (the 2nd picture). You can quickly test this for yourself by creating a custom half resolution, like 960x540, and then playing a game in windowed or fullscreen (with no scaling and override enabled). Compare no change in sensitivity, and double game sensitivity (or whatever sensitivity value is equivalent to half the cm/360°). See which one feels better. Scaling the game sensitivity by the change in focal length is exactly what 0% monitor match does. The change in monitor size is also the same factor as the change in focal length. This suggests that 0% is the only way to convert game sensitivity/cpi, as it results in no change in 'sensitivity'. The relationship between the device and the display element remains constant. Any deviation from this will be personal preference. Many will have personal preference that will override 0%. Like if the screen was incredibly wide such as 32:9, making the distance from one end to the other double than that of a 16:9, then they may prefer to scale their sensitivity by a factor or 2 in order to make the hand distance the same when going from the start menu to the taskbar, or closing browser tabs, etc. They distance matched, which requires a change of device/mouse sensitivity (also applies to 3D). Many may also prefer to amplify their sensitivity for aim down sights/scopes, so they don't have to scale their input proportionately with the change in zoom and image curvature. 0% usually feels too slow in this case because you are directly comparing two different focal lengths without the distance between you and the reference point changing to cancel out the perceived zoom, whilst simultaneously using the same hand movement before and after the zoom. The target size, distance between the target and the crosshair, the target movement speed, etc., all scale proportionately with the focal length, which means you also need to scale your input with the focal length to land the flick or track the movement speed (and then there's the difference in eccentricity/curvature that results in that snappy/sluggish feeling and different diagonal trajectories). Due to these preferences to scale sensitivity instead of input, other methods like 'monitor distance match' can be useful. I think Viewspeed v2 is also useful, the feeling is is kind of comparable to zooming in and having the camera dolly in the opposite direction of the zoom. If you zoom in from one end of the spectrum to the other, whilst simultaneously moving the mouse in circles, it looks like the sensitivity is matched perfectly. But when it comes to actually using Viewspeed v2, it results in worse aim performance (personally) at the expense of it feeling more consistent in that exact specific moment, due to the no sudden feeling of slowdown or speed up whilst using identical mouse movement before/after the zoom. As for focal length, I believe it is found by doing the following: (SquarePixels/2) / tan(SquareDegrees * pi/360) = focal length in pixels? It's the same as this graphical fov calculator: https://teacher.desmos.com/activitybuilder/custom/5a61dd34fafbd40a25416e02#preview/d123ef39-8694-4760-af7d-c18c936ce79d Scale pixels by the physical dimension of a pixel, and you will see that the above cases have identical focal lengths despite very different angle of views. 10" 90 (4:3) has 720 pixels focal length, 720 * 0.0045 = 3.24" 20" 126.87 (4:3) has 360 pixels focal length, 360 * 0.0090 = 3.24".

in valorant i use windowe mode with 4:3 res. in fortnite the same but just for the stretch res. my monitor size is 24.5"