Whatever fov you're using, the sens/accel doesn't change at all.
Your perception is different though, with lower fovs the world seems to rotate faster, hence why most people recalculate their sens/accel or use zoomfov scripts to get the same " rotation feel "

(basefov/newfov) * sens (basefov/newfov) *accel
or cg_fov your base fov, cg_zoomfov your desired fov ( say your basefov is 95, then you'd use zoomfov 95 for your hitcans and 110 for your rl or whatever ) and play +zoomed

Or if you were talking about a standard +zoom, the sens/accel get lowered but the feeling remains.

this, sens stays the same.

If you want the same feeling at different fovs, you need to do some calculation. It's not just simply fov1/fov2=sen1/sen2.

check this post, the section about the fovs and zooms.

http://www.quakelive.com/forum/showthread.php...Live-Guide

Do you mean this one:

Zoom_sensitivity=sensitivity * tan((zoomfov/2) * (PI/180)) / tan((fov/2) *(PI/180))

Example:

sensitivity 4
cg_fov 100
Desired: fov 50

4 * tan(50/2 * pi/180) / tan(100/2 * pi/180)=1.5651

The one i've been using was this one:

// Ratio: tan(45/2) / tan(90/2) = 0.414213562
// Zoomsens: 0,414213562 x 5 = 2,071067812

I have no idea what that means, but that's on my cfg. I don't remember.

Also what do you do with your acceleration value, you leave the same value or apply the formula to accel aswell?

well, some ppl just calculate the ratio and change their m_yaw/pitch, so no bothering with sen/accel :)

k but considering I want it as precise as possible and use this formula:

4 * tan(50/2 * pi/180) / tan(100/2 * pi/180)=1.5651

Should I apply it to my accel value aswell?

Also: Up to how many decimals does QL detect? I say that cos the windows calculator gives me a shitload of decimals.

afaik it's 5 decimals.

ffs just zoomfov your way through if you want to use this method.

But IrrSolicitude said that wouldn't be enough.

It is. Do you think fox would have played for years ( recently switched to the +zoomed ) with the basefov/newfov method and noctis with the +zoomed one if it didn't feel right?
Sure, flicks 180 will feel slightly wrong at first but you'll soon get used to it ( and you're not really supposed to flick 720 with a railgun )

The zoomfov one is boring to script, just steal from noctis' cfg.

'the same feeling' i meant is that moving the same 'distance' on screen with the same mouse movment at different fovs.

Ofc keeping the same sen/acc gives the same cm/360 at different fovs, but at different fovs the size of things on screen looks different. So if you want to compensate this difference you need to change sen/acc or m_yaw/pitch. Using +zoom, the QL syestem will automatically do the sen/acc change (you can try the difference with +zoom and acutally fov change using same sen/acc and you will feel the difference.)

If you don't want this then single sen/acc is absolutely fine. :)

Okay im wanting to use the zoomfov thing since apparently Rapha uses it too.

Anywhere where I can learn how it works/steal it copy-paste style?

Errr... I don't think rapha is using different fovs with different weapons.
All those messy fov/zoomfov scripts in his config are not actually in use.

Are you blind or what.


noctis' cfg

His cfg is a mess, so I can't copypaste.

It's not, it's the cleanest zoomfov script you could steal. Just use your fucking brain for a second.

I like to use +zoom by pressing spacebar, so it gets zoomed while you are pressing spacebar, if you stop pressing spacebar it goes back to normal. I find the "you press a button it gets permanently zoomed till you press it again-method" stupid in such a fast game. Can I still zoom while you press spacebar with that script? (noctis's)

If you cared enough you would already have :
a. tried his cfg
b. read and understood what it does.

I tried his cfg, and the way he zooms is not the way I want it to zoom (he presses mouse 1 and it stays zoomed, and that sucks)

you're fucking retarded.

nope.

you are french lol

you're fucking retarded

I'm french lol

>I'm french lol
You can't call someone retarded when you are french. It's like you are always more retarded by default.

cg_zoomtoggle 0 will zoom out when you let go of the button.

But he is not using +zoom to zoom, he is using a nearer cg_zoomfov value cos hes using the zoomfov script.

I dunno if it's changed for Quake Live, probably not, but no matter what I changed my FOV to my cm/360 always stayed the same. Providing I had the same in game sensitivity setting of course.

edit: Dunno about zoom and I didn't use accel.

Afaik:

If you use cg_fov to change your field of view, the sensitivity stays the same. And I strongly recommend you use one single sens and accel with different fov's, instead of what, for example, #2 wrote. Otherwise you're risking being inconsistent with your aim.

If you use +zoom and different cg_zoomfov values, your sensitivity and acceleration do in fact change with your field of view. Fox used this kind of setting, don't know if he still does.

i dont want "the same sens/accel", i want the same "feeling" of the same sens/accel on all fovs, if you get what I mean.

then maybe you should use
+zoom for every fov change (weapon wise bound)
cg_zoomsensitivity (or w/e its called)

How do I do that?

bind v "weapon 1;cg_zoomfov 60;-zoom"

bind 1 "weapon 2;cg_zoomfov 60;-zoom"

bind 2 "weapon 2;cg_zoomfov 60; -zoom"

bind t "weapon 7;cg_zoomfov 95; +zoom"


ok


it's not so good i think

- zoom/-zoom might not even work this way
- just calculating the according sens for each zoomfov/fov might be cleaner
- I wouldn't worry about to choose 5 or 7 decimals anyway
- accel: you def. have to try this yourself :/
- rail aim works very different to lets say lg anyway...

|
|
v

bind v "weapon 1;cg_zoomfov 60; cg_fov 105; sens x"

bind 1 "weapon 2;cg_zoomfov 60; cg_fov 105; sens x"

bind 2 "weapon 2;cg_zoomfov 60; cg_fov 105; sens x"

bind t "weapon 7;cg_zoomfov 60; cg_fov 95; sens Y"


zoomfov should feel the same via cg_zoomfov 1


SENS
Y < x
there's that tan(asldfkj) formula further up in this thread

What is that?

I just want the same sens feeling when I change weapon, I don't ever use zoom.

I dont get it.

What he's telling you is wrong. Check out fox's config (www.fojji.se). It's like this:
bind x "weapon 1; cg_zoomfov 90"
bind y "weapon 2; cg_zoomfov 95"
bind z "weapon 3; cg_zoomfov 100"

The point is to play with a fixed fov (only zoomfovs are different), otherwise the sensitivity/accel scaling gets all messed up.

What's important is that every time you launch the game, you have to type +zoom in the console, so that you play zoomed all the time. You should never play unzoomed, otherwise you won't be able to change the fields of view on your weapons.

But, I repeat once again - this kind of play is for very advanced players who know perfectly what they're doing. I don't recommend these kinds of settings for anyone, since it's virtually a different sensitivity/acceleration for every single weapon that the zoomfov attached is different. You probably will not get a feeling that you want, you'll just make your aim inconsistent.

If you've read it and still want to do it, that's the correct way to achieve your aim. Pun also intended ;)

noctis.

+zoomed, and he can still zoom ( dynamic zoomfov )

I use the same fov for every single weapon, I just use a closer fov for rail.

launch the game, you have to type +zoom in the console

nice1

Wasn't 100% sure if it's the best way to do it, but that's how it worked with q3 (although there was a cvar for auto-entering +zoom or some other command every time you join the server) and with some early versions of QL. Also, I am certain that this way of approaching the problem works, since I just checked it.

If there's a better way, though, you're free to elaborate in order to help fromage, instead of just behaving like a dick.

i think noctis has the +zoom bound to every weapon bind
alias n_conf2 "weapon 2 ; cg_drawcrosshair 2; cg_crosshairSize 32; cg_drawgun 0; cg_hitBeep 2; cg_gunZ 0 ;+zoom" //mg




I'm not behaving like a dick on purpose

Then why noctis has this on his cfg?

seta cg_zoomSensitivity "0"

because he wannts to have a consistent cm/360 even in zoom

wait, I'll check his latest config

No, you're wrong again. The cvar for enabling or disabling the scaling is is cg_zoomScaling.

cg_zoomSensitivity is:
The value of this cvar is multiplied to our current zoom sensitivity, allowing the user to increase or decrease their sensitivity while zoomed. A value of 0 will revert the zoomSensitivity code to the Q3 legacy code that was previously available in QuakeLive.

Next time, read this.

oh thank you
I didn't check back when I wrote zoomsens, thats why i put the (?) in my posts


!!Zoomscaling!!


edit: apparently not
see lorfa

Zoomscaling has nothing to do with the sensitivity. It has to do with whether or not it instantly switches to the zoomfov, or "zooms" to it.

Right, my bad.

That doesn't make any sens. Pun intended.

Fuck your puns bro, makes total sens and even accel.

I just use fov 100 for every weapon, but i got 2 binds for rail 1 with fov 100 and one with fov 50 and halved sens, easier that way :)

k, got fox's cfg to check the zoom script thing, can't understand shit.

I use this:

set fovin "cg_fov 60 ; m_pitch 0.0166 ; m_yaw 0.0147"
set fovout "cg_fov 90 ; m_pitch 0.025 ; m_yaw 0.022"

Works fine for me.

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

When zooming your sensitivity and cl_mouseaccel values are multiplied by k. (formula applies to cg_zoomsensitivity is 1 which is the default. )

If you simply change the cg_fov, your sensitivity/mouseaccel will not be scaled with it, and it will feel as if your sensitivity is increasing the lower you adjust the fov.

This is because your field of view is decreasing in size, while the distance your mouse needs to move to produce a given rotation remains the same.

In your case you could calculate things manually for your two different fovs, using the higher fov as the base. So we would plug in 95 for the 'zoomfov' part, and 105 for the fov part.

I get k = 0.8862

4 * 0.8862 = 3.5448
0.2 * 0.8862 = 0.17724

So a config would look something like this:

bind [key] "weapon [others] ; cg_fov 105 ; sensitivity 4 ; cl_mouseaccel 0.2" // Other Weapons than Rail Gun

bind [key] "weapon 7 ; cg_fov 95 ; sensitivity 3.5448 ; cl_mouseaccel 0.17724" // Rail Gun

Lol, i already have seen like 4 formulas to do that. What about the

4 * tan(50/2 * pi/180) / tan(100/2 * pi/180)=1.5651

one?

Use lorfa's, this one is correct.
that 0.75 is the aspect ration (4:3), quake is based on this (doesn't matter you are using 16:10 or whatever).

lorfa's forumula is missing changing degrees to radians part (pi/180), so - imho - it should be:
k = arctan[0,75*tan((cg_zoomfov/2)*(pi/180))]/arctan[0,75*tan((cg_fov/2)*(pi/180))]

It's a good point, but I don't think it works as you stated.

Just remember to specify degrees, after all fov is in degrees.

If zoomfov is 95 input 95° (alt+0176) or just write out 95 degrees, a bunch of programs recognize this.

Here's an example that you can paste into www.wolframalpha.com

arctan[ 0.75 * tan( 95 degrees / 2 ) ] / arctan[ 0.75 * tan( 105 degrees / 2 ) ]

Yields 0.8862

Formula is from injx.

excel/openoffice calc aren't that smart. but it's all clear now :)

really? so much bullshit cos one guy wants to f33l good when zooming? really? really?? REALLLLYYYYYYYY?!?!?!?!

ITS A FUCKIN COMPUTER GAME

I think you missed the point.