Since v3.2.1a, using the +speed command to walk silently has been bugged to be slower than normal for most users. This is currently band-aid fixed by editing the associated movespeedkey values for each player class by 2.5x to return the resulting speeds to their intended value.
The problem with this fix, apart from not solving the root cause, is one user has reported that they don't experience this issue when running v3.2.1a, but they haven't tested the new builds to see how the edited values affect them. The only reported difference in their setup from most others was that they were running windows 7 as well as in compatibility mode for winXP SP3. From testing on my end in windows 10 with and without compatibility mode it is bugged and needs the edited values for normal play.
A while back puzl updated the cvar locking code for movespeedkey, but reverting those changes had no affect on my end.
Since v3.2.1a, using the +speed command to walk silently has been bugged to be slower than normal for most users. This is currently band-aid fixed by editing the associated movespeedkey values for each player class by 2.5x to return the resulting speeds to their intended value.
The problem with this fix, apart from not solving the root cause, is one user has reported that they don't experience this issue when running v3.2.1a, but they haven't tested the new builds to see how the edited values affect them. The only reported difference in their setup from most others was that they were running windows 7 as well as in compatibility mode for winXP SP3. From testing on my end in windows 10 with and without compatibility mode it is bugged and needs the edited values for normal play.
A while back puzl updated the cvar locking code for movespeedkey, but reverting those changes had no affect on my end.