Mice - Hardware

[PooPShewT]

I called up Logitech about this...got a replacement Rev then started happneing again...called again got them to change out my mouse for a G9 mouse (since Im a gamer) and Im waiting for it now. My suggestion, call logitech and ask for a different mouse.

[Aussiewallaby]

This I'm sure is one of the biggest threads in the Logitech forums and it would seem that it has most of the techs here stumped on how to fix it.
There is no doubt about it the MX is a great mouse but it has a serious design flaw one in which Logitech does not want to admit as they would have massive call backs.
It would seem that the wireless receiver or the MX signal sender is completely insufficient for the job it was engineered for.
The fix seems to be simple place the receiver about 15cm from the mouse and it should eliminate these problems.
This seems to have fixed 8 out of 8 MX revolutions that I have had to try and fix for customers who have bought this mouse under my recommendation although they are unhappy as I am because it is not what you would expect from the Worlds Most Advanced Mouse.
Logitech I and many others put it to you to acknowledge that there is a problem Hardware side and offer up a reasonable fix or compromise for this line of mice.
The main issue I have with customers know is that they have had to purchase additional hardware in order to move the sensor closer to the mouse.
Moving the sensor closer to the mouse is not a fix its a patch and glue solution at best.
I believe the Mouse fails the FIT FOR THE JOB STANDARDS THAT CONSUMERS ARE PROTECTED BY.

[PeterLau]

I have finished trying to resolve the issue. I have posted in previous reply that I will try to

buy an entension cable so that the receiver and the mouse are very closed to each other.

After testing for 3 weeks(especially play games intensively),I confirm the mouse is back

to working without stuttering. So I advise anybody to try this.

I don't want to waste any more time to guess what problem it is.  

Now my mouse free spin mode is still out of service, as in another thread has mentioned it and I know why.

I am greatly disappointed with such a mouse problem, this is AN HIGH END MOUSE,

COSTLY ME HK$800 in HK.

People use this mouse are high end user, especially they are a few that willing to pay

for such computer accessories.

But we get the support like this.

I will (and tell all my fd) not buy any more logitech product.

P.S: I notice in the largest computer center in HK, MX/VX revolution retail price drop dramatically.

Message Edited by PeterLau on 07-27-2008 11:37 PM

Message Edited by PeterLau on 07-29-2008 07:21 PM

[drewdoog]

Does anyone have the mx5500 bluetooth revolution? I am wondering if it has the same problems as the 2.4ghz model.

[mgc8]

>Does anyone have the mx5500 bluetooth revolution? I am wondering if it has the same problems as the >2.4ghz model.

Good question! I am wondering the same? It may shed some light on the issue...

[NightCoder]

Hi, I've read a lot of posts on this thread, trying to find a solution for my problem with MX Revolution (you know, lags, sttutering, etc).

Yesterday I uninstalled the setpoint completely from my computer and ... gues what ? No more problems !!!

Hope this don't come back later, but until now, everything is fine. I'm on Windows Vista x64 and was using the latest SetPoint (4.60.something).

I recommend this test for everyone with the lag/stuttering problem ... just remove setpoint!

Greetings from Brazil,

Andre Casteliano

PS: As a side note, I've MS IntelliPoint installed on the same machine, and now I'm using it configured as 'MS Wireless Laser Mouse 5000'. The sad part is that I lose the 'free spin' mode of the MX Revolution, but now I can at least work using it ...

[mgc8]

'NightCoder'>Yesterday I uninstalled the setpoint completely from my computer and ... gues what ? No more problems !!!

It appears that you have encountered a conflict with your OS and other devices. Most people with this issue however don't use SetPoint, or not even Windows for that matter so the underlying problem is more complicated.

I for one have done some more testing with the receiver distance and, at least in my case, it is obvious that the cause for stuttering is low signal/interference... Previously, I had tried bringing the receiver really close to the mouse via an extender, but that meant the it was in a "strange" position, almost hanging vertically. Now I have managed to bring it close but this time in a horizontal position (so it'a aiming directly at the MX Revo), and it sits about 30cm away from it.

The result? NO MORE STUTTERING! I've been using the mouse intensively for two days, in both Windows and Linux, even including a few hours of FPS gaming -- the mouse works flawlessly, no stutter, no lag. It seems the actual orientation as well as distance of the receiver matters (!).

Evidently, this is not a cause for celebration as it only provides a workaround, and it's incredibly annoying to have cables running all around my desktop for a WIRELESS mouse :-/ But at least I can use it now, and maybe it will work for other people as well -- try it if you haven't already! Still waiting for a real solution from Logitech...

[Reita]

I also have Vista x64 and I am just trying your suggestion about removing the SetPoint software. I have yet to test with games for any stuttering issue.

However, I'd like to know if anyone knows how to manually set the wheel button to middle-click, without the SetPoint software? Perhaps some registry settings or something to be able to change the default action for the MX.

[dantesnake]

I tried MGC8's strategy with usb cable, and it worked.

Spread the news.

[Chucky]

I've put the MX receiver into the charger (and usb extension) of my old G7. This has cured the stuttering, most likely due to the closer proximity of the devices. The G7 was not really getting any use because of the 'double click' problem it developed. The G7 was bought to replace the MX1000 I used for a while, sadly this developed a 'double click' problem and was rendered unusable. The MX1000 replaced my faithful Cordless Click which..... oh you already guessed.... yeah, a 'double click' problem.

You'd think I would learn, but I never did.... 'Till now.

I WILL NEVER BUY LOGITECH AGAIN.