KandiVan

Imagine feeling the need to call something the R word and make a thread out of the inconvenience of having mouse acceleration on for 3 seconds while you login to your PC

Pretty sure its the same as titanfall 2 with HFOV 16:9. 1.0 is 0% monitor match just going off feel

Do we know what the FOV cap via the config file is?

Does the ADS value apply to every scope? Im assuming they just perform monitor match on each scope in game based on the value you input in config. I think its close? Its really hard for me to tell.

Im not sure where drimzi has gone either, but as far as Im aware we havent migrated. Could you give a link to an equation or excel spreadsheet for your method? I know the one you linked earlier you had said was probably incorrect

Hey @DPI Wizard, I matched via cm/360 for hipfire and ADS in H1 @ 0.08 (hipfire) and 0.160184 (ADS) and I realized the calculations for cm/360 on ADS in H1Z1 arent correct. I converted from 0.08 hipfire via cm/360 to the equivalent ADS sensitivity and this is what happens in game when I do a full swipe of my mouse pad with a rifle: http://plays.tv/video/5a7e83744f35f8d7fa/ads-calcs-arent-right-for-cm-360 As you can see, the ADS sensitivity is too slow as the same mouse swipe (within a reasonable margin of error) is consistently 10-15 degrees too short on the rotation back. I tried it with both the AR-15 and AK-47 and the same issue results. Further, this will consistently make every single calculation in H1Z1 for ADS sensitivity consistently too short, whether it be monitor distance, viewspeed etc. Any way we can get this fixed? Thanks in advance!

So ADS sensitivity is supported on the game now, has it been updated for that or do you just convert using the hipfire sensitivity and set as your ADS sensitivity? Seems pretty close doing the above imo

I saw that distance skew setting, what exactly is it? and thanks again for all your hard work!

Any update on this? There are multiple zoom levels now and im fairly certain ADS is incorrect. Seems far too slow for matching.

Whats the formula for CS GO's zoom 1 AWP scaling at zoom_sensitivity_ratio_mouse "1"? I was just playing around with it and it actually feels really good. Edit: Figured it out, it feels awful, disregard post

No, going ADS just zooms you in over the shoulder while maintaining third person over the shoulder. Camera scales back 1.67 m in hipfire and 1.1 m in ADS. Is there a way we could scale the first person config FOV kind of like how a microscope works? IE: Going third person increases FOV by scalar dependent on distance back from first person?

See, I feel like my issue is that im taking incredibly long range fights on relatively high FOV while ADS'd (61.84 vFOV). On top of that, movement is very sporadic in H1Z1 and I'm playing in third person, so I think there is FOV discrepancies as opposed to config FOV. Further, hitboxes are relatively small and headshots are HEAVILY favored. Pin point precision is an absolute requirement. As a result, most people just utilize incredibly low ADS sensitivity (50-60 inches on average) so that their margin of error is so massive you dont miss those crucial two taps. Likewise, they just utilize player movement for crosshair placement more than actual mouse movement. I may try to lower my config FOV which will bring down my ADS FOV as well, see if it gives me a little more leeway.

Is zoom ratio the same as 0% monitor match on the calculator? I've been using it for about two weeks. I dont know, I still feel like im wiffing shots I shouldn't be and it feels too sensitive while ADS'd.

Roger that. Significantly faster, will give it a try and report back.

I change y to "1" if im using vFOV on a 16:9 resolution correct? Is this correct for 1920x1080, 67 vFOV, 400 DPI 4/11 WPS

Do i maintain the 3/4 for "Y" if im using vFOV in this, it makes the overall cm/360 much larger if i keep it at 3/4 100% Monitor Match - 1:1 Diagonal Desktop, 1:1 Diagonal FOV

If we limit the fov range to limit distortion, say 60-80 vFOV, does it make finding a perfect solution easier? It always seems like the extremes of the spectrum are what cause us issues. I realize that with sniper scopes in other games it has to be done, but personally in H1 its pretty much irrelevant because the hunting rifle ~22vFOV is so rare and im not even my teams dedicated hunting rifle so i essentially never use it.

try taking viewspeed v1 (when my shotty flicks felt the best) and applying the FOV scaling from the above formula. I think thats what you were planning, but just verifying

Slow in general, i feel like I'm constantly tracking behind. The previous iteration i would just naturally re-adjust to the head. For the record, the lowest FOV I use is 61.84 vFOV.

The scaling of the previous formula was perfect, my hipfires feel good on this but ADS feels too slow, I dont know man why is this so difficult

and the multiplier (4) is changed to 2 if i play on 4/11 correct? or do i just change 400 to 200 if i play on 4/11, that gives a value that seems relatively close to what im looking for (~26 inches/360). Is this correct for 400 DPI, 4/11 WPS on 1600x900 desktop res with an ingame vFOV of 67?

Theres no option to change the FOV in those formulas? And the result is in radians? Need some more clarification on how to use them.

The last two iterations feel amazing, even in third person. If you havent found the perfect formula I'd say you are incredibly close. Will do more stringent testing in the coming days to verify my feelings. Great job guys!

Yea i use 200 dpi on 16x9. (400 dpi 4/11). Its quite easy to navigate with the mousepad space. Sensitivity is universal

Also think the 2D->3D conversion is a tad off but the fov scaling from hipfire to ADS is wonderful. 67->61.84 vFOV. (Thats for Diagonal 90 arc length)