Logitech MX610 Mouse - Lagging Problems

[zachig]

Hi guys!

I recently purchased the "Left-Handed" version of the MX610 (in Japan).
I'm already using it for one week and I'm facing severe lagging problems, espceially when surfing the internet.

It seems that whenever I open several instances of Internet Explorer and/or the CPU usage is over 20%, the mouse cursor starts to lag BADLY.

The lagging is sooo bad, that sometimes, the cursor actually freezes for a second or two!!! :(

This is VERY annoying and I suspect that maybe I got a defective mouse...http://www.forums.techgage.com/images/smilies/confused.gif

I've read A LOT of reviews about this mouse, and it's very confusing since some reviews praise this mouse and say it is one of the best mice they have ever used, while other complain about the same lagging problems I'm facing and say it is a VERY BAD mouse.

I really hope it's just a small problem with my drivers and/or something similar...:roll:

BTW, I've noticed that after moving the 2.4GHz adapter from the back of the case to the front, the laggings seem to occur less often???

Have any of you experienced such problems with wireless mice before and/or with any of logitech mice and/or especailly the MX610???

It's too bad I can't send it back to the store, because like I said, I bought it in Japan...:(

I'll aprreciate any help/advice you can give...:roll: :???:

[werty316]

Maybe its because you are left handed? :lol: jk

I heard of this happen before somewhere but I can't remember. Make sure you are using upto date Logitach drivers.

Any effect at all if the adapter is near or close to the mouse on your desk?

[darkorb]

when i move my g5 fast around, i get 30% cpu usage

[werty316]

when i move my g5 fast around, i get 30% cpu usage
How does that help zachig? Instead a reply like this suggest something that'll help zachig ;)

[DragonMaster]

Defective unit? Ask Logitech if there's a known problem and if yours is affected. I know that there was a problem with suttering MX1000, some had a bad laser, some a bad receiver.

One other thing, in your BIOS, try to change the PCI latency, and enable/disable USB legacy mouse support. If you don't have legacy USB support, plug the mouse in the PS/2 port. I experience much less lagging with PS/2 than USB.

[zachig]

Any effect at all if the adapter is near or close to the mouse on your desk?
It seems that after I moved the receiver to the front of the case, the problems occurs less frequencly, though I'm not sure about it...:???:

Anyway, thanks for your suggestions guys...I guess I'll have to refer to Logitech and see if they can help as well and/or point to a specific problem (...or...but hopefully not...I just got a defective mouse. I really hope this ISN'T the situation, as like I said, I bought this mouse in Japan, so I can't return it to the store...:().

If you'll have more suggestions/ideas I'll be glad to hear...:roll:

Thanks. :wink::paw:

[Kougar]

Did you already try downloading the newest drivers/software for the thing? I've heard of some early versions being pretty bad with some mice.

If your lag is dependant on CPU usage or amount of IE windows open like you say, then I doubt it's the physical receiver that is the problem.

[zachig]

Did you already try downloading the newest drivers/software for the thing? I've heard of some early versions being pretty bad with some mice.

If your lag is dependant on CPU usage or amount of IE windows open like you say, then I doubt it's the physical receiver that is the problem.
I'm already using the latest SetPoint version (Ver. 3.10).

I'm also not sure if it's a "physical" problem or a problem with drivers and/or any other software related problem. That's why I need your help...:wink:

Anyway, like I said, I'll contact Logitech Customer Support, but I'll do it later on today, since I'm currently at work and I need to fill in the S/N of the mouse (and the mouse is currently at home...:roll:).

Anyway, I'm a little bit skeptic that Logitech Help-Desk will be able to help, as I read in their forums about a guy complaining on EXACTLY the same problems I'm facing, and he says that he already been in contact with Logitech people FOUR (!!!) times and they couldn't help him out nor tell him what's the problem...:???: :(

Anyway, thanks and I'll keep you updated if anything new will pop up...:wink:

[DragonMaster]

Tried the PS/2 adapter?

[zachig]

Tried the PS/2 adapter?
Nope, but I can try...:roll:

In case it will solve the problem, will it affect the performance of the mouse if I'll use the adpater instead or directly using the USB connector??? :???:

[DragonMaster]

Well, performance can only improve, as the PS/2 mouse port was designed just to work with a mouse. If you try the PS/2 port, make sure every buttons work, I know that when you use the MX1000 through the PS/2 port on Linux, not every buttons work, but IIRC, there's a workaround.

I don't know if it will affect the mouse's resolution or disable features, but it shouldn't under Windows. It's easy to find tho: If SetPoint doesn't alert you with the low battery status, etc.

If some features are disabled, enable USB legacy mouse support in the BIOS, Windows will see 2 mice, the USB device will allow to keep all the features, and the PS/2 one will provide you a lag-free mouse.

I've just read that some people had the same problem until they had the latest drivers, but you have them with SetPoint 3.10, so that's not your problem.

The problem is that USB wasn't really meant for low latency, so unless the BIOS, chipset, Windows USB hardware layer or drivers aren't fast, it's not working well. You shouldn't have any problems since it works well for everyone. Look in msconfig for KHALMNPR.exe, it's Logitech's own hardware layer, try enabling or disabling it(Same for setpoint)

[zachig]

Well, performance can only improve, as the PS/2 mouse port was designed just to work with a mouse. If you try the PS/2 port, make sure every buttons work, I know that when you use the MX1000 through the PS/2 port on Linux, not every buttons work, but IIRC, there's a workaround.

I don't know if it will affect the mouse's resolution or disable features, but it shouldn't under Windows. It's easy to find tho: If SetPoint doesn't alert you with the low battery status, etc.

If some features are disabled, enable USB legacy mouse support in the BIOS, Windows will see 2 mice, the USB device will allow to keep all the features, and the PS/2 one will provide you a lag-free mouse.

I've just read that some people had the same problem until they had the latest drivers, but you have them with SetPoint 3.10, so that's not your problem.

The problem is that USB wasn't really meant for low latency, so unless the BIOS, chipset, Windows USB hardware layer or drivers aren't fast, it's not working well. You shouldn't have any problems since it works well for everyone. Look in msconfig for KHALMNPR.exe, it's Logitech's own hardware layer, try enabling or disabling it(Same for setpoint)
THANKS A LOT for your help, DragonMaster!!!
I'll surely try what you suggested and let you know if it worked out for me...or not :roll:

THX again,
zachig. :wink: :paw:

[zachig]

SHORT UPDATE:

I've just noticed that since I moved the receiver MUCH MORE close to the mouse, the problem doesn't occur anymore (at least for the last hour, since I moved it).

So I think it IS/WAS a recpetion problem afterall :grin:

I'll keep checking it and I'll keep you updated...:wink:

Anyway, it still makes me wonder why should I locate the receiver soooo close to the mouse if it's a 2.4GHz receiver that should work up to a distance of 10m??? :roll:

[DragonMaster]

Try PS/2, if you still have problems, it's probably hardware related. Have you tried it on an other computer?

[Kougar]

Wireless phones, cell phones, wireless networks, bluetooth, and even microwaves can cut down wireless mouse reception to almost nothing if there are enough of them causing spectrum interference, you might want to doublecheck to see just how many are active in the room.

[DragonMaster]

Anything at ~2.4GHz will probably cause you problems. My MX1000 is the 27MHz version IIRC, no problems at all! :wink:

[werty316]

Make sure you don't have anyother wireless hardware nearby.