02-08-2010 08:44 AM - edited 02-08-2010 11:16 AM
There is something I just don't get about the Logitech G9x. I've contacted support but the entire conversation ended up in a complete mess because noone knew what I was talking about, and they spent more time on verifying my mouses serial number and type, than anything else.
Ok, lets get started:
The mouse has onboard memory. According to the description this memory can store settings that the user can take around to other pcs.
Everything works fine as long as I don't move the mouse to another pc, or do a complete reinstall of the system.
If I take the mouse to another pc the DPI settings are screwed up. (Which I guess is pretty obvious because this pc thinks that the mouse is a normal mouse, and thus adds OS accelleration and speed settings, on top of the G9x's own "hardware settings".)
"Ok, I'll just install Setpoint 5.20 on the other pc" I thought.... but now things start to get strange.
Macros work, so the mouse clearly takes some data with it on the built in memory. But the mouse DPI and OS/Setpoint driver implementation settings seem to be different.
"Ok, no problem I'll just open setpoint and adjust them" I think, and open setpoint. When I select the mouse I am greeted with the following message:
"The mouse you are using is not associated with this computer. You must associate the mouse with this computer before it can be configured. Note that if you do associate the mouse with this computer, it will be restored to its default configuration and any changes you have made to your mouse will be lost. Do you wan't to associate this mouse with your computer?"
The possibilities are Yes, and No. With Yes, like the message says, clearing all settings from the mouse.
Why does the mouse even need to be "associated"(And what is this)?
Why can't it just read the settings and use them as they are, instead of bothering if they were made on this pc or not?"
I really don't see how this is supposed to work or what benefit the onboard memory is?
If you have to clear the settings every time you plug it into a new pc, you might as well just have the settings stored on the pc.
Other info: The mouse is the G9x with an x. The firmware is 1.1, the newest. I have setpoint 5.20 installed on my pc and I know how I know how use it to change my settings and store them on the mouse. I've tried this on Windows 7 RC, Windows 7 Home Premium, and on Windows XP.
02-08-2010 11:28 AM - edited 02-08-2010 11:31 AM
Are you taking the steps to burn (Onboard Memory Manager in the Profile Options window) the profiles to the mouse? Also, always make sure to hit "Apply" after making any profile changes in the profile manager... That is what will cause the profiles to download to the mouse.
Oh, and that message you're seeing is SetPoint trying to associate with the mouse. The reason it does this is to have a host computer with which the mouse can be managed. It helps the mouse keep all it's profiles straight without having to take up excess data like the name of the profile on the onboard memory. So, pick a primary computer, create the profiles you want to use on there, make your onboard memory selections using the OMM in the SetPoint Profile Options window, then make sure to hit apply when done.
02-08-2010 11:54 AM
I don't have any problems getting the profiles "burned" to the mouse.
My problem is that I don't see why the mouse needs ONE computer only from where it can be managed. This sort of kills the idea of traveling with the profiles.
I want my mouse to be able to be configured whereever I have access to Setpoint. Not one computer only.
To me it simply does not make sense, since it clearly must have cost more "development time" to create this stupid "association"-thing, than to simply let setpoint just read whatever is on currently plugged in mouse?
02-21-2010 03:07 AM
Hmm... 3 weeks and no other replies...
Am I really the only one who is puzzled by this?
To give a short summary of what I don't understand:
Whats the point of having onmouse memory, when the software locks the mouse to only one pc?
03-01-2010 07:31 AM - edited 03-01-2010 08:12 AM
my problem is lesser another PC, more my own PC with this issue. SetPoint often don't recognize my G9 (without x), they only way is to install the driver new, but then i have the same problem, i must restore the Mouse Settings to default to edit the Settings in SetPoint. Very frustrating thing... I like the mouse really, but the driver software...
Edit: Ok, i have found the SetPoint 6.0 Driver Software (the auto check for update function from the logitech software have never ever worked here), have install it and the mouse settings are still there. But i don't know if the issue with other PCs is "fixed" too.
03-01-2010 10:12 AM
Timusius- Some 3-4 years back, when the original G9 was being developed, I was told the reason why, but it's a little fuzzy. If I recall correctly, it's to have the addressing of the memory when it comes to profiles be more efficient, as certain contextual things only need to be referenced on the host PC via metadata, instead of taking up onboard memory to make it visible to all versions of setpoint on different PCs. There were some other reasons as well, but that was one that stuck in my head.
03-07-2010 08:54 AM
Thank you both for the great input.
I hadn't noticed that Setpoint 6.0 was out, so now I've tried with that.
The association thing is still there, but at least the 6.0 covers both my logitech mice in one install. (It still behaves like two completely different systems, but at least its one download, one install even though I have a G9x and a MX Revolution.)
Its not a big problem for me though, as I mostly only use the mouse on one pc, but I still wonder why one would design a mouse like that.
It has memory, but the software still forces us to wipe this memory every time we use another pc, install a new version of the driver, reinstall the OS.
Thanks to Chales B for clearing up that there is probably some obscure reason for this madness.
I have a friend with a Steelseries XAI. This mouse has the same "onboard memory so you never forget your settings". I'll have a go at this and see if it acts just as crazy :-)
04-24-2010 11:37 PM
I also have this problem and it really vexes me. Whenever I take back my mouse back home from college and plug my mouse into a computer the "burned" profiles have a clear sensitivity difference. My sensitivity and DPI are turned up - I like a faster mouse - and when I switch computer the mouse feels as slow as snail on the same "burned in" settings. In this regard the razor driver for it's mouses are far better - just install the driver and you are set to go. With logitiech you can only adjust settings from the host computer and when you transition you will feel a clear discrepancy at faster settings. Given that this doesn't affect many users - most people who touch my mouse will literally have the cursor fly off the screen - but this issue needs to be addressed as it is a serious design flaw.
03-14-2011 03:33 AM
The onboard memory might be there physically but it is 100% useless.
I share the above posters' sentiments and I honestly feel cheated. You simply have to do better than this. Too bad, I have given you a 5 star feedback but I have to rectract that. I am a huge fan of your company otherwise but this is just silly.