Skidushe

How does the calculator convert between the two?

I don't know how complex you can get with your lua scripts, but you can normalise the zooming by making the the size of the intervals between zooms get larger as you zoom in. If you half the FOV, you get a 2x zoom, if you quarter the FOV, you get a 4x zoom, you can quickly see that zoom is directly proportional to k/newFOV, in this case k is the base fov, which in our case is 106.26, if you differentiate to find the rate of change of zoom, you can do the opposite of this to get the gap size between intervals

I've changed the script to now use the formula provided, I thought they'd be some guarded secret, but here we are: https://github.com/Skidushe/sens-fov-scalar It's now basically instant at creating the files, and you don't need to install any requirements now, just run the file

I know I posted this a while back when I didn't know anything and now I do, but thanks for the insight, still learnt a little more

How does this work on games reliant on FOV like PUBG? Also, I'll put that in the script tonight, it should make it a hell of a lot faster too, thanks

I felt like I wanted a large % for low zoom and a high % for large zoom as I didn't really care about flicking far off view when I was really zoomed in, has this idea been explored where mm% decreases as fov decreases?

With my script, I did 10% intervals from 0% -> 60% as 75% felt too fast: 0%: Feels really good on close targets, but far targets you need to hit are too slow 10%: Still feels really good on close targets, but far targets still sluggish to hit 20%: Far targets are still sluggish, but close range stopped feeling so good and felt uncanny 30%: Everything didn't really feel that good, far targets were better, but close also was comprimised 40%: Everything stopped feeling too far away to hit when it was on screen, or just left FOV, close range felt good 50%: Close seemed slightly comprimised but far away felt good 60%: Far felt good but close range felt really disconnected This leaves my to believe that my best monitor distance ratio lies between 40%-55%

I've attached a cue profile with the macro for executing the scripts, the toggle is the END key, place the files in the cfg file, exec the fov<min>+<max>.cfg, and press end with this cue profile and you should see it start to work FOVTestingCorsair.cueprofile You would have to change the number of times the 1 key is pressed on either side of the 2, as we can't do any pre-processing, but that's just a copy pasting exercise, it's setup by default for the FOV range 15-100 which from my testing seems adequate. Note that there is a 'remove all delays' button if you're having trouble with the delay blocks.

I have created a python script to create the files for the cs fov testing @Drimzi made with his lua script here : https://github.com/Skidushe/sens-fov-scalar It should allow us to test the different monitor distance ratios efficiently rather than copy pasting. You should be able to put the python file inside the cfg folder and then run from there if you want to do it that way too.

I hate to be naive here, but could you explain the cases tested, I don't understand what they're referring to from the calculator: 0% I assume is 0% monitor distance, 1:1 no clue, 4:3 no clue, 1:1 diagonal no clue, Viewspeed v2 from your formula, was this intended for 3d -> 3d conversion? I thought it was for taking a 3d -> 2d???

I understand this, however, if we're coming up to what feels natural transitioning from hipfire -> ADS or what ever FOV change there is, to an average human, I have the thought that mouse acceleration 'feels' the most natural even though it's the most inconsistent in terms of aiming, such that our solution is not simply one value out of a function

Just a thought, but has mouse acceleration ever come to mind when doing this 'perfect formula'?

Viewspeed in my head seems like the 'optimal' solution, however, in ads, is muscle memory more trained to distance or speed? For a real life example, if you push a brake pedal in a car, your muscle memory tells you how much pressure to apply much better than how far to push it, muscles are better at 'remembering' tension, is there an equivalence in this?