KandiVan

While a contentious topic, I want to hear people opinions on this as it genuinely interests me. I'm somewhat stuck personally, I'm not sure what sensitivity to play on to be brutally honest. Has anyone come up with a scientific way to test and find what sensitivity (or range of sensitivities) you "naturally" excel at the most?

Im on the same page. H1 is the one game that I just cant seem to do viewspeed on the scoped and ADS sensitivities consistently. I've tried for months of training and just cant seem to nail it down. I personally think it has to do with how slow the character movement is and how finite your mouse movements have to be to track heads (small hitbox as well). Maybe dpi wizard could check the FOV's to verify they are still correct on the ADS and scoped? Regardless, I think its just the game itself.

CS uses Horizontal Deg | 4:3 Base. You've got it correct. You need to be on a cheat enabled server like Aim_Botz, all you do is type fov_cs_debug 80.69 in the console and the FOV will be match to 65 vFOV on warframe.

Tried it, but doesnt seem to be working

Pogchamp! Thanks Wizard take my one year subscription hehe FYI: This is the same result that stereo's first equation above got me. So his was correct and can be used to find viewspeed for cg_zoomsensitivity: https://www.wolframalpha.com/input/?i=1.754752%3D%3D2.031552+x+arctan%5B3%2F4*tan%5B72.93degrees%2F2%5D%5D+%2F+arctan%5B9%2F16*tan%5B83.93degrees%2F2%5D%5D Just correct the 2 sensitivities and the 2 FOV's and you're good to go!

Im so excited for this, love quake for aim training, gonna be so nice for training quick peaking when I can ADS and know its accurate

Input: Windows, 4/11, 400 DPI, 1920x1080 (Aim, sensitivity, and FOV not applicable) Output for quake: Base sens: 1.354368, main fov: 83.93, zoom fov: 72.74 (4:3 base), 1920x1080 in game res. Thanks in advance wizard!

yea I also think they added greater accuracy for sensitivity values, my config file looks similar.

Will that be in the near future? or could you post a wolfram alpha with the equation, y'know maybe if Kandi donates 20 dollars to the website? LOL. I feel like using ADS on quake is stalling my muscle memory cause its not perfect for viewspeed. Just wanna have it correct

Thanks stereo i'll give it a try EDIT: After testing its very very close. Would say its a tiny bit slow, but that could be human error.

Yes

I know you're busy with the forum upgrades DPI wizard, but any update on the cg_zoomsensitivity calculator for quake? Drimzi's method was close, but I still think theres more to it. The results I got from drimzi's formula are just a tad too fast I think.

PUB has an incredibly low FOV. Its hard to convert to it. Viewspeed unifies your crosshair speed across all FOV's, would argue its the best method for matching sensitivities. Some people have been using cm/360 for hipfire on PUB and then viewspeed for all of the scopes.

Yea i think it depends a lot on the game. H1 requires a lot of headshots, so I think a little bit lower than 106.26 hfov is ideal. Arena shooters like quake with large hitboxes can have much higher fovs (upwards of 120-130 hfov). I think for most games, hovering within 10 hfov of 106.26 is the "ideal" range.

Any way we could get a car sensitivity option as well for conversion? Also, I see this hasnt been updated since Z2. Im fairly certain they may have changed ADS FOV's since then. Any chance you could take a second look DPI Wizard? I've recently been turning a lot of people in the H1 comp community onto viewspeed and I want to make sure all of the information is correct.

So I take it its more complicated than the solution Drimzi came up with in the quake live thread IE: Whatever cg_zoomsensitivity value I came up with is more than likely wrong?

Lots of complaints in the PUBG thread because the FOV is so low on that game ~47 VFOV. General consensus is that sensitivity feels "too slow". Opposite on the high end, sensitivity feels too fast. What you're saying makes sense though.

I've noticed that players are having issues with viewspeed at the extremes of the FOV range (high and low)so that got me thinking, is there an ideal FOV that matches the best from 2D (windows/desktop)? There might be something I'm completely missing here, but who knows, figured I'd ask.

Use viewspeed, i think ~70% monitor distance matching equates to viewspeed, but its better to just use viewspeed

If PUBG is still requiring you to use that low ass FOV, thats why your sensitivity feels so slow. dpi wizard pls check your DM's and help me i love u

Ok I used the 4:3 fov value (which is what is used for cg_fov and cg_zoomfov in quake), so my calculations should be correct. To elaborate, for hipfire, my 4:3 hfov is 83.93 (used in calculation), my vfov is 68, and the actual hfov is 100.34 (because im playing on 1920x1080); ADS, my 4:3 hfov is 72.93 (used in calculation), vfov is 58, and actual hfov is 89.15. So i should have no discrepancies in my calculations, assuming the initial formula is correct.

my flicks feel great, so I have to imagine its pretty close

https://gyazo.com/bc0d8bb7d9da0af45d30591db318b5cd There is nothing inherently wrong with my calculations, correct?

you the real MVP, you know that right? Thanks buddy Edit: actually, those FOV values dont seem to match mine. I calculated so that the VFOV is 68 and 58 for my cg_fov and cg_zoomfov, respectively. I'll just plug in the values though, thanks!

Bumping this up. Would also like this option, tried drimzi's solution but couldnt quite get it to work for me. Unless drimzi knows how to do it for viewspeed? For me, sensitivity is 2.031552 @ 400 dpi, cg_fov = 83.93, cg_zoomfov = 72.93