NilValue

=( Who does that? That actually requires more work than doing it differently.

Probably in the config file

Okay thank you

Vehicle aim is missing. And I'd love to know what the conversion is between different scopes (f.e. 6x vs 12x and so on). Is it 0% monitor match like in PS2?

Name: Planetside Arena Website: https://store.steampowered.com/app/987350/PlanetSide_Arena/ Status: release Release date: September 19, 2019 Availability: Free

Ah ok, thank you. But how do you feel about the example I explained in my second post in this thread? I'd really appreciate to get your opinion on that. Because in that case, if you were to stay at the same place (same distance to the screen), wouldn't that be awkward for you, too?

Your opinions on one particular theoretical comparison would be interesting to me in this regard: Imagine you're looking at a 20'' size monitor with a scene with a horizontal field of view of say 90° on it. Now imagine you'd compare that to something like a cinema screen, maybe 100 times as large, with the same scene on it. According to a different discussion on these forums (https://www.mouse-sensitivity.com/forum/topic/4631-same-game-monitor-size-change-different-aim-can-you-help/page/2/#comments) you'd have to reduce your sensitivity then by a factor of 100 (assuming you want to match 0% monitor distance), because the screen is now 100 times as large. This seems a little bit excessive and kind of makes little sense to me. My question is this: If you were to move backwards (increasing your real life distance to the monitor) 100 times as far instead, wouldn't this cancel out the size difference, too?

Nevermind, found out. It seems to be 0% monitor match

Hello, I've tested, with me as the only test subject, if my ingame accuracy and feel of sensitivity changes depending on how far away i am from my monitor. I usually sit around 55cm from my display. If I move closer to monitor (around 20cm away) I notice that my sensitivity starts feeling too fast and my accuracy suffers, too. Has anyone else experience with this?

Thanks for the quick reply So in the case of Planetside 2: What would be the expected behaviour there?

Nowadays, in recent games, f.e. Apex Legends, there is usually some note like: Notes: All scopes use the same sensitivity value, choose one specific scope to calculate for. All scopes are matched to hipfire with 0% vertical monitor distance. I would love to have that information for older games, too. Like for example Planetside 2. I'd be really interested in how different scopes are matched to each other (The setting "scoped sensitivity" in planetside 2 applies to the anything from 3.4X to 12X) I can understand that this might be time consuming to do, but I think it would be highly appreciated.

I was just curious if that came with some new update or if it had always been like that, because I don't remember it being that way before. If it was an update, something else might be effected as well. In any case it's stupid for the software to behave in such a way, so calling it retarded is imho nothing but accurate. Sorry if that triggered you...

On the Windows 10 startup screen I have mouse acceleration. Thankfully the MarkC mouse acceleration fix works here. http://donewmouseaccel.blogspot.com/2010/03/markc-windows-7-mouse-acceleration-fix.html Am I the only one who has this?

I am not entirely sure if it's a sensitivity issue, or if it is actually an acceleration issue. Regardless, I tested my sensitivity in other games, too. I tested Planetside 2 and Overwatch, just to also make sure that my measuring is not off for some reason. There everything is as it should be. Only BF V with DX12 enabled was odd. Thank you very much for your input.

I just did some testing, first I tried messing around with my settings, verified that my mosue DPI is still 793, tried to go back to 500hz polling and even disabled GSync on my monitor. Nothing of that changed anything until I disabled DX12 and started the game with DX11. Now my sensitivity is fine. I'd really love to know if you experience the same issue with DX12 enabled (or if you already tested it with DX12).

Yes, I only changed my hz rate since the last time playing from 500hz up to 1000hz. If nothing has changed on your side, I will continue to troubleshoot this on my end. Thanks a lot for your help.

Yes

Hello, since today my mouse sensitivity in Battlefield V (cm / 360°) is not the same as before. I have FOV set to 77.55 and sensitivity to 0.007865. My mouse DPI is 793, which should result in around 39.107 cm / 360°. However, since today it is more like 41 to 42 cm / 360°. I don't know what it is, maybe it is mouse acceleration for some odd reason or maybe some patch changed the sensitivity ratio so that the calculator is wrong now? Before today, everything was as expected.

OMG, no that wasn't it. I was testing in Single Player. In Single Player the game actually uses the configured FOV as 4:3. In Practice Range it used it as vertical. Weird thing though... Thanks for the fast reply

Hello, I just downloaded Battlefield V and wanted to adjust the FOV. While doing so, I noticed that the tooltip might say it uses vertical FOV, but it actually uses horizontal 4:3 FOV. Is this correct? Does the calculator respect that? Also, BF5 provides the ability to adjust Vehicle FOV separately. How does the calculator reflect that?

Well then it's different formulas and the 0% formula of the calculator is equal to mine, nice :D. Thank you

I tested that and it's true, but not in the way one would understand. If you make an fov other than the default, then you'd have to leave the zoom sensitivity on 1 in order for the calculated sensitivity to be accurate. The way you phrase it, at least I myself would have understood it the other way around. On that note, maybe you can give me an answer to this question here:

When converting between different FOVs with 0% MM, there would be 2 ways to do so. One is an approximation, where you're using the usual formula for FOV monitor match conversion but with a very small vertical resolution. Another way would be to calculate the limes of FOV -> 0 for this formula. In other words: If I want to calculate cm / 360° with a formula (can copy paste it on https://rechneronline.de/function-graphs/ if you like) for vertical match 100% I could use something like this: f(horizontal_fov_for_relative_horizontal_resolution) = ((rad(360)) / ((2 * arctan((absolute_vertical_resolution / horizontal_resolution_for_relative_horizontal_fov) * tan(0.5 * rad(horizontal_fov_for_relative_horizontal_resolution)))))) * modifier This would give me all cm / 360° values for any vertical fov, enhanced by a modifier of my subjective choosing. Now I could calculate the 0% MM by just setting the value for (absolute_vertical_resolution / horizontal_resolution_for_relative_horizontal_fov) to a very small value like Integer.MIN_VALUE / Integer.MAX_VALUE. Or alternatively I could calculate the limes for absolute_vertical_resolution -> 0, which would result in the following: f(x) = rad(360) * (horizontal_resolution_for_relative_horizontal_fov / absolute_vertical_resolution ) * cot(0.5 * rad(horizontal_fov_for_relative_horizontal_resolution)) * modifier In this case, 0% MM would actually use a "different" formula than the other percentage MMs. My question is now: Which of those approaches does the calculator use?

Ah ok, that makes sense. Thanks