4.1
the correct method is described here

maybe it feels weird, because your accel stays the same...

no...

that's the *q3* method. and it is far from 'correct'.

Loose the accel for a bit and get a good cm/360 going for the normal zoom. Now do the fovscript thing, get the right uhm numbers so that it matches the new fovs cm/360 with your regular zoomed sens.

Re-enable accel and you should be goodish to go unless they handle the accelstuff differently while zoomed. If so you might want to multiply the accel by the same factor you do the sensitivty and see how it goes.


Anyways never bothered to do this stuff with accel on so I might be a ton off :)



Edit: An alternative would be to construct a robot arm which moves the mouse at the exactly the speed you want and from that get a good cm/360 with diff kinds of accel but I somehow don't think it's worth the effort.

i don't use accel :)

Bust out your ruler then :)

it should be obvious that you want the sensitivity to decrease for zooming in. so 2 of your 3 options can be immediately discarded.

however, you seem to be under the impression that there is only one correct method of scaling sens with fov: this is not the case.

there are a number of methods that are sensible, it's up to you which one you like the best. some good ones are here:

1) ratio of horizontal fov

2) ratio of vertical fov (this is what q3 tries and fails to do properly)

3) tangent method (gives the same result whether applied to horizontal or vertical fov)

so what should the calculation look like? Sorry been almost 10 years since i graduated :p

1) ratio = zoomfov / fov

2) ratio = arctan[ h/w * tan[ zoomfov/2 ] ] / arctan[ h/w * tan[ fov/2 ] ]

3) ratio = tan[ zoomfov/2 ] / tan[ fov/2 ]

h/w is screen resolution heigh/width.


in order of most sensitive to least sensitive: 1,2,3.

http://www17.wolframalpha.com/input/?i=arctan[+1024%2F960+*+tan[+105%2F50+]+]+%2F+arctan[+1024%2F960+*+tan[+50%2F2+]+]

This gives a ratio of 7.5578785857 sounds kinda wrong?

yeah i made a typo. but you also need to tell the calculator that your fov is in degrees (its radians by default).

its also height/width, not width/height.

click

result: 0.4657

why did you use 105 degrees?

I'm quite sure their +zoom code uses #1 for their calculation, so if wanting the same feeling he should just use that one.

as i said, it uses a broken version of #2.

Have you seen QL's code? :o

QL uses Q3 code, and Q3 code is free, and you can se they try to use method 2.

what point of this script , then we have +zoom lol? :DDD

some ppl dont like to hold down a button while zooming?

some ppl can make script with +zoom , sens will be ok!

+zoom takes time to zoom in.

yeah 2 hours :(

That's pretty easy to bypass. For instance:
seta unzoom "-zoom"
seta zoom "+zoom"
bind MWHEELDOWN "vstr unzoom"
bind MWHEELUP "vstr zoom"

Optionally, you can also add "vstr unzoom" at the end of every weapon bind.

I think Guard has the best, pretty direct reasoning about all this ;x

this is hugely anal

not enough aparently

I've always used the information czm posted ages ago; I just decided what my base sensitivity and accel is going to be, decide what fov's I'm going to use for each weapon, and fire up quake 3.

Fire up quake 3, cl_showmousrate 1, set sensitivity to 1, turn on zoom and go through all the various fov's that I'm going to be using, logging the value coming up.

Just divide your base sense and accel values by these values you recorded for each fov. This will then keep your sensitivity and accel settings the same for each fov with +zoom constantly on. Then you just bind your zoom button as cg_zoomfov whatever you like, and have your zoomfov's as your actual fov in your weapon binds.

I have a base sensitivity of 2.9, pitch and yaw 0.022 and accel of 0.1 (IE 3.0 mouse), and this is whats in my config:

Weapon Binds:

bind z "weapon 1;cg_zoomfov 110;cg_crosshairsize 25;cg_drawcrosshair 7;vstr nrm110;bind mouse1 cg_zoomfov 60"

bind c "weapon 2;cg_zoomfov 90;cg_crosshairsize 20;cg_drawcrosshair 3;vstr nrm90;bind mouse1 cg_zoomfov 60"

bind capslock "weapon 3;cg_zoomfov 95;cg_crosshairsize 7;cg_drawcrosshair 7;vstr nrm95;bind mouse1 cg_zoomfov 60"

bind x "weapon 4;cg_zoomfov 110;cg_crosshairsize 25;cg_drawcrosshair 7;vstr nrm110;bind mouse1 cg_zoomfov 60"

bind q "weapon 5;cg_zoomfov 110;cg_crosshairsize 27;cg_drawcrosshair 2;vstr nrm110;bind mouse1 cg_zoomfov 60"

bind r "weapon 6;cg_zoomfov 100;cg_crosshairsize 30;cg_drawcrosshair 7;vstr nrm100;bind mouse1 vstr lg"

bind e "weapon 7;cg_zoomfov 90;cg_crosshairsize 15;cg_drawcrosshair 2;vstr nrm90;bind mouse1 cg_zoomfov 60"

bind f "weapon 8;cg_zoomfov 110;cg_crosshairsize 15;cg_drawcrosshair 2;vstr nrm110;bind mouse1 cg_zoomfov 60"

Fov scripts:

set lg "sensitivity 2.010102;cl_mouseaccel 0.089732"

set nrm110 "sensitivity 2.315482;cl_mouseaccel 0.0798442"

set nrm100 "sensitivity 2.602245;cl_mouseaccel 0.089732"

set nrm95 "sensitivity 2.767196;cl_mouseaccel 0.095420"

set nrm95 "sensitivity 2.949561;cl_mouseaccel 0.101709"

The lg vstr lowers my sensitivity to 2.3 with zoomfov 100.
Here are the ratios I found:

ZOOMFOV 110: 1.252439
ZOOMFOV 100: 1.114422
ZOOMFOV 95: 1.047992
ZOOMFOV 90: 0.983197

I've probably re-posted a lot of the information already there, but I hope this helps :)

OR

+zoom
set zoom_in "cg_zoomfov 50;sensitivity 8"
set zoom_out "cg_zoomfov 100;sensitivity 8"

dunno why they let people use these scripts but wont let us use cg_fov lower then 75

You're right. I'm quite sure the low cg_fov limit is so people do not use those scripts (because they are a stupid way of flooding the commands upload. I implemented low fov limit in wsw because of the same reason). But if people keep scripting with cg_zoomfov the problem persists. Using +zoom is the right way, -with zero upload consume-, of zooming.

you do know this is 2009 ? if peoples zoomscripts somehow affects the servers too much i think something is seriously wrong with the software.

You'd be surprised what users are capable of doing.

I think cg_fov and cg_zoomFov only affects how client views things. The server shouldn't be affected.

btw lol i didn't really know there was a limit at 75 fov in QL that is pretty stupid :p

limit is gonna be lowered a lot in the next update afaik.

Lowered to 10, same range as cg_zoomFov.

uh, 1st one

Do the guys who are constantly hitting around 50% lg accu zoom while firing the lightning gun?

In Quake Live, no. Anyone can hit 50% lg there =) in cpma i'm not really sure, i doubt most good people do it, but some do i know.

tbh some do, some don't.