e' lokkato a 140 oppure ha un range di valori possibili?
PS: non riguarda la scala di sensibilita' orizzontale?
No.
pb_sv_cvar cl_freelook IN 1
Associated with scripts to lock the mouse at headheight, moving only from side to side. This setting is perhaps overly zealous since some players presumably do still like moving with the mouse DooM I style, but at least at one time there was much hype about scripts setting the crosshair at headheight, locked on the vertical axis so aim consists of side-to-side movement.
Update: this cvar could be useful for undesirable scripts (no-recoil, mortar) if allowed 0.
pb_sv_cvar cl_yawspeed IN 0 140
pb_sv_cvar cl_pitchspeed IN 0 140
These restrictions counter some "mortar bot" scripts which have been made to essentially automate the targeting with the mortar. There are some other suspect uses of the cl_yaw/pitchspeed cvars but the mortar scripts are of most concern, and anyway the other things seem to be tackled between these restrictions and cl_freelook IN 0.
cl_pitchspeed sets the speed that the player looks up and down if using the keyboard keys for looking up and down, while cl_yawspeed sets the speed for looking left and right. However the commands for these keys, (+lookup, +lookdown, +left & +right) also work in scripts to automatically line up and set the angle of the mortar weapon. The scripts are not particularily straightforward to use, for example they only work from set positions and have to start from the correct angle and whatnot, requires the user to tweak for their FPS settings, plus they are also inflexible in that of course they will only target the pre-made target locations.
With free reign over cl_pitchspeed and cl_yawspeed, the mortar bots can be fairly reliable, fast to target and quite deadly. The scripts can be defeated entirely by only allowing these cvars to have the value of 0, and this is currently used in European leagues. I've relaxed the reccomendation here to allow between 0 and the default of 140 because some players do like to play the mortar one-handed on a ciggy break, for example, and the maximum speed of 140 still makes the mortar scripts less reliable (and crucially, at least as slow as a human, yet still nowhere near as flexible and skilled as a talented mortar player).
Further, 140 being in the allowed range means it will not be a problem as a Punkbuster-enforced restriction: 140 is the default value and so if 140 is not allowed then players would have to manually change their settings or be kicked from the server. When using ETPro to restrict cvars then going with the League's restriction of 0-only is more palatable, since ETPro will force cvars into the allowed range and there's no problems.
Update: cl_yawspeed and cl_pitchspeed are no longer useful restrictions if ETPro 3.2.0 is being used, as +lookup and +lookdown have been nuked. This resolves the above.
pb_sv_cvar cl_freelook IN 1
Associated with scripts to lock the mouse at headheight, moving only from side to side. This setting is perhaps overly zealous since some players presumably do still like moving with the mouse DooM I style, but at least at one time there was much hype about scripts setting the crosshair at headheight, locked on the vertical axis so aim consists of side-to-side movement.
Update: this cvar could be useful for undesirable scripts (no-recoil, mortar) if allowed 0.
pb_sv_cvar cl_yawspeed IN 0 140
pb_sv_cvar cl_pitchspeed IN 0 140
These restrictions counter some "mortar bot" scripts which have been made to essentially automate the targeting with the mortar. There are some other suspect uses of the cl_yaw/pitchspeed cvars but the mortar scripts are of most concern, and anyway the other things seem to be tackled between these restrictions and cl_freelook IN 0.
cl_pitchspeed sets the speed that the player looks up and down if using the keyboard keys for looking up and down, while cl_yawspeed sets the speed for looking left and right. However the commands for these keys, (+lookup, +lookdown, +left & +right) also work in scripts to automatically line up and set the angle of the mortar weapon. The scripts are not particularily straightforward to use, for example they only work from set positions and have to start from the correct angle and whatnot, requires the user to tweak for their FPS settings, plus they are also inflexible in that of course they will only target the pre-made target locations.
With free reign over cl_pitchspeed and cl_yawspeed, the mortar bots can be fairly reliable, fast to target and quite deadly. The scripts can be defeated entirely by only allowing these cvars to have the value of 0, and this is currently used in European leagues. I've relaxed the reccomendation here to allow between 0 and the default of 140 because some players do like to play the mortar one-handed on a ciggy break, for example, and the maximum speed of 140 still makes the mortar scripts less reliable (and crucially, at least as slow as a human, yet still nowhere near as flexible and skilled as a talented mortar player).
Further, 140 being in the allowed range means it will not be a problem as a Punkbuster-enforced restriction: 140 is the default value and so if 140 is not allowed then players would have to manually change their settings or be kicked from the server. When using ETPro to restrict cvars then going with the League's restriction of 0-only is more palatable, since ETPro will force cvars into the allowed range and there's no problems.
Update: cl_yawspeed and cl_pitchspeed are no longer useful restrictions if ETPro 3.2.0 is being used, as +lookup and +lookdown have been nuked. This resolves the above.
ottimo. Thx.
Cosi' posso fare una guida per chi non ci piglia e vuole sens verticale bassa
edit: e forse ho detto una cazzata... i cl_qualcosa servono per la tastiera, non per il mouse :S
me = scarso
giochi a et da soli 5 anni , non ti abbattere
cl_pitchspeed e cl_yawspeed devono essere settati a "0"
140 è cvar detected
140 è cvar detected
fossero 5 anni continui, bacerei a terra. Al massimo "di continuo" ne ho fatti 1 e mezzo.
pero' sono scarso lo stesso
w et.
Non ti fai sentire più, per questo ti aNo sempre di meno! Lamma.
fixed
[ot]
true, a sto giro gli esami mi han messo ko.
Non tocco et da gennaio (e non vado manco nei pubblici per una partitella a scazzo, perche' non sai mai se scarichi o c'e' uno che ti deve rovinare la serata (che cittano con il bot bene settato, non me ne accorgerei e quindi gioco uguale, vedi ynos, per me era pulito pt. Ma se lo piazzano a 100% addio).
warsow idem con patate.
piango
cmq lovvo crwy, reve, btbam, kamui (e' vivo?) e tutti gli altri compagni di matte serate.
[/ot]
true, a sto giro gli esami mi han messo ko.
Non tocco et da gennaio (e non vado manco nei pubblici per una partitella a scazzo, perche' non sai mai se scarichi o c'e' uno che ti deve rovinare la serata (che cittano con il bot bene settato, non me ne accorgerei e quindi gioco uguale, vedi ynos, per me era pulito pt. Ma se lo piazzano a 100% addio).
warsow idem con patate.
piango
cmq lovvo crwy, reve, btbam, kamui (e' vivo?) e tutti gli altri compagni di matte serate.
[/ot]
Braziiiillll Braziiiilll