Zandronum

This has been an issue for awhile now, my mouse gets "stuck" quite often, when I am firing a gun for example, I let go of my mouse and it continues firing, this messes me up in deathmatch quite a bit. I know it is not my mouse actually getting stuck cause it happens in no other game except this one. I am using a Sentinel Advance Twin Laser Gaming Mouse.

This is because if your computer's lagging particularly hard, it doesn't register you releasing the mouse button. It can happen in any game. Tends to happen at under 15 fps. Just click again and it'll stop firing.

Also, if you're on a laptop, watch the touchpad and its buttons so you don't hit those by accident too.

I just bought A new computer valued at over $2200, I get over 60 fps in crysis 2.. So that is not the problem.. As I have insisted before, it is not to do with my computer.

You must have a dodgey mouse then. Have you tried other mice?
And please don't say it's not until you have tried more than 1 mouse.

I tried some piece of crap $20 mouse that seemed to work fine.. and didn't have an issue.. But I don't see how it could be the mouse if it works fine in everything else. That cheap mouse just broke and it would sure be nice if I could use the mouse I use for everything else in doom. Perhaps give me some suggestions on known gaming mice that don't have any problems?

I confirm this.
Happens with my new Logitech G500.
Doesn't happen with Logitech MX518, a very small 10$ mouse, and a couple of other cheap mice.

Happens both in Zandronum and Zdaemon. I didn't try on Odamex, Non-Doomsourceports play perfectly.

Happens to me sometimes as well. The game will freeze for a split second (not sure if freeze is the proper term for this.) and my mouse will continue firing despite me not holding the button down. I have a logitech G500 as well. It's not like it's a huge issue, as you just click again and it stops, but it's there.

EDIT: Maybe this should be reported to the bug tracker?
EDIT 2: Happens in software mode as well, that's what I use primarily.

Yeah, it doesn't have to be constant lagging, it can be triggered by random split-second hangs while sounds are loaded, textures are loading in GL, loading something in general, etc.

Just as a precaution, if you use GL, go turn on preloading GL textures. It should be in the display options somewhere. Let's see if we can troubleshoot this for everyone.

I know the solution - set the mouse's polling rate to 125 hz. I guarantee 100% it will work.

.

Ruin wrote: Happens to me sometimes as well. The game will freeze for a split second (not sure if freeze is the proper term for this.) and my mouse will continue firing despite me not holding the button down. I have a logitech G500 as well. It's not like it's a huge issue, as you just click again and it stops, but it's there.

EDIT: Maybe this should be reported to the bug tracker?
EDIT 2: Happens in software mode as well, that's what I use primarily.

I also get this occasionally but didn't know a lot of other people got it, so I never reported it thinking it was just my drivers. My mouse is a Saitek Cyborg RAT5. This is usually only a huge pain in the ass when I try to rocket jump in both software and GL.

So should this be considered a clientside problem? Now days I am sure a lot of people will be using laser gaming mice.

Edit: I now see that my mouse's dedault polling rate is 1000mhz, so once I am able too I will test this out.

Yes, this is a client sided issue with ports using the zdoom base.

zdoom isnt correctly configured to be able to handel the inputs high end gaing mice use. I just got my Cyborg R.A.T. 7 and I am having the same issue but only when I aim up and down and firing. all the other games work perfectly with my mouse.

Just need someone to report it to zdoom and imsure they'll fix it fast so zandronum, Cyclonix, and maybe zDaemon [if they even pay attention] will apply the fix in zdooms next revision.

Odamex should work fine sence it's not under the same zdoom base. I already tested and was a success. your configurations are not wrong here :).

it's zdooms fault not yours xD

---

your usb is fine being set at 1000 hz. not mhz xD just hz. thats a 1ms delay. no usb port has the clocking capability to do 1000 mhz ..

I do hope my findings on this issue may resolve some problematic issues within zdoom's base. Have a nice day :D

Haha alright thanks, when I put mhz I questioned it but didn't feel like double checking as I am stuck using a crappy android for a few days. Also thanks for the feedback and support, last time I tried to report this everyone was saying it was me and my computer, I will report on zdoom forums asap. xD Now hopefully Zandronum (I finally memorized the name!) stays up to date with zdoom.

Your observations are an indication that this could be a ZDoom bug, not a proof. It can still be a bug of your mouse driver. Nevertheless it won't hurt to bring this up on the ZDoom forum.

Torr Samaho wrote: Your observations are an indication that this could be a ZDoom bug, not a proof. It can still be a bug of your mouse driver. Nevertheless it won't hurt to bring this up on the ZDoom forum.

Evidence is clear on how the software that came with the driver clearly registers the inputs.

http://puu.sh/CFL2 <--- notice how it registers the inputs when im aiming up and down. [yet if I do this on a zdoom based port it will either not shoot or it will shoot and not register that i've let go. I think that is proof enough that it's a zdoom input bug.

these issues seems to only happen when people play a port based off the zdoom revision. I don't see zDaemon ever going to fix that. I'm sure zandronum will use the new revision of the zdoom once they've added the fix.

[note it works fine on odamex, COD:MW, Warsow, and just about every other game thats not related to the zdoom based ports. if they continue on your part then yes it's your driver fucking up. but if it only happends with a port using the zdoom revision then it's the port and not your driver.]

So I assume you tested the latest zdoom svn build here and saw that is still happening, right?

If so, please make a new bug thread here with all the analysis you showed up here.

Luke wrote:Happens with my new Logitech G500.

It happened on mine too, setting the pooling rate to 500Hz (Down from 1000) fixed it like a boss, however.

.