Since 2.1, everytime I use the Laser's secondary to change back to the weapon used before, weapon changes and the weapon I switch to is triggered once as well. Couldnt manage to avoid it.

I'm using a Logitech MX518 under WinXP with the latest driver.

Has anybody else experienced that bug?

No i can't confirm this..
BUT the weapon switch time was lowered in 2.1 so if you 'press' the button2 instead of just 'clicking' it its possible to switch the guns and fire the secondary fire mode. Maybe you are used to the old weapon switch time and just need to release the button faster.

Usually I'm a precision worker with the mouse. Almost nobody can work with the double klick speed and mouse acceleration settings I have on my computers. So I cant imagine I'm pressing the button for too long. Well, you never know. I keep working on it...

Maybe its some problem on windows or something but i doubt that. Its working fine here.. (debian gnu/linux unstable, nexuiz 2.1 sdl)

This bug doesn't happen to me, but what's happening to me quite often (though I can't reproduce it voluntarily) is that I get "Invalid weapon" or something, when I try to switch back to previous weapon from laser. That is after pressing "right click" with laser there appears this message on screen and I stay with laser. But this also happend with 2.0.

Thanks for reporting this.. do you have any idea what causes that? Maybe you were fragged and simply do not have you 'last gun' anymore.. or you dropped it (guess almost noone knows you can do)
This switch to last gun is very simple and i can't think of an other reason for that message.

I think sometimes it happens after respawning with laser in hand? But I'm sure that it also happens when not freshly respawned. I'm quite sure that I hadn't dropped a weapon before this (though that would be a very good explanation ).

Maybe it has something to do with cl_autoswitch = 0?

But I'll try to discover the pattern ... and report then .

I seriously think that almost nobody has extreme double-klick mouse settings like I have. I really have to be extremely careful to avoid that secondary trigger happen twice. And my settings are prolly the reason....

Those double click settings should not matter in games (i think so). Can you try if the same thing happens with 'the other binary'?

esteel wrote:Can you try if the same thing happens with 'the other binary'?

D'oh, must I ?

Dunno why, but the sdl version always sucked for me and I cant play with it. It's no alternative for me actually. So I'm gonna try the 'awful binary' and report my results, just for the hell of it.

Btw I have the same issue at my company's PC with a Logitech MX310. Which runs with mainly the same settings and drivers...

edit: Yes, same issue in the sdl version. And now I know what's so strange with the sdl for me: the sound has a lag of maybe a quarter of a second.

Urmel... wrote:And now I know what's so strange with the sdl for me: the sound has a lag of maybe a quarter of a second.

Did you try to run the SDL version with "-sndspeed 48000 -sndstereo"? Without that I have audio lag too.

Shuold not be an isue after 2.0

I've got news. As the both Batservers are still running on 2.0.1, I had the possibility to test if I get the same issue there. Funnywise I was playing with client 2.1 there and I didnt have any problems with the secondary there.

Weird