MuntyYy

No, it does not scale as it should as far as I can tell, because the FOV of the scopes are wrong. I tested with a scope that is supposed to be 4x, and the sensitivity (360 distance) scales correctly if the FOV of the scope had been 1/4 of the configured FOV, but since it in reality is quite a bit higher, the scaling is completely off.

It should work, but if you already have the heading [/Script/Engine.InputSettings] in the config file, you can't add it again. Just add the smoothing line under it:

If this is what you are doing and it still gets removed, the only thing you can do to fix it is to lower your polling rate to 250 Hz or even 125 Hz.

Update: For Conan Exiles, theres a new mod that does the trick - for anyone needing it 

I have updated this game now:
Fixed the FOV so it mimics the game's limitation of maximum 130 hdeg res. Updated the sensitivity calculation to use the 16:9 FOV, this corrects any errors with ultrawide etc. Added instructions on how to disable smoothing. Added config file sensitivity for better accuracy.

What you said, doesn't make much sense.
Your hipfire sensitivity, for the sake of argument its 10 in overwatch ( 34.6364 cm/ 360 ) converting that to a game with a similar FOV ( either by viewspeed v1, v2, mm 10000% ) will give your the same amount of 360 distance. You then said whilst adsing you use 0% mm ( that's where you should have viewspeed 1 - hence you "prefer" it over the other methods ).
Also 0% mm its same as all the other values in hipfire, thus your assumption of  "acquiring your target first before zooming in" - its false.

This statement doesn't stand for 100% mm. Indeed, you would move more or less degrees with different aspect ratios, but the movement will be exactly the same from the crosshair to the edge of the screen. If that's not improving your muscle memory then what it is ?

Take for instance, this example, using an aspect ratio of 32:9 ( super wide; I know its a bit extreme, but it will prove more than I stated above ).


It takes the same amount of movement to reach the edge ( from the crosshair ) that is 9 cm. Of course, the 360 degree distance got quite reduced due to the fact that your FOV is much larger, but your distance to the very edge remains unchanged.
Now with a 00% monitor match, in the same scenario - the following occurs


Look at the 360 degree movement. That's one of the biggest disadvantages when it comes to 00% ( which is a known fact ). One might say, "no one uses such extreme aspect ratio", yet the most versatile method is in fact the 100% monitor match.


The examples I used, are my personal preference as it's easier to get used to 100% mm with a lower sensitivity, which is again, solely based on my tastes and feel as I don't condone anyone to follow my biased judgment. I'm just questioning stuff.
So m y question for y'all, is .. Which monitor distance will likely maintain and improve your aim ?  I'm not talking about "the long run" for the simple fact that If you played a game for a given amount of time, and become used and develop a certain skill for it then you can make it work with any method.

I don't think you get it. Distortion will still be present regardless of your monitor match percentage. However choosing 00% may be the most logical cuz you ain't matching to a "random" point on your screen. If you go up or down in the game  world you will still spin instead of going left or right due to how the matrix is designed.

Ask Microsoft what they broke in 1703, partially fixed in 1709 and broke again in 1803. 1809 does not require any mouse fix but it suffers from other things like the inability to change HPET. Raw input in csgo isnt using raw input method, it just disables WM-Input and uses direct input. Set rawinput to off tells csgo to also use direct input but it doesnt ignore WM settings and such.
In theory the mousefix shouldnt affect raw input in the first place..(but somehow it does on the versions I mentioned) because all its changing is WM-input which is being ignored when turning raw input on.. its meant to fix mouse movement of legacy games which havnt had raw input..

@WhoCares? Microsoft fucks up on a daily basis, different version of windows might or not require the fix. It can differ based on mouse as well and, even if it has the same sensor the srom outputs a different signal. We are doing a comprehensive analysis on different os'es we've dropped 1809 (as it has a locked 10mhz frequency even disabling it in bios won't work, thus the only timer thats effective is tsc, pmt is unavailable) 1709 might be better, but 1151 ltsc looks solid. Check out this results:
https://cdn.discordapp.com/attachments/533881637948096522/562236395834572820/unknown.png
https://cdn.discordapp.com/attachments/533881637948096522/562236447088967690/unknown.png
and that achievable with little to no tweaking BUT with hyper threading ON :(.
Win7 and 8.1 are in testing as well, but it will take time till anything is concluded.

@WhoCares? @spyder256 @Pyroxia @Dribbler @DeDa I've edited the post, you might wanna take a look. 

Windows 10 1809 Build 17763.379
The hardware is i9-9900K and 2080 TI.

WOW I tried this and it feels very comfortable on desktop.

I wish that was so, but I doubt it works on games with built in acceleration and/or inaccurate count registration?
Like Arma 3 or Mass Effect 1 for instance. I'm not able to test now, but will tomorrow.

Okay, than I wont use this fix together with WPS 3 😅
I will play this evening with wps 6 and this fix and give some feedback  
 
You should include in your start-post that this fix is best with WPS 6. I know a lot of People using WPS 3 😁

Good thinking will edit now.
 

unchecking pointer acceleration its a meme, you can see the path by clicking edit on the reg

Hello guys,
First post after a long, long break. I've attached a reg fix that works for win 10 (certain versions see bellow) and 8 (will edit it when I have it for 7) at 100% scale & wps 6
What it does, is unlike Markc fix it actually removes the entire acceleration your system exhibits, markc is pretty much a meme since it removes it just from one entry.
Happy fraggin,
Munty
ps: send some love to this guy: Zoyata#7364 (discord)

EDIT1: In some w10 versions even raw input in games is still bad as follows:
1507 -> requires mousefix
1511 -> requires mousefix
1607 -> i dont know?!
1703 -> i dont know
1709 -> mouse will occasionally spin out without the fix
1803 -> fixed bug with not using rawinput in csgo
1809 -> doesnt need mousefix
so 1809 doesnt need any mousefix, 1809 works best AT DEFAULT!
Here's a spreadsheet with what each fix changes: https://docs.google.com/spreadsheets/d/15-vKik4jV354SZdSppTtDW3LvvvrNdC1iT3yDKGp_dw/edit#gid=0
 
EDIT2: Check this video out if you want all the good stuff that we've been working at - https://www.youtube.com/watch?v=3dE1Dc2JQrY&feature=youtu.be
Someone needed to step up and compile pretty much all the good tweaks that are scattered all over the internet, that "someone" is FR33THY. Join the discord if you want to help or just be up to date with everything.
EDIT3 (4.19.2019): The flat curve should be in use only when playing games that either dont support raw input or you simply play  them without raw input. It should in theory remove the window's acceleration as thats the flatest achievable curve. You can check that out and much more using this little program - https://github.com/TemporaryName/PointerSpeedSetter
That said, you can safely apply it in all win10 versions, (ignore the info thats present at edit1) but make sure you have the default registry  (check the attachments)  as well backed up.
You should either have no mouse fix applied to your registry and play games that have raw input, or use the "flat line" (attached) and play them WITHOUT raw input. The only drawback in playing without raw input (and mouse fix) is that some win10 versions might bug out your mouse input and make it spin out. I urge all you guys to check FR33THY's guide and join our discord, I was helped by many of you here, I want to be of help to some as well.

Much love,
Munty
Zoyata_Mouse_fix.reg
MARKCTOALLKEYS.reg WIN10DEFAULTALLKEYS.reg

Much appreciated !

A mod I made that allows you to customize zoom sensitivity recently got approved for official realm.
By default the mod makes zoom sensitivity scale with focal length/zoom ratio but you can change it to scale by a custom FOV aspect ratio (aka monitor distance).
The game uses vertical FOV to scale by default.
https://steamcommunity.com/sharedfiles/filedetails/?id=1498189723
Unrelated to sensitivity but using the same math I also made a mod that fixes crosshairs: https://steamcommunity.com/sharedfiles/filedetails/?id=1569650837

It's not forgotten! Just had to put it on hold while prioritizing some code updates and BFV.
I think turning off Scale sens by FOV solves the issue for both Insurgency games, so that will probably be the solution. I'll do them both very soon!

Use the Mouse Mod linked in the notes to disable acceleration and smoothing.

The mod fixed it, just added the game!

you need to consider the actual design of your mouse skates as well if your using a softer pad like the ARTISAN 'soft'.
For example, larger skates will distribute pressure over a larger area, making the pad able to resist more downward force relative to how far the skates will 'dig' in. Some of the new mice come with skates that are really small and will do the exact opposite. Another factor with a really soft pad is the bottom of your mouse, if your skates are 1mm thick then you will understand as you play the bottom of the mouse will also rub on the pad more. If you have thicker skates, they will simply dig in more and create further resistance.

Again, all this really depends if you can always play with a light hand. I cant, so it's not for me.
 
A quick note on the GSR, the surface is really slick, it allows your hand to glide over the pad just as well as the mouse. A PLUS in my books. I hated the GSR originally (the very high static friction) however i started using my favorite 'cleaner' on it. Mr Sheen, it contains all kinds of chemicals that make things shiny and repel dust! You just spray a LITTLE on a microfiber cloth and wipe it over. You will instantly see it feels completely different, i actually use this on all my pads.

I'll try!

I've added iron sight now. Scope has the same issue as in Sandstorm in that it scales the wrong way when changing FOV... It's really strange that they kept this design, it makes no sense!