Quake Live

hey ...

really good work with this site!

1 small addition:

Quake live: it is possible to set your sensitivity below 1 with an autoexec.cfg. but the calculator always just says sensitivity too low.

Great job on the calculator, it's a lovely thing to use.

There is an error with the quakelive calculator however, it says the minimum setting is 1 and only configurable ingame.

Navigate to C:Users$user$AppDataLocalLowid Softwarequakelivehomeaseq3

and you can find/create the autoexec.cfg.

The setting:

set sensitivity ""0.5""

Will set the mouse rate to whatever you please, even values under one. I imagine this is also available with the console.

I see you've updated Quakelive with information on how to adjust the mouse using the autoexec.cfg. However the minimum value for sensitivity is still wrong.

I haven't tested it, but I imagine the limits of the sensitivity to be similar to valves products.

Hi, 

This is a rather in depth question but I'm trying to figure it out. Essentially I'm attempting to match my h1z1 hipfire and ADS cm/360 to my quake live hipfire and ADS sensitivities. I want them to all be the same cm/360. My goal here is to utilize quake to train for h1z1. The real issue i'm having is figuring out how to make the quake ADS match. 

If i utilize the commands "set sensitivity 1.35" and "cg_zoomsensitivity 1.35" will they be the same cm/360 while zoomed and not zoomed?

Hi, 

 

This is a rather in depth question but I'm trying to figure it out. Essentially I'm attempting to match my h1z1 hipfire and ADS cm/360 to my quake live hipfire and ADS sensitivities. I want them to all be the same cm/360. My goal here is to utilize quake to train for h1z1. The real issue i'm having is figuring out how to make the quake ADS match. 

 

If i utilize the commands "set sensitivity 1.35" and "cg_zoomsensitivity 1.35" will they be the same cm/360 while zoomed and not zoomed?

There's no point matching cm/360 unless you are using the same FOV. You need to convert via monitor distance otherwise the sensitivity will feel off even if the cm/360 is the same. As such don't bother changing the zoom sensitivity. Just pick the FOV you want to use for ADS, leave zoom sensitivity on default (1.0) and let the game figure out the ADS cm/360 you should be using. For the H1Z1 ads and scoped sensitivities just convert monitor distance same as you did for converting h1z1 to quake hipfire. I don't own h1z1 so I don't know if the game can automatically scale your sensitivities, but you can change them manually if you have to.

There's no point matching cm/360 unless you are using the same FOV. You need to convert via monitor distance otherwise the sensitivity will feel off even if the cm/360 is the same. As such don't bother changing the zoom sensitivity. Just pick the FOV you want to use for ADS, leave zoom sensitivity on default (1.0) and let the game figure out the ADS cm/360 you should be using. For the H1Z1 ads and scoped sensitivities just convert monitor distance same as you did for converting h1z1 to quake hipfire. I don't own h1z1 so I don't know if the game can automatically scale your sensitivities, but you can change them manually if you have to.

I've matched the FOV's in h1z1 and quake.

H1Z1 FOV = 65

Quake FOVs: cg_fov 80.69; cg_zoomFOV 69.91

Thus, cm/360 and all monitor distance values result in the same sensitivity value in H1.

If i utilize the commands "set sensitivity 1.35" and "cg_zoomsensitivity 1.35" will they be the same cm/360 while zoomed and not zoomed?

no. http://www.regurge.at/ql/

I've matched the FOV's in h1z1 and quake.

H1Z1 FOV = 65

Quake FOVs: cg_fov 80.69; cg_zoomFOV 69.91

 

Thus, cm/360 and all monitor distance values result in the same sensitivity value in H1.

Who in the right mind would play Quake with anything else lower than 120FOV? Unless you play against easy bots it's ok i guess but if you want to get any good at the game FOV has to be as high as you can get in Arena shooter like this where visibility is one of the most important things... especially if you play duels.

Who in the right mind would play Quake with anything else lower than 120FOV? Unless you play against easy bots it's ok i guess but if you want to get any good at the game FOV has to be as high as you can get in Arena shooter like this where visibility is one of the most important things... especially if you play duels.

The intent isnt to "become a better quake player" its to emulate H1 settings to become a better H1 player.

I noticed cg_zoomSensitivity isn't supported by calculator for Quake Live. 

Since CSGO was derived from the same engine as QL was, and my sensitivity is exactly the same in both games ... then assuming I set QL's cg_zoomfov=40 to match CSGO's single-zoom FOV, does that mean that QL's cg_zoomSensitivity should match CSGO's zoom_sensitivity_ratio_mouse to have an identical zoom sens?

I normally do a 50% match to my distance/360, any idea how I can incorporate that into the given formula?

Would like the option to convert for ADS in Quake... merci

Would like the option to convert for ADS in Quake... merci

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

Try 1.00981 zoom sensitivity.

 

 

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!

https://gyazo.com/bc0d8bb7d9da0af45d30591db318b5cd

There is nothing inherently wrong with my calculations, correct?

Let me know if it is correct because I'm not 100% confident in that formula. An option in the calculator would be ideal.

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

The formula uses the 4:3 fov value, not the actual hfov. I assumed the fov you gave me was the actual hfov, which translated to 58 fov and 68 fov.

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.

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.