Quake Live

[KandiVan]

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.

[stereo3D]

it's too fast because zoomsensitivity is bugged at aspect ratios other than 4:3.

https://www.reddit.com/r/QuakeLive/comments/5ztk6d/169_zoom_sensitivity_algorithm/

 

try this:

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

[KandiVan]

it's too fast because zoomsensitivity is bugged at aspect ratios other than 4:3.

https://www.reddit.com/r/QuakeLive/comments/5ztk6d/169_zoom_sensitivity_algorithm/

 

try this:

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

 

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.

Edited April 29, 2017 by KandiVan

[stereo3D]

i know what you mean. give match 100 % a chance: https://www.wolframalpha.com/input/?i=1.804999%3D2.031552*x*arctan%5B3%2F4*tan%5B72.93degrees%2F2%5D%5D%2Farctan%5B9%2F16*tan%5B83.93degrees%2F2%5D%5D

[DPI Wizard]

I got calculations for this game ready, but need to make some changes to the code to support the variables.

[KandiVan]

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

[DPI Wizard]

2 minutes ago, KandiVan said:

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

It will probably take a few days at least, but I can do it manually for you in the meantime. If you tell me the numbers I'll do the math!

Input: Game, aim, sensitivity, dpi, resolution, fov.

Output for Quake: base sens, main fov and zoom fov.

[KandiVan]

6 minutes ago, DPI Wizard said:

It will probably take a few days at least, but I can do it manually for you in the meantime. If you tell me the numbers I'll do the math!

Input: Game, aim, sensitivity, dpi, resolution, fov.

Output for Quake: base sens, main fov and zoom fov.

 

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!

Edited May 1, 2017 by KandiVan

[Drimzi]

Edited January 28, 2018 by Drimzi

[DPI Wizard]

Ok, will look at it tomorrow.

[KandiVan]

17 hours ago, DPI Wizard said:

Ok, will look at it tomorrow.

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

[DPI Wizard]

22 hours ago, KandiVan said:

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.

cg_zoomsensitivity 0.799424

21 hours ago, Drimzi said:

Input: Windows/Desktop, 3/11, 1600 DPI, 2560x1440

Output: Quake Live, 3/11, 1600 DPI, 95 hFOV (4:3 base), 0.579149 base sensitivity, 65 Zoom hFOV (4:3 base)

cg_zoomsensitivity 0.830876

Converting from Windows or Quake Live hipfire with your settings (both of you) yield the same result, so it's viewspeed all the way!

[KandiVan]

4 minutes ago, DPI Wizard said:

cg_zoomsensitivity 0.799424

cg_zoomsensitivity 0.830876

Converting from Windows or Quake Live hipfire with your settings (both of you) yield the same result, so it's viewspeed all the way!

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!

Edited May 2, 2017 by KandiVan

[DPI Wizard]

Just published this update now

[KandiVan]

6 minutes ago, DPI Wizard said:

Just published this update now

Tried it, but doesnt seem to be working 

 

[DPI Wizard]

I see what's wrong, gimmi a sec!

[DPI Wizard]

Now it works

[potato psoas]

So which FOVs do we put where? The note doesn't say anything about the zoom fov so I assume you put zoom fov in the normal fov field but put your hipfire fov in the Sensitivity 2 field - is this correct?

[DPI Wizard]

2 minutes ago, potato psoas said:

So which FOVs do we put where? The note doesn't say anything about the zoom fov so I assume you put zoom fov in the normal fov field but put your hipfire fov in the Sensitivity 2 field - is this correct?

Correct, I'll update the notes to be clear about this.

[potato psoas]

thanks wizard

[Dribbler]

I tried to convert my normal QL sens to QL zoom sens and results were complitely wrong.. So here are the steps ive done:

1) Im using 800x600 res, 800 dpi, 2.5 ingame sens and 90 fov in QL

2) Wanted a flat convertion from 90fov 2.5sens to 45fov and 2x times slower sens when zoomed

3) Used match monitor distance by 100% to get those results , so according to calculator if i want my 20,7818cm per 360 (which is sens 2.5 and 800 dpi) become 41,5636cm per 360 when using zoom_fov 45 my cg_zoomsensitivity should be 0.850558

4) Tried that ingame and instead of 41,5cm per 360 when zoomed i end up with 50+cm..

Is there a mistake in your zoom formula? Mb it somehow has to deal that im using 4x3 aspect instead of 16x9, but thats just a guess

[Audile]

I'm trying to run this on a 21:9 screen and something just doesn't seem right about the FOV values I'm getting from the calculator (103 doesn't feel like 132 HFOV)

Am I doing something wrong here?

Cheers

[DPI Wizard]

14 minutes ago, Audile said:

I'm trying to run this on a 21:9 screen and something just doesn't seem right about the FOV values I'm getting from the calculator (103 doesn't feel like 132 HFOV)

Am I doing something wrong here?

Cheers

This game had the wrong FOV type, updated it now.

[ScottyFPS]

10 hours ago, DPI Wizard said:

This game had the wrong FOV type, updated it now.

I always wondered why my tracking felt so different in this game despite using the same FOV as Overwatch. Thanks for everything!  

[Audile]

On 8/23/2020 at 8:51 PM, DPI Wizard said:

This game had the wrong FOV type, updated it now.

Hey again,

Has it reverted to a different FOV type? I'm getting some values that don't feel right...

Cheers!