Well I use this for zooming and it always felt pretty good:
cg_fov "106"
cg_zoomfov "70"
cg_zoomToggle "1"
cg_zoomSensitivity ".7"
cg_zoomOutOnDeath "1"

zoomsensitivity .7 is 70 percent of the normal sens.
Since my fov is 70 when zoomed and my normal fov is around 100, I guess you could say my fov and sens lower almost the same amount when zoomed in (70 percent). So if I had zoom fov of 50 maybe I'd use .5 zoom sens... but tbh I just go on how it feels, working things out with maths is only good when it feels good, imo!

Found this though :D
http://www.esreality.com/post/2235053/zoom-fo...pid2235163

\cg_zoomsensitivity 1

This will calculate it for you as long as you use +zoom. Don't touch your \sensitivity.
Small mouse movements translate almost linearly to "crosshair movements" over "static background". Your muscle memory should work as before in close proximity to the crosshair.

Tbh if you switch from fov 105 to 70 it wont feel the same in most situations and you will need to get used to it anyway.

The idea would be that I not use +zoom but rather switch from cg_fov 105 to cg_fov 70 within the weapon binds. Thus not using cg_zoomfov , +zoom or cg_zoomsensitvity settings.

For example : Imagine that rapha plays on fov 110 with sens 5, for a the tournaments he decides to use to fov 90. Should he switch his sensitivity or keep with sens 5?

If he will switch sensitiviy, is there a 'calculation' for it?

Thanks.

He could do either, theres no rule, its personal prefence (ie, the fov doesn't actually change your sensitivity, it just changes how it looks), but if he wanted it to change his sens so it looks more similar, then he would probably use the calculation I already gave you in my post above:

http://www.esreality.com/post/2235053/zoom-fo...pid2235163

Sorry, missed that one. T hanks!

when you switch fov sensitivity stays the same

Sorry, but I would argue with you about that :)

When you think about it, I am agree with you that the sensitivity stays the same, but the feeling of this sensitivity changes the lower you set your fov. A good example would be playing with fov 100 and then immediately switching to fov 50. In this case, the sensitivity setting stays the same, but a low fov value makes it feel higher. Although something like that would never happen with zoomfov, as no matter what value you set zoomfov, the sensitivity feeling doesn't change.

And I guess that is why the OP is so concerned about :)

For small fov changes, like 110 to 105 or so, the calculation is definitely not worth the trouble.

The zoom algorithm (assuming zoomsens 1) multiplies the sensitivity by k, where:

k = arctan[ 0.75 * tan[cg_zoomfov°/2] ] / arctan[ 0.75 * tan[cg_fov°/2] ]

Here's a template you can use:

http://www.wolframalpha.com/input/?i=+arctan%5B+0.75+*+tan%5B70%C2%B0%2F2%5D+%5D+%2F+arctan%5B+0.75+*+tan%5B105%C2%B0%2F2%5D+%5D

So going from fov 105 to fov 70 would be sens * 0.6248

For the bind:

bind v "vstr rg1"

set rg1 "weapon 7 ; cg_fov 105 ; sensitivity 5 ; bind v vstr rg1"

set rg2 "weapon 7 ; cg_fov 70 ; sensitivity 3.124 ; bind v vstr rg2"

However you will have to add something to all weapon binds to reset the fov and sensitivity, for example:

bind [key] "weapon 5 ; cg_fov 105 ; sensitivity 5"
bind [key] "weapon 3 ; cg_fov 105 ; sensitivity 5"
etc.

Another way to do this would be to simply use the +zoom feature and it will calculate the changes for you:

cg_fov "105"
cg_zoomfov "70"

bind v "vstr rgg"

set rga "weapon 7 ; -zoom ; bind v vstr rgb"

set rgb "weapon 7 ; +zoom ; bind v vstr rga"

Other weapon binds will need:

bind [key] "weapon 5 ; -zoom"
bind [key] "weapon 3 ; -zoom"
etc.

Note: This is for a 4:3 screen, as there appears to be a bug with the zoomsens calculation at other aspect ratios at the moment.

I think this is what i was looking for.

I play with the same fov for all weapons but I change it for rail (90 fov).

I want to use the same sens and accel for all weapons, but when I go from my fov 110 to the 90 fov of the railgun, I want to have absolute 1:1 feeling of both sens and accel. Is that algorithm useable for accel values too?

Im using a 16:10 screen but im using a 4:3 resolution.
When you say there is a problem with non 4:3 resolutions you are talking about the +zoom method or the algorithm works with any screens?

btw, if im on a 16:10 screen but im using 1280x960 (a 4:3 resolution with dem black lines at the sides) do I need to set r_aspectratio to the 4:3 option or set it 16:10?

Is there something else i should look for?

For 1280x960 you can use the +zoom algorithm and it will be correct as this is a 4:3 resolution.

The algorithm is usable for accel values as well. When using +zoom it also multiplies cl_MouseAccel by this factor.

I dont understand the +zoom thing. How do I do it so its fov 95 for railgun and 105 for the other weapons

Just do it manually : z * arctan[ 0.75 * tan[cg_zoomfov/2] ] / arctan[ 0.75 * tan[cg_fov/2] ] with z being sens then accel, it's what the ql zoom algorithm does except by doing it this way you're sure you won't get any of the weird fuckups that a widescreen res seem to cause. Just add the different fovs and stuff to your binds and you're done.

Ok, in that case will do it manually as fairie suggested:

k = arctan[ 0.75 * tan[95°/2] ] / arctan[ 0.75 * tan[105°/2] ]
k = 0.8862

x = sensitivity for the "other" weapons
y = sensitivity for the rail gun

y = x * k

a = mouseaccel of the "other" weapons
b = mouseaccel for the rail gun

b = a * k

bind [key] "weapon 1 ; cg_fov 105 ; sensitivity x ; cl_mouseaccel a"
bind [key] "weapon 2 ; cg_fov 105 ; sensitivity x ; cl_mouseaccel a"
bind [key] "weapon 3 ; cg_fov 105 ; sensitivity x ; cl_mouseaccel a"
bind [key] "weapon 4 ; cg_fov 105 ; sensitivity x ; cl_mouseaccel a"
bind [key] "weapon 5 ; cg_fov 105 ; sensitivity x ; cl_mouseaccel a"
bind [key] "weapon 6 ; cg_fov 105 ; sensitivity x ; cl_mouseaccel a"
bind [key] "weapon 7 ; cg_fov 95 ; sensitivity y ; cl_mouseaccel b"
bind [key] "weapon 8 ; cg_fov 105 ; sensitivity x ; cl_mouseaccel a"
bind [key] "weapon 9 ; cg_fov 105 ; sensitivity x ; cl_mouseaccel a"
bind [key] "weapon 11 ; cg_fov 105 ; sensitivity x ; cl_mouseaccel a"
bind [key] "weapon 12 ; cg_fov 105 ; sensitivity x ; cl_mouseaccel a"
bind [key] "weapon 13 ; cg_fov 105 ; sensitivity x ; cl_mouseaccel a"

THanks. How many decimals can QL read? 4 or more?

I believe it is type double, so it would be 15 digits of precision.

Er edit, the q3 source uses float for sens, so QL likely does too.

That would be ~7 digits of precision depending on the number.

When applying the algorithm, I tried (with accel 0) to move and see the cm I move from one corner of the mousepad to the other. Is it normal that I rotate less angles with the higher fov (105) compared to the lower fov (95) ??

No, that does not make sense, unless there is accel from the mouse sensor/mouse drivers, or issue with the test.

Mouse sens ultimately degrees per count and has nothing to do with how it is displayed (fov).

Are you using viewpos? Ie. making sure that your two points are precise with it before changing settings for a test. The last number is your horizontal orientation in degrees relative to some point in the map.

What is viewpos?

What I did is get in front of the ZTN pillar (GL) and align myself on there on the edge of the pillar. I would start from the left edge of the mousepad to the right.

Then I would switch to rail (the weapon I use less fov with) and did the same.

I rotated more with 105 fov than with 95 fov.

I got my sens values here:

http://kyto.dez.fi/ql/zoomsens/index.php

Im using MarkC builder to get rid of any extra accel and precision pointer is off in the controller. I have a WMO at 500hz.

In a practice game (although it should work online too) open the console and type 'viewpos', and it will give you some numbers. The last number is what you want.

For example, looking at that ztn pillar (back of the pillar, player facing towards sg)) and performing that same motion I would go between -7 and 16 degrees.

Are you using the zoom command to change fov? Like do you play zoomed in all the time, and have each weapon change cg_zoomfov? If so then +zoom will internally scale your sensitivity.

The lower the fov the lower the sens (and so the converse is true) to keep the same feeling across fovs.

Otherwise make sure cg_weaponconfig doesn't have any sens changes, or none in the weapon bind. Also is in_mouse 2?

No, i just using different cg_fov and different sens taken from the link i pasted (its basically the same old algorithm)

will try viewposs later

yes in mouse 2

Hey man, I see you are real good with scripts, can you help me with this:

http://www.quakelive.com/forum/showthread.php...vel/page55

Same happens to me. I also would like how to configure each weapon individually.

I use a different xhair and xhair size for PG and SG, then I use a different xhair and xhair size, sens and fov (what we are talking about here) for RG (all of this NOT during fire, I mean permanent when you swtich to said weapons) then I want the LG to have lower sens during pressing fire, everything else is the same.

I have tried for hours trying to modify Yakuma script with no success :(

alias +zfire "Lgsett"
alias -zfire "-attack; sensitivity A"

alias normal "alias +zfire +attack"

alias Lgsett "alias +zfire LgFire"
alias LgFire "+attack; sensitivity C"

bind [key] "weapon 1; normal ; sensitivity A ; cg_drawcrosshair a ; cg_crosshairsize a" // GT

bind [key] "weapon 2; normal ; sensitivity A ; cg_drawcrosshair a ; cg_crosshairsize a" // MG

bind [key] "weapon 3; normal ; sensitivity A ; cg_drawcrosshair b ; cg_crosshairsize b ; cg_fov A" // SG

bind [key] "weapon 4; normal ; sensitivity A ; cg_drawcrosshair a ; cg_crosshairsize a ; cg_fov A" // GL

bind [key] "weapon 5; normal ; sensitivity A ; cg_drawcrosshair a ; cg_crosshairsize a ; cg_fov A" // RL

bind [key] "weapon 6; Lgsett ; sensitivity A; cg_drawcrosshair a ; cg_crosshairsize a ; cg_fov A" // LG

bind [key] "weapon 7; normal ; sensitivity B ; cg_drawcrosshair c ; cg_crosshairsize c ; cg_fov B" // RG

bind [key] "weapon 8; normal ; sensitivity A ; cg_drawcrosshair d ; cg_crosshairsize d ; cg_fov A" // PG

bind [key] "+zfire" // Attack key

For sensitivity:

Replace 'A' with your common sensitivity.
Replace 'B' with the lower sens you want on the RG.
Replace 'C' with the lower sens you want to have when firing the LG.

For cg_drawcrosshair:

Replace 'a' with the common, or default crosshair number you use.
Replace 'b' with the crosshair number you wish to use for the SG.
Replace 'c' with the crosshair number you wish to use for the RG.
Replace 'd' with the crosshair number you wish to use for the PG.

For crosshairsize:

Replace 'a' with the crosshairsize number you wish to use as a default, common setting.
Replace 'b' with the crosshairsize you wish to use for the SG.
Replace 'c' with the crosshairsize you wish to use for the RG.
Replace 'd' with the crosshairsize you wish to use for the PG.

I notice the following with your script:

When I select for example SG it has the crosshair I want, but as soon as I shot it gets the "common" crosshair permanently selected

Also when I run out of LG ammo and the weapon changes to any other weapon the script is still running (when I press mouse1 I get the lower sens) so I have to manually press the bind of the weapon.

Also when firing and pressing the LG bind to change to LG it doesnt work until you stop clicking and then click again

This sucks. I wish they implemented all of this shit in-game. Its buggy as hell

When I select for example SG it has the crosshair I want, but as soon as I shot it gets the "common" crosshair permanently selected

This should not happen.

Can you pastebin your config?

Also when I run out of LG ammo and the weapon changes to any other weapon the script is still running (when I press mouse1 I get the lower sens) so I have to manually press the bind of the weapon.

Are you a premium or pro member? I believe this could be mitigated with the premium/pro only cg_weaponconfig options.

Also when firing and pressing the LG bind to change to LG it doesnt work until you stop clicking and then click again

Why would you press the lg bind while firing? I might be able to correct this as well. I would like to see the config you are using though to get a better view of the problem.

I meant for example during a RL fight you are clicking mouse1, and during said fight while STILL pressing mouse1 you press X or whatever you have binded LG to to not lose any time and start shotting LG as soon as possible.

Anyway here are my weapon settings and how I set it up with your script:

http://pastebin.com/JH8YhSBf

as you can see im already usign the premium weapon settings feature

Ok, try this:

http://pastebin.com/EsNsiiwt

This solves the problem of the sens not changing right when out of ammo.

It also fixes the problem of your crosshair resetting to the common one when you press attack on weapons are not supposed to use it.

As for the problem of holding down the attack button while shooting the RL, and then switching to LG, am I right in that you want the sens to suddenly lower to the +LGfire sens upon switching since the attack key is being held down?

This might not be possible but I have an idea to try.

When out of ammo it changes to the correct sens but not to the correct xhair/fov

Ok!

I believed I have fixed all of the aforementioned problems.

Here is the script:

http://pastebin.com/nZZJyQxN

I didn't have time to test it really thoroughly, but it seems to work.

Hopefully no parts remain from my "testing framework", I think I got them all.

With this you can have for example RL selected. Hold down the attack button, then switch to LG and have the sensitivity lower to what it would be if you had selected the LG first, and then pressed attack.

Releasing attack returns the sensitivity (and accel) to normal. The same happens if you have the button held down with the LG, and switch weapons.

Let me know if it works and if there are any issues.

Just tested it.
Yep, it works now when switching from any weapon to LG and from LG to any weapon. Sens change, correct xhair, correct fov.

But there is still a flaw: When you run out of ammo from LG and it switches to rail (different xhair and fov) or SG or PG (different xhair) the sens changes but the xhair and fov remains the one of the LG.

Ok, should be fixed now:

http://pastebin.com/chFre1uP

I also gave it a little bit easier framework for on-the-fly config adjustments.

alias rgsens "sensitivity 2.9486569 ; cl_mouseaccel 0.2215527"

lolwut

edit: okay, because of FOV change.. :D

There is still something wrong on there. When you are shotting LG and run out of ammo, the low sens is still applied to whatever other weapon it automatically is switched, so you have to press the bind key of the weapon it automatically switched after being out of LG ammo s you aren't stuck with low sens. It seems now it changes automatically when out of ammo to the correct sens but as soon as you click again the low LG sens is applied to whatever weapon you are using.

Also, when you press again X (or your LG bind) while you are firing LG the sensitivity goes back to normal (3.25) for some reason. This can fuck up easily a LG battle if you by accident press your LG bind during the fight.

This version should have both issues fixed:

http://pastebin.com/WvVifFF4

I detected another glitch:

Let's say you are firing any other weapon that isn't LG, lile RL. You are pressing MOUSE1, then (while still pressing MOUSE1) you press X to change to LG, and right before the LG beam starts shotting you stop pressing MOUSE1. At this time the script is stuck with the LG low sens. If you change to any other weapon then go back to LG, the low sens is still there. To make it go to normal sens, you have to fire (any weapon, including LG) to fix it. Little annoying bug on there if it happens by accident.

I've also noticed a little FPS hiccup every time I shot any weapon (it goes from 125, to 11X real quick then back to 125.

This version appears to have fixed the first glitch you mentioned:

http://pastebin.com/QBPezVPW

The FPS hiccup will require some investigation. It is difficult because I do not get any fps hiccup and so I cannot run tests.

I can however imagine where the lag might be. As a test I tried replacing as many aliases as I could with sets as I believe they have faster performance, but there's some sort of lockdown on mixing the two.

If you vstr a set that aliases something, that alias will accept one, and only one command. It will not accept any variables. So if you do:

set realias "alias +jack vstr happy"

vstr realias

+jack becomes "vstr"

Maybe sync did this on purpose to prevent some sort of scripting exploit, or maybe it's just a bug. I have no idea. Point is that this produces limitations on what I can do to address performance.

I'll probably come up with some other ideas sometime, just maybe not this morning :-)

yep for me it works now. I know a couple of other players who tested it too, we all get the fps slowdown too... its real fast only when you click. it also happens when changin waepons...

i have tried several times script like this, i like it for a while then i hate it, makes your aim very inconsestant... still thanks anyway

yep for me it works now. I know a couple of other players who tested it too, we all get the fps slowdown too... its real fast only when you click. it also happens when changin waepons...

I believe you! Might be hard to fix though as there isn't much breathing room in terms of what can be changed and have it still work.

i have tried several times script like this, i like it for a while then i hate it, makes your aim very inconsestant... still thanks anyway

Well I don't advocate the use of such scripts or use them myself :-)

I suppose it's nice to have the option of one, and it is interesting to see what can and cannot be done with the console script.

I did the viewpos thing

I got with fov 105: 0 to -120
with fov 95: 0 to -68

again the sens i got them from here:
http://kyto.dez.fi/ql/zoomsens/index.php

I don't understand what you mean by "the sens i got them from here"

I'm honestly not even sure what that page is for.

Well, lets see. I use for example fov 100 for everything, then for rail I use fov 95. So on that page you set the sens you use for everything on "sens" Then on FOV you use the default FOV (100) then on "zoomfov" you use the lower fov you want to use (95)

The number you get is the sensitivity that theorically gives you the exact same feeling but with the lower fov (95)

That page basically is doing the zoomfov algorithm automatically (This one)

http://www.wolframalpha.com/input/?i=arctan%5B+0.75+*+tan%5B60+degrees+%2F2%5D+%5D+%2F+arctan%5B+0.75+*+tan%5B120+degrees+%2F2

but you said if it worked I should rotate exactly the same which is not the case. So wtf is going on?

Ahh ok, I misunderstood you. My apologies.

Your original question:

Is it normal that I rotate less angles with the higher fov (105) compared to the lower fov (95) ??

Confused me since I thought you were only changing the fov, but you were also changing the sensitivity.

Changes to sensitivity will result in less degrees per distance on the pad regardless of fov.

The lower your fov the faster your sensitivity feels, that's why +zoom automatically lowers your sensitivity when it zooms in to compensate.

So it's normal that i rotate less degrees?

Lower sens = less degrees of rotation for a given mouse motion.

the second method doesnt work at all

u can try it urself

when u are zooming rail, lets say zoomfov 70 , then swith to another weapon , like RL , the FOV doesnt change at all ,remains 70 !
no matter what u do unless u press ur rail bind again which is V like u posted above

cg_fov "105"
cg_zoomfov "70"

bind v "vstr rga"

set rga "weapon 7 ; -zoom ; bind v vstr rgb"

set rgb "weapon 7 ; +zoom ; bind v vstr rga"

bind w "weapon 5 ; -zoom"
bind a "weapon 3 ; -zoom"

I tested this just now and it worked.

There was a typo in that I wrote "bind v vstr rgg" instead of "bind v vstr rga". My apologies for that. That would not produce the symptoms you're describing though.

Another method:

cg_fov "105"

cg_zoomFov "70"

set selectRail "weapon 7 ; bind v vstr railzoom"

set railzoom "+zoom ; bind v vstr rail_unzoom"

set rail_unzoom "-zoom ; bind v vstr railzoom"

set bind_SelectRail "-zoom ; bind v vstr selectRail"

bind [key] "weapon x ; vstr bind_SelectRail"
bind [key] "weapon y ; vstr bind_SelectRail"
bind [key] "weapon 7 ; bind v vstr railzoom"

Also tested and worked.

if i remember 'DC.Storm' had this in his 2007-ish config.

to keep the same perception of aiming with different fov's do:

sens / highfov * lowfov = sens for lowfov

example: 4 / 105 * 70 = 2.6666

so who is right? everyone comes with a new algorithm once in a while

actually it was done like above already in Q3, when +zoom with cg_zoomfov was messed up resulting in alot of skipped pixels while zooming in.

Q3 did this:

arctan( tan(zoomfov * PI/360) * height/width ) * (360/PI) / 75

Which can be used in QL by setting:

cg_zoomSensitivity "0"

The better algorithm that is used in QL is:

arctan[ 0.75 * tan[cg_zoomfov°/2] ] / arctan[ 0.75 * tan[cg_fov°/2] ]

do u have website i can use to actually calculate this?

http://kyto.dez.fi/ql/zoomsens/index.php

Sure:

QL algorithm:

Link 1

The example is for zoomfov 60 degrees, and fov 100 degrees.

k is the factor that sensitivity and mouseaccel are multiplied by.

Q3 Algorithm:

Link 2

The example is for 800x600 resolution, cg_zoomfov 60.

After hitting enter, scroll down to solution and click "approximate form". That will give you the factor it scales the sens by.

For example, sensitivity 3 with the above calculation, scales down to 1.873058 per cl_showmouseRate 1.

Multiplying 3 by the answer it spits out, 0.62435 makes 1.87305. I could have asked it for more digits and probably gotten the exact result.

Alternatively you could just ask it to multiply it directly, like this:

Link 3

Then you'd get a long but very precise answer.

EDIT: Esr doesn't like long link files. So instead see this pastebin for the links:

http://pastebin.com/uZAqz5zT

Thunda's wrong, stop being retarded for a change and use something based on either zoom algorithms.

due to fishbowl effect it's not exactly fov:zoomfov ratio, that's why you got all those zoom formulas which give you proper 'pixel speed' = if you move mouse with the same physical speed while zoomed and non-zoomed it's gonna pass the same amount of pixels/second in the middle of the screen(yes, pixels, not the same angle) which is what 'the same feel' can be described as.

example:

you aim at an enemy 50 meter away with fov 100 and sens 4.
the enemy moves 5 meters to the left, which requires you to move the mouse 5cm to the left aswell to track him.

you aim at an enemy 100 meter away with fov 50 and sens 2.
the enemy moves 5 meters to the left, which requires you to move the mouse 5cm to the left aswell to track him.

My post for a script that does something like this:

http://www.esreality.com/post/1950460/elegant-zoom-script/

Although this is my current one (I only use it for rail)

cg_fov 100
cg_zoomfov 60
cg_zoomtoggle 1

set fovin "+zoom"
set fovout "-zoom"

set railzoom "vstr railout"
set railin "vstr fovin ; set railzoom vstr railout"
set railout "vstr fovout ; set railzoom vstr railin"
set railn "vstr fovout ; set railzoom vstr railout"

bind KP_HOME "vstr w6 ; vstr railn"
bind KP_PGUP "vstr w5 ; vstr railn"
bind KP_END "vstr w1 ; vstr railn"
bind KP_DOWNARROW "vstr w3 ; vstr railn"
bind KP_PGDN "vstr w8 ; vstr railn"
bind KP_DEL "vstr w4 ; vstr railn"
bind KP_PLUS "vstr w2 ; vstr railn"
bind MOUSE2 "vstr w7 ; vstr railzoom"