jabbothehut

On battlefield 4&1 there is the resolution scale option which allows you to super sample your resolution. I have a 1080p monitor but have my game running at 1280x1024 because muh 5:4. Downside is that the game looks like ass so would like to supersample up to 158%. Would this affect sensitivity in any way?

@DPI Wizard could you please add scoped sensitivity since they give the option for both ingame now Thanks!

BF rounds up to 74. Go to config and set fov as 73.74 to get a HFOV of 90

Coolbeans! Thanks for the help!

dude just realised I had a question for this; if I'm on a 1080p monitor but use 1280x1024 5:4 aspect ratio, would I still use 56.25% or would I use 80%?

Experiment with the two and see which one fits your playstyle better. In games with dynamic fov's i find viewspeed v2 keeps the fluidity and speed of your aim intact when you zoom in and that matching screen distance slows me down significantly as my brain is still thinking of the hipfire fov. MM at 56.25% however is perfect for converting sensitivity across static fov's (so hipfire at fov A to hipfire at fov b). Again this all depends on how fast the game is and on your playstyle. Hope this helps.

You're the best. Thanks a lot!

does viewspeed work dynamically in the calculator or is it screen dependent again like mm matching? @Drimzi

Could Far Cry 2 be added to the calculator please?

When you get to that stage when you know a sensitivity by heart it will make a difference since your brain is forced to make conscious calculations again to relearn.

Gotcha! Thanks for the answer m8ie!

Could you elaborate on what you mean by "the calculator is screen dependent". 56.25% feels fucking insanely good but I don't understand why it is different to the calculator's 100% value if they're both supposed to be 100%. I 80% get what you mean but am still a bit confused. Hope this makes sense.

Yeh saw all the stuff on viewspeed and got the message! Thanks anyways for the replies. A bit slow on this ;_;

@potato psoas Just re read through this forum and stumbled across this excellent post. Could you explain how you use the table of values to obtain the monitor match for selected FOV's since the calculator now lets you match at any value.

Awesome thank's so much for your time!

Gotcha! So the calculator method is the way to go then?

@potato psoas @Drimzi @DPI Wizard Just wanted your opinion on this guys; When I convert my hipfire to rds at 0% screen matching on rainbow six siege using the formula which DPIWizard provided me with (tan(106.26degrees/2)/tan(98.6degrees/2))*77.3461, I obtain an answer of 88.7038584629 This comes out as needing a multiplier of 0.726632 when inputted into the calculator as a "360 distance answer" as follows: Tom Clancy's Rainbow Six Siege - Iron sight Sensitivity 1: MouseYawSensitivity=1 Sensitivity 2: AimDownSightsMouse=2 Multiplier 1: MouseSensitivityMultiplierUnit=0.012896 Multiplier 2: XFactorAiming=0.726632 Ratio: 1 cm mouse movement = 1.6091 cm crosshair movement 360° distance: 88.7039 cm Discrepancy: 0% (0 cm) Config FOV: Field of View: 73.74 Actual VFOV: 66.37 degrees Actual HFOV: 98.6 degrees However when I convert purely using the calculator I get these results: Tom Clancy's Rainbow Six Siege - Hipfire Sensitivity 1: MouseYawSensitivity=1 Multiplier 1: MouseSensitivityMultiplierUnit=0.012896 Ratio: 1 cm mouse movement = 1.6091 cm crosshair movement 360° distance: 77.3461 cm Config FOV: Field of View: 73.74 Actual VFOV: 73.74 degrees Actual HFOV: 106.26 degrees Tom Clancy's Rainbow Six Siege - Iron sight Sensitivity 1: MouseYawSensitivity=1 Sensitivity 2: AimDownSightsMouse=2 Multiplier 1: MouseSensitivityMultiplierUnit=0.012896 Multiplier 2: XFactorAiming=0.726617 Ratio: 1 cm mouse movement = 1.6091 cm crosshair movement Discrepancy: 0% (0 cm) 360° distance: 88.7058 cm Config FOV: Field of View: 73.74 Actual VFOV: 66.37 degrees Actual HFOV: 98.6 degrees I know that the discrepancy lies within the decimal places and that I am maybe being too picky but when you get used to a sensitivity, any slight deviation is noticeable so it would be nice to invest effort into the more accurate multiplier. Thanks for your time guys.

It'll have to be tonight when i get home but it is essentially what Drimzi posted in the 2nd and 3d screenshots. Csgo to r6 irons is faster than r6 to r6 irons. Edit: it is just discrepency and I think I'm being too picky in this case.

Glad it isn't only on my end! Which one would you recommend? Matching at 0% between game A hipfire and game A ads?

Ok I understand what you guys are saying but then why do I get such large differences between matching different fov's of the same game. For example if I match R6s hipfire (73.74 vfov) to iron sights (66.37 vfov) I get 0.726617 as my xfactoraiming. However if I match hipfire fov at 73.74 vfov to hipfire fov but at 66.37 fov I get a 360 value that would require an xfactoraiming multiplier of 0.726647 to achieve. I don't understand why the value changes so much if that makes sense. Any help would really be appreciated.

Just a quick question. When MM% across games, what is the correct process? Do you match from game A hipfire to game B ADS or do you matrch from game A hipfire to Game B hipfire and then from game B hipfire to game B ads? Asking because I have noticed different multipliers being given when converting from csgo to rainbow six siege. If I convert from csgo hipfire straight to rainbow six ads I get a higher multiplier tahn if done from rainbow six hipfire to ads. Hope this makes sense and any help is appreciated.

Just a quick question. In certain game config files there is a limitation to how many decimal places a sensitivity multiplier can have. Adding more causes the game to round up or down and modify the config file. However if one was to add more decimal places and make the file 'read only' would it then proceed to read the whole value or would the game still round up/down? Any help would be very appreciated.

irons are the same as holo, rds, and reflex

Are the iron sights the same as rds zoom for pistols and AR's respectively? Also do the smg's use pistol or AR multipliers?

Problem is a lot of the pros don't really understand how sensitivity works. They all preach the "83" ingame value to get the same sensitivity without realising that fov changes also impact the sensitivity. Same goes for raw input, sens hasn't changed but the response time is snappier which feels weird on a brain that is used to slight input delay.