Skidushe

Are you playing 4:3 stretched? Also, can I ask why you're playing 1440 x 1080 fps? Or because you've seen someone else comfortable with it. If it's because you've seen someone else comfortable with it, you're probably better using the native res. of your monitor and finding where you're comfortable from there. Your pc will be less jitterery alt-tabbing and faster. for csgo you should go fortnite hipfire -> csgo hipfire if you want to match the hipfire sens's if you want to match the scope aswell you can go fortnite hipfire -> scope1 awp ssg and change your zoom_ratio_sensitivity_mouse to the value it gives. 0% monitor match is the 'right' conversion, but if you have another preferred method use that. For aim hero you can set FOV of fortnite to aim hero and match using any method (in the calculator) and they will all give you the right fortnite 1:1 sens translation everywhere in the view.

Surely if you placed the 4:3 portion of your 16:9 screen in the same place as the existing 4:3 screen, the only thing that changes is the extra view you get, this would just mean you have more periphery vision. Sure that extra bit will move faster, so the edges of you screen will move faster but that's it. Where's this 0.2 come from? What's your reasoning?

if you type all the values in the calc, if you scroll down you should be given your cm/360 or whatever unit you used, no script needed. And monitor distance is the conversion method field on the second section of the calculator, then you can type the match % in. To answer the second questionif we take the overall sens as (ingame sens x dpi) then: 0.0113 x 400 = 4.52 0.00565 x 800 = 4.52 So they will both feel identical

So you're changing your cm/360 on the same FOV, but it still works? I've lost it now but I'll take your word for it, I'm never going to use this it anyway

What about my other point, surely if you went from 800dpi -> 940 dpi the after the desktop would be matched but as you'd gone up by a factor of 1.175 in your dpi you'd need to divide your sens in games (first person shooter games) by 1.175?

pixel skipping to my knowledge is not a problem, and DPI (CPI - Counts per inch) is not the cause either, a count is a count the same 'distance in your os' for every count, the higher the DPI just means how many counts per inch it reports. so you're sending more counts, so you kind of have a higher res grid on your mouse pad that your mouse is sending every time it goes over a grid intersection. the problem is how big you're sens value is in game, so you want a low value to stop pixel skipping in theory, you can see here on this thread how it works: The sensitivities where Pixels/count: 2 is greater than 1 is when 'pixel skipping' happens, that post is a good read though for understanding if that's what you want. There's probably some maths to work out if this happens but to my knowledge your combo is probably perfectly fine. Also, if you want to see this pixel skipping and you have counterstrike, go in the console and do: sv_cheats 1 fov_cs_debug 2 and move your mouse around, the higher your sens in game, the more you'll see the jerky movement as each count is registered. in terms of mouse mat aiming and accuracy, I find personally the sweetspot for games like fornite is 180-360 degrees in your mouse mat width, as you don't need more than 360 per swipe, so these are best for accuracy, and you don't want less than 180 as you can't see behind you without lifting your mouse, I personally thing 270 degrees on your mouse mat is the sweet spot as you can kinda swipe on your mouse mat and see the other bit of where your view was. The calculator has 2 sections input game and output game, they can both be the same e.g. the top one your hipfire in fortnite if you want to convert that to your scoped sensitivity. all the values are pretty self explanatory. The only one that I can think might be confusing is the FOV type and the FOV to accompany it: everything with 'deg' in is measured in degrees, everything with 'rad' in is measured in radians, you'll probably use the first one the one with 4:3 is if you made the vertical all the way up your monitor set, and pretended your were on a 4:3 screen, what would your FOV be. The res one is just the FOV you can see at a resolution (converts to aspect ratio) (For fortnite you'll use HDeg Res and give your FOV in fortnite) There's lots of other threads for what conversions to use, at the end of the day everything is personal preference, go with the data but your preference at the end of the day is more important. I personally thing 0% monitor match is the best... BUT that's personal, 100% VERTICAL monitor matching (56.26% horizonal 16:9) is also a good one to try, or viewspeed V2.

I understand that if this change makes the cursor feel the same across games and desktop, but you not need to then need to decrease your in-game sensitivity by the same factor you increased your dpi by otherwise your cm/360 would change? Or am I missing something... Also, what is the term AR?

Why is it resolution dependent (same aspect ratio)? Surely that just changes the detail contained within the 24 inch screen but not anything else?

If vertical mm is used, it's 100%, if horizontal like in the calc it's the apsect ratio division: 4:3 --> 3/4 = 75% 16:9 -> 9/16 = 56.25% x:y -> y/x = (y/x) *100%

I could think of doing it if you could kind of draw out an angle grid in front of you, but with games like PUBG and most games where that's not possible, and probably wouldn't get accurate results, how does it end up getting done? The only other way I could think is a data mining sort of approach but that sound like way too much work

.

Different games have different FOV's, when you look at each target on your screen, you don't do it based off angle movements in your whole 360 surround, you do it based off what fits on your monitor, and because FOV correlates to how much of the view fits in your screen you want a different sensitivity for each FOV to make everything 'feel' the same, that's how you build muscle memory better. Monitor match does this for different 'rings' around your crosshair, but these are really anything but arbitrary, for building muscle memory, your best bet is to learn the muscle memory exactly at the crosshair as this is the only way that it's independent of FOV and will translate across to other games. This is 0% monitor match

Ah okay, didn't know how USA worked, don't have battlefield.

@WhoCares? I've just posted a new thread with all the info on here:

you have two options, match with viewspeed V2, or monitor distance with a specific match percentage, you talk about EXACT same sens, but that's not going to work. It's impossible to do in practice, because that would be the same 360 distance for all zooms which is just ridiculous. You've selected uniform soldier aim. I don't have battlefield, but I think in this case it's the same as 56.25% monitor match (on 16:9 aspect ratio), so that hipfire sens generated will then transfer by that 56.25% monitor match across all scopes. I think you're better off turning uniform soldier aim off, and setting custom sensitivities with each scope FOV with monitor match 0%

I had this buried under another thread, but since people still want to use it, I've improved it and I'll put it in it's own thread here. It doesn't follow drimzi's pattern any more, so old macros won't work but you only need to press 1 now, the config files create the loop on their own. I've removed the need for brand specific keyboard macros, but they can still be used if you want, you only need to make it press 1 repeatedly, but I recommend using the script I've made called keypresser.py which does the same thing for all windows machines. Also, make sure zoom_mouse_sensitivity_ratio 1 is set before you start Download + Instructions here: https://github.com/Skidushe/sens-fov-scalar Recommended map: https://steamcommunity.com/sharedfiles/filedetails/?id=1104441138 I made a tutorial video here, the audio is a bit loud at some points sorry:

I recently pushed an update to the script I was going to create a post about but forgot, I've changed the file structure so rather than pressing 2 and 3 for each change, the scripts incorporate this so that you only need to keep pressing 1. I'll push my python script up to the same repository which does this so that you don't need any differences in keyboard macro software and everyone can use the same thing. I'll make a main post when I do this

I mean for scope sensitivities. is there an mm match or formula that fits their variation in scope sensitivites

Do you know what conversion they use?

Or if you have a smaller mouse mat, 180 degree rotation of character

I would recommend setting your sens so you can do 270 degree character rotation over the whole mouse mat

I'm gonna make some code changes tomorrow to put all the code in one, I've also made a python script that does the button pushing, and everyone can use python it's not keyboard software dependent

Mine's completely smooth throughout all the transition, you don't have some other scripts activating on other button presses do you?

I've added your script onto the same github repo

I find this map really good, because it takes the aspects of all the maps like training_aim_csgo_2 and aimbotz and that one where they all move towards you together, my fave setup is default, but you make the bots spawn also vary vertically https://steamcommunity.com/sharedfiles/filedetails/?id=1104441138