Upvote Upvoted 0 Downvote Downvoted
fiddling with sensitivity
posted in Customization
1
#1
0 Frags +

how do i give each class and weapon slot it's own sens?
i.e.
sniper:1.3 primary/2 secondary/2 melee
soldier:2 primary/1.3 secondary/2 melee

how do i give each class and weapon slot it's own sens?
i.e.
sniper:1.3 primary/2 secondary/2 melee
soldier:2 primary/1.3 secondary/2 melee
2
#2
45 Frags +

dont

dont
3
#3
1 Frags +

I did something like this:

bind "MOUSE3" "slot3; sensitivity 2"
bind "MWHEELUP" "slot1; sensitivity 2"
bind "MWHEELDOWN" "slot2; sensitivity 1.3"
You can also add switching viewmodel on/off.

There're more complicated binds that also change sens when using numbers and Q, but I'm fine with mine. Not hard to get used to.

I did something like this:

bind "MOUSE3" "slot3; sensitivity 2"
bind "MWHEELUP" "slot1; sensitivity 2"
bind "MWHEELDOWN" "slot2; sensitivity 1.3"
You can also add switching viewmodel on/off.

There're more complicated binds that also change sens when using numbers and Q, but I'm fine with mine. Not hard to get used to.
4
#4
7 Frags +

That would end really badly. I already discourage class based sensitivities. This would be even worse for muscle memory.

That would end really badly. I already discourage class based sensitivities. This would be even worse for muscle memory.
5
#5
0 Frags +

bind 1 "slot1; sensitivity 1.3"
bind 2 "slot2; sensitivity 2"
bind 3 "slot3; sensitivity 2"

would not recommend it, but each to their own i guess.

edit: ninja'd

bind 1 "slot1; sensitivity 1.3"
bind 2 "slot2; sensitivity 2"
bind 3 "slot3; sensitivity 2"

would not recommend it, but each to their own i guess.

[i]edit: ninja'd[/i]
6
#6
1 Frags +

I along with many others would recommend against constantly switching sensitivities because you won't be very consistent, but if you want to do that then more power to you

different sensitivity values to into each specific class cfg file. Examples below. Don't mind the exec InGameSettings part since that's a thing that I have that's unique to my specific configs

Scout cfg:

exec InGameSettings

sensitivity 1.12

//crosshair settings
cl_Crosshair_file crosshair7
cl_Crosshair_Scale 20

alias primary "slot1; r_drawviewmodel 1"
alias melee "slot3;r_drawviewmodel 1;"

bind "1" "primary"
bind "2" "secondary"
bind "3" "melee"
bind "f" "melee"
bind "MWHEELUP" "primary"
bind "MWHEELDOWN" "slot2"

Soldier:

exec InGameSettings

//crosshair settings
cl_crosshair_file crosshair4
cl_Crosshair_scale 45
crosshair 1
tf_use_min_viewmodels 0

alias primary "slot1;r_drawviewmodel 0"
alias secondary "slot2;r_drawviewmodel 1"
alias melee "slot3;r_drawviewmodel 1;"

bind "1" "primary"
bind "2" "secondary"
bind "3" "melee"
bind "f" "melee" //+attack3 when needed
bind "MWHEELUP" "primary"
bind "MWHEELDOWN" "secondary"
bind "MOUSE2" "+duck"

basically you'd need to create aliases for your weapons and within those weapon aliases assign what settings you want, including sensitivity and many other things.

Still I along with many others would recommend picking one sensitivity and sticking to it since finding the right sensitivity is all about building up the muscle memory to be able to perform well with it as much as possible.

edit: I spent all this time typing this out to get ninjad smh

I along with many others would recommend against constantly switching sensitivities because you won't be very consistent, but if you want to do that then more power to you

different sensitivity values to into each specific class cfg file. Examples below. Don't mind the exec InGameSettings part since that's a thing that I have that's unique to my specific configs

Scout cfg:
[code]exec InGameSettings

sensitivity 1.12

//crosshair settings
cl_Crosshair_file crosshair7
cl_Crosshair_Scale 20

alias primary "slot1; r_drawviewmodel 1"
alias melee "slot3;r_drawviewmodel 1;"

bind "1" "primary"
bind "2" "secondary"
bind "3" "melee"
bind "f" "melee"
bind "MWHEELUP" "primary"
bind "MWHEELDOWN" "slot2"[/code]

Soldier:
[code]exec InGameSettings

//crosshair settings
cl_crosshair_file crosshair4
cl_Crosshair_scale 45
crosshair 1
tf_use_min_viewmodels 0

alias primary "slot1;r_drawviewmodel 0"
alias secondary "slot2;r_drawviewmodel 1"
alias melee "slot3;r_drawviewmodel 1;"


bind "1" "primary"
bind "2" "secondary"
bind "3" "melee"
bind "f" "melee" //+attack3 when needed
bind "MWHEELUP" "primary"
bind "MWHEELDOWN" "secondary"
bind "MOUSE2" "+duck"[/code]

basically you'd need to create aliases for your weapons and within those weapon aliases assign what settings you want, including sensitivity and many other things.

Still I along with many others would recommend picking one sensitivity and sticking to it since finding the right sensitivity is all about building up the muscle memory to be able to perform well with it as much as possible.

edit: I spent all this time typing this out to get ninjad smh
7
#7
0 Frags +
CrymadontTsarbucksThat would end really badly. I already discourage class based sensitivities. This would be even worse for muscle memory.NoobKbind 1 "slot1; sensitivity 1.3"
bind 2 "slot2; sensitivity 2"
bind 3 "slot3; sensitivity 2"

would not recommend it, but each to their own i guess.

edit: ninja'd

i know it's bad but playing hitscan with anything higher than 1.3-1.5 is a no bueno for me and being somewhat effective as soldier or demo with a sens that low is kinda hard

[quote=Cryma]dont[/quote]
[quote=Tsarbucks]That would end really badly. I already discourage class based sensitivities. This would be even worse for muscle memory.[/quote]
[quote=NoobK]bind 1 "slot1; sensitivity 1.3"
bind 2 "slot2; sensitivity 2"
bind 3 "slot3; sensitivity 2"

would not recommend it, but each to their own i guess.

[i]edit: ninja'd[/i][/quote]

i know it's bad but playing hitscan with anything higher than 1.3-1.5 is a no bueno for me and being somewhat effective as soldier or demo with a sens that low is kinda hard
8
#8
2 Frags +
TsarbucksThat would end really badly. I already discourage class based sensitivities. This would be even worse for muscle memory.

Yeah because muscle memory for shooting hitscan weapons and slow projectile weapons is sure the same.

[quote=Tsarbucks]That would end really badly. I already discourage class based sensitivities. This would be even worse for muscle memory.[/quote]
Yeah because muscle memory for shooting hitscan weapons and slow projectile weapons is sure the same.
9
#9
2 Frags +
matchstickmani know it's bad but playing hitscan with anything higher than 1.3-1.5 is a no bueno for me and being somewhat effective as soldier or demo with a sens that low is kinda hard

I'd recommend spending some time and finding a middle ground so that you can aim well with both hitscan and projectiles. Either that or just learning how to aim with a higher sensitivity is going to be better for you in the long run

also for comparison on the i55 [R]eason team, Mike and Kaptain were the soldiers, but Mike did make a comment about how you could always tell which soldier was in a certain clip even without names since Mike played with a significantly higher sensitivity than Kaptain. However both of them are still incredible with both rockets and a shotgun, even at different sensitivities since they've taken the time to get used to it.

[quote=matchstickman]
i know it's bad but playing hitscan with anything higher than 1.3-1.5 is a no bueno for me and being somewhat effective as soldier or demo with a sens that low is kinda hard[/quote]
I'd recommend spending some time and finding a middle ground so that you can aim well with both hitscan and projectiles. Either that or just learning how to aim with a higher sensitivity is going to be better for you in the long run

also for comparison on the i55 [R]eason team, Mike and Kaptain were the soldiers, but Mike did make a comment about how you could always tell which soldier was in a certain clip even without names since Mike played with a significantly higher sensitivity than Kaptain. However both of them are still incredible with both rockets and a shotgun, even at different sensitivities since they've taken the time to get used to it.
10
#10
1 Frags +

Different sensitivities per classes can work, you're human you have a brain smart enough to realize that scoped sensitivity isn't the same as unscoped sensitivity - you can get used to different sensitivities for hitscan and projectile weapons.

Different sensitivities per classes can work, you're human you have a brain smart enough to realize that scoped sensitivity isn't the same as unscoped sensitivity - you can get used to different sensitivities for hitscan and projectile weapons.
11
#11
-1 Frags +

x

x
12
#12
0 Frags +

why would you need a different sens for melee... so you can track better?

why would you need a different sens for melee... so you can track better?
13
#13
0 Frags +

If you can't be bothered to make alisases then you can download someone else's config which I'm sure you can find and edit it, though personally I wouldn't recommend using different sense for weapons

If you can't be bothered to make alisases then you can download someone else's config which I'm sure you can find and edit it, though personally I wouldn't recommend using different sense for weapons
14
#14
0 Frags +

having different sens for each class is weird

having different sens for each class is weird
15
#15
3 Frags +
Crymadont
[quote=Cryma]dont[/quote]
16
#16
0 Frags +

i'll just stick to 1.5 for everything i guess,can i at least set my zoom sens to be lower than my main sens?

i'll just stick to 1.5 for everything i guess,can i at least set my zoom sens to be lower than my main sens?
17
#17
2 Frags +
matchstickmani'll just stick to 1.5 for everything i guess,can i at least set my zoom sens to be lower than my main sens?

Since ratio 1 is different than non scoped sens anyway, just use what zoom sens you want. Some people like using the ratio that makes your zoom sens the same as non zoom sens (which I think is .833(?) Somewhere between .79 and .83 afaik), but do whatever you want.

[quote=matchstickman]i'll just stick to 1.5 for everything i guess,can i at least set my zoom sens to be lower than my main sens?[/quote]
Since ratio 1 is different than non scoped sens anyway, just use what zoom sens you want. Some people like using the ratio that makes your zoom sens the same as non zoom sens (which I think is .833(?) Somewhere between .79 and .83 afaik), but do whatever you want.
18
#18
0 Frags +

It's a very common misconception that using different sensitivities for different things will 'screw up your muscle memory.' The fact of the matter is that some people won't be able to get used to using different sensitivities for different things, but most people would be able to do so if they gave themselves adequate time to create a link in their brains between the different settings (which would most likely not take anywhere near as long as you might expect). There were a LOT of top quake players who used vastly varying sensitivities per weapon and proved to be quite consistent.

It's a very common misconception that using different sensitivities for different things will 'screw up your muscle memory.' The fact of the matter is that some people won't be able to get used to using different sensitivities for different things, but most people would be able to do so if they gave themselves adequate time to create a link in their brains between the different settings (which would most likely not take anywhere near as long as you might expect). There were a LOT of top quake players who used vastly varying sensitivities per weapon and proved to be quite consistent.
Please sign in through STEAM to post a comment.