Toggle Sensitivity Script :3

[Tsweezy]

So....when I played this game a long time ago I was actually good at making my own CFG and making scripts and stuff

Seeing how 4-5 years have passed, I'm terrible at it and I'm looking for some help making a script that does something pretty basic...

 

Not shooting mouse sensitivity = 2.5

While shooting mouse sensitivity = 0.5

 

Thanks for any help ( I haven't browsed any of the forums I'm sure it may already be on the forums but I'm lazy and didn't feel like digging through pages on top of pages; so if this same thing is posted 2 topics below me don't blame me )

[stabak]

Like that?

 

bind MOUSE1 "+vstr shoot_a shoot_b"

set shoot_a "+attack; sensitivity 0,5"

set shoot_b "-attack; sensitivity 2,5"

 

Should be work but i dont know its 2,5 or 2.5

[SunLight]

it's 2.5, not 2,5

 

anyway, if you have a different sens when you shoot it is bad for your accuracy (imho)

but since I'm low someone could say that I fail because I use only 1 sens, so it's up to you. (well, low with 40+ accuracy )

[stabak]

it's 2.5, not 2,5

 

anyway, if you have a different sens when you shoot it is bad for your accuracy (imho)

but since I'm low someone could say that I fail because I use only 1 sens, so it's up to you. (well, low with 40+ accuracy )

 

 

 

i also think so, that´s why i toggle it only while crouching

 

But i can´t play with a sens like 2.5 or 0.5 for me its impossible

 

you are sure about that ?

[sinA* <3 Padme*Amidala]

I have a toggle like this somewhere, i will find it

[PHANTASM]

I don't use it myself, but this should be exactly what you describe:

 

//attack bind

bind MOUSE1 "+vstr atk1 atk2"

set atk1 "+attack; sensitivity 0.5"

set atk2 "-attack; sensitivity 2.5"

[Pepperonipizza]

But i can´t play with a sens like 2.5 or 0.5 for me its impossible

 

The effect of the sensitivity variable depends a lot on your mouse and what your mouse settings are outside of ET. I play with 7+ sens, but this would probably about the same as a sens of 2.5 with another player.

[stabak]

The effect of the sensitivity variable depends a lot on your mouse and what your mouse settings are outside of ET. I play with 7+ sens, but this would probably about the same as a sens of 2.5 with another player.

 

of course,

some mouses can toggle the sensitive with their own mouse drivers

 

I play with a senstitive from 7 (only while crouching) to 10 (logitech MX 518)

But I'm still working on fine-tuning

[SunLight]

of course,

some mouses can toggle the sensitive with their own mouse drivers  

 

I play with a senstitive from 7 (only while crouching) to 10 (logitech MX 518)

But I'm still working on fine-tuning  

you should keep your os mouse sens to the middle notch, otherwise you will lower your mouse dpi and reduce your overall precision...

 

 

 

with sensitivity=10 you can move 10*m_yaw = 10*0.022 = 0.22 degrees every mouse pixel.

 

Now at, for example,  1280x1024 (let alone on widescreen monitors) and 100 fov you have 1280/100 = 12.8 pixel for 1 degree. So 1 pixel is 0.08 degrees only.

 

In this example, with your huge sens you move 12.8*0.22 = 2.8 pixels every mouse pixel! So you can't even aim at every single pixel, you move 3 pixels at a time!

 

I know that aiming in et is so random that rarely you will need 1 pixel precision, but not being able to aim at every pixel is bad imho. Your sens shouldn't be higher than 2.5 if you want to be able to aim at every single pixel on your screen, so set your windows sens higher (possibly middle notch) and lower your et sens, it will feel much smoother.

[stabak]

you should keep your os mouse sens to the middle notch, otherwise you will lower your mouse dpi and reduce your overall precision...

 

 

 

with sensitivity=10 you can move 10*m_yaw = 10*0.022 = 0.22 degrees every mouse pixel.

 

Now at, for example,  1280x1024 (let alone on widescreen monitors) and 100 fov you have 1280/100 = 12.8 pixel for 1 degree. So 1 pixel is 0.08 degrees only.

 

In this example, with your huge sens you move 12.8*0.22 = 2.8 pixels every mouse pixel! So you can't even aim at every single pixel, you move 3 pixels at a time!

 

I know that aiming in et is so random that rarely you will need 1 pixel precision, but not being able to aim at every pixel is bad imho. Your sens shouldn't be higher than 2.5 if you want to be able to aim at every single pixel on your screen, so set your windows sens higher (possibly middle notch) and lower your et sens, it will feel much smoother.

 

 

 

Thats new for me :?

 

I´ll try it

[BossHK]

you should keep your os mouse sens to the middle notch, otherwise you will lower your mouse dpi and reduce your overall precision...

 

 

 

with sensitivity=10 you can move 10*m_yaw = 10*0.022 = 0.22 degrees every mouse pixel.

 

Now at, for example,  1280x1024 (let alone on widescreen monitors) and 100 fov you have 1280/100 = 12.8 pixel for 1 degree. So 1 pixel is 0.08 degrees only.

 

In this example, with your huge sens you move 12.8*0.22 = 2.8 pixels every mouse pixel! So you can't even aim at every single pixel, you move 3 pixels at a time!

 

I know that aiming in et is so random that rarely you will need 1 pixel precision, but not being able to aim at every pixel is bad imho. Your sens shouldn't be higher than 2.5 if you want to be able to aim at every single pixel on your screen, so set your windows sens higher (possibly middle notch) and lower your et sens, it will feel much smoother.

 

Now that formula doesn't make any sense? o_O

 

Omg, it allways (at least 50%) leads to mouse/sens conversation. Well, lets post most important things when messing around with mouse:

3.0 Mouse

---------

 

I could write any amount about this but I try to get to with so little writing as possible.

First of all just think what type of player you are: highsens-, midsens- or lowsens player. Rought values in 360 degree turning could be:

 

Highsens: under 10cm (~4")

Midsens: over 10cm (~4") but under 40cm (~16")

Lowsens: over 40cm (~16")

 

(1" = 2,54cm)

 

So it is sensible to tell sensitivity in the form of cm/360. You can find out what type of player you are when you measure how much you move your mouse that in-game characher turns 360 degree. Make sure you measure it right. Do that measure also several times.

 

That was made that you have some direction what mouse will be best for you. I mean optical mouse or laser mouse. Basically if you are lowsens gamer then optical mouse is your choise(because laser technology can't handle yet fast movements making skipping and negative acceleration). But if you are highsens gamer then laser is maybe better for you nowdays. Though for example Deathadder and MX518 are still very good also for highsens gamer.

So choosing the mouse:

 

-Cord mouse (never wireless/cordless for gaming!)

-Technical information about mouse (especially important for lowsens gamers!)

-Ergonomic and design of mouse (how it fit to your hand)

-Lowsens/highsens gamer (optical or laser)

 

When mouse has chosen you can start optimize it. I go shortly through the most vital things:

 

 

3.1 Disabling mouse acceleration. First disable all acceleration from mouse drivers(if you have so called gaming mouse). Windows(at least XP) still have a little acceleration and disabling it needs a little operation. You can either download mouse accel fix.reg and use it or disable acceleration manually:

 

1. Press Start

2. Select Run

3. Type regedit and hit enter

4. Open the tree HKEY_CURRENT_USER-->select control panel-->mouse

5. Right clicking, modify the SmoothMouseXCurve and SmoothMouseYCurve hexidecimal values to the following:

 

(Remember to take backup copies from original values if you want later restore them)

 

SmoothMouseXCurve:

00,00,00,00,00,00,00,00

00,a0,00,00,00,00,00,00

00,40,01,00,00,00,00,00

00,80,02,00,00,00,00,00

00,00,05,00,00,00,00,00

 

SmoothMouseYCurve:

00,00,00,00,00,00,00,00

66,a6,02,00,00,00,00,00

cd,4c,05,00,00,00,00,00

a0,99,0a,00,00,00,00,00

38,33,15,00,00,00,00,00

 

6. Press OK after setting both(X and Y) values and you are done.

 

 

3.2 Speed of pointer. In Start-->Settings-->Control Panel-->Mouse-->Settings of Pointer set speed to half way(very middle notch) aka 6/11. Do NOT cross Enhance Pointer Precision -box but leave it empty.

 

 

3.3 Overclocking the usb port. Windows has default 125hz(8ms) usb port but with overclocking it even up to 1000hz(1ms) you can get faster mouse reaction time and smoother mouse movement. At same time you reduce negative acceleration. Some mouses have ability to change this straight from drivers. If not, same thing is possible to do with some tool.

One tool to that is hidusbf which you can get here(Win XP): http://sweetlow.at.tut.by/download/hidusbf.zip.

For Vista&Win7 check this website: http://www.ngohq.com/news/15043-how-to-increase-usb-sample-rate-in-windows-vista-7-a.html

You can see the polling rate of usb port for example with mouserate checker -program(Download it from that previous webpage, its called mouserate.exe). Target is to get as stable rate as possible(aka as high average rate as possible).

NOTICE! This operation could make problems for example with printer but I didn't had any problems.

NOTICE! It's useless to try to get high polling rate with basic mouses.

 

 

3.4 DPI(Dotch per inch, more closely Counts per inch). How much is enought? Is more always better?

 

(NOTICE! If you have basic mouse, probably you are not allowed to change your mouse's DPI. Surely you can still check more closely from internet how it is at your mouse. Maybe with some drivers DPI changing would be possible.)

 

You can figure out necessary amount of DPI as follows:

 

Figure out what resolution you are playing with. Pick up the horizontal amount of pixels aka first value, for example I'm playing with 1280x1024 so my value is 1280. Multiply that value by four(4). By four, because screen shows 90 degree at time.

 

1280 x 4 = 5120

 

After that divide the total number of pixels by the total distance (in inches,) which is needed to turn your characher in-game 360 degree(remember, you have figured it out already). I need 50cm = ~19,685". That's how you get a rough idea of how much DPI is useful.

 

5120 / 19,685 = 260,0965... So about 260 DPI is useful for me.

 

Using more DPI than you just calculated for yourself doesn't offer any benefit but mouse movement could feel smoother. Though on older mouses which uses 8-bit dimension, increasing DPI value increase crucially possibility to get negative acceleration. In turn using less DPI than you just calculated for yourself hinders your aiming because mouse will skip pixels.

 

 

Yesss, new textwall created. Succes, its time to go to sleep

 

P.S. Ops I forgot to post it, very, very nice website about mouses, basically it calculates everything for you(+ it tells some stories/information too, just check it out, it will be the best website you will ever visit when you need information about mouses+gaming combination), you just need to fill in 8 different fields. Here it is: http://lawliet.wippiespace.com/mouse.htm

(That "windows sensitivity multiplier" -field is tricky one, there is list of those multipliers under those 8 fields where you can check your own multiplier. So, for example, I have my winsens 6/11, so my multiplier is 1(so not 6 as I first though )), so I put 1 to that field)

 

P.P.S. So now people when you are talking about "what is my sensitivity, omg its 7, thats so high, you use 0.5 omgomg", you can forget it and just go to that website and see your "real sensitivity" (cm or inches / 360 degree(1 full turn)) Hf.

Edited November 8, 2010 by BossHK

[SunLight]

Now that formula doesn't make any sense? o_O

[cut]

great informational post

 

now, I think I missed one (big) detail in my formula, that website you posted says:

The projection of the 3D world onto the 2D plane of your screen means the pixels located near the crosshair represent much larger angles than those pixels located at the edges of your screen

I didn't think about it, in my calculations I just divided my screen resolution by my cg_fov, not taking into account that not every pixel is equivalent to the same angle in degrees...

 

the fact that, in q3 engine, the minimum movement (in degrees) you can make is m_yaw * sens is still true. (I am assuming that cl_mouseaccel = 0)

 

 

Anyway using a low sens in your desktop and a high one in game is bad, so my post (even though the formula is not valid) still made some sense...

(Of course we are talking about people who don't use any direct input/raw input/ linux in_dgamouse) because in that case their desktop sens is not taken into account)

 

So, I made a mistake, thanks for pointing it out...

[BossHK]

great informational post

 

now, I think I missed one (big) detail in my formula, that website you posted says:

 

I didn't think about it, in my calculations I just divided my screen resolution by my cg_fov, not taking into account that not every pixel is equivalent to the same angle in degrees...

 

the fact that, in q3 engine, the minimum movement (in degrees) you can make is m_yaw * sens is still true. (I am assuming that cl_mouseaccel = 0)

 

 

Anyway using a low sens in your desktop and a high one in game is bad, so my post (even though the formula is not valid) still made some sense...

(Of course we are talking about people who don't use any direct input/raw input/ linux in_dgamouse) because in that case their desktop sens is not taken into account)

 

So, I made a mistake, thanks for pointing it out...

 

Lol I didn't mean it to be any attack/insult toward you, just mentioned that it didn't made any sense, lets see(with my own values);

 

with sensitivity=4 you can move 4*m_yaw = 4*0.022 = 0.088 degrees every mouse pixel.

Now at,  1280x1024 and 115 fov you have 1280/115 = 11.13 pixel for 1 degree. So 1 pixel is 0.09 degrees only.

In this example, with your sens you move 11.13*0.22 =  2.4 pixels every mouse pixel! So you can't even aim at every single pixel, you move ~2.5 pixels at a time!

 

Hmm, so I'm moving ~2,5 pixels / 1 "mouse pixel", and I don't do that. But with this "formula" every player is skipping pixels no matter what they do. Untill I have missed something really badly...

[Tsweezy]

I have a bad habit of sliding too far past the target since I've been stuck playing CoD for so long, I'm used to just look, shoot, move on; still getting used to, headshot->headshot->ohlookhehas15packsonhiscorneralready->headshot->headshot->headshot-> dead

 

Anyways, thanks for your help given the I play I'm rarely face to face with someone; so this helps a lot, they tend to move at the same speed of 0.5 or 0.8 sens. so it's pretty much just press and hold and wait

[SunLight]

Lol I didn't mean it to be any attack/insult toward you, just mentioned that it didn't made any sense, lets see(with my own values);

and in fact I didn't read it as such, so np at all    

 

 In this example, with your sens you move 11.13*0.22 =  2.4 pixels every mouse pixel! So you can't even aim at every single pixel, you move ~2.5 pixels at a time!

 

0.22 was his value (sens 10 * 0.022), for you it would be 0.088 (sens * 0.022), so you can move 0.98 pixels, which is ok.

 

But this formula is just a hint for the average case, because just doing res/fov is wrong. Pixels close to your xhair have a bigger angle, so in the real case you have a higher precision.

 

 

'bad' formula for the angle of a pixel:

115(fov)/1280(res) = 0.0898 degrees

 

'good' formula should be (but I am a noob in maths so beware...)

how many degrees is a pixel close to your xhair:

fov = 115

tan(fov/2) = 1.570

res/2 = 1280/2 = 640


640 / 1.570 = 407.7

atan(1/407.7) = 0.00245, which in degrees is: 0.14

 

now that means this pixel is bigger (0.14 degrees, and not 0.0898), then:

 

you move (sens*m_yaw) = 0.088 degrees, 1 pixel (in the middle of your screen) is 0.14, so you can actually move 0.6 pixels on the screen per mouse count.