05-08-2012 06:09 PM
I'd like a standalone program for the g400, it conflicts with my g15 keyboard. I don't care to install so called gaming "profiles" at all. It always conflicts and loads it own settings whenever I play an opengl game that isnt a profile. I got tried of those issues, so I swaped out my g15 for something else. I don't care to have 1 driver run 2 pieces of hardware and have zero control of what I want to install. I had the option on the g15 being that I have 2 install disc's for it
05-15-2012 07:31 PM - edited 05-16-2012 09:12 AM
CharlesB - When are you planning to add Mouse Sensitivity settings to LGS like Setpoint has?
This is one of the reasons I'm still using my old G5 and not the new G400.
I use the G5 with 4/11 sensitivity in SetPoint + 1600 dpi.
I want to use the G400 at 1600 dpi as well, but I can't get it to feel the same.
Adjusting sensitivity in Setpoint just isn't the same as in Windows. I've tested with "Mouse Movement Recorder" utility that while Setpoint increased both Mouse and Pointer speed (with both being in tandem, resulting in no red lines) the Windows settings only increase Pointer (red lines = interpolation).
So, please add Mouse Sensitivity in Logitech Gaming Software, just like it is in SetPoint!
05-15-2012 08:26 PM
What makes you think that the issues you're seeing aren't simply because the G400 and G5 are different mice with different sensors?
Also, could you explain what "3/11" refers to?
05-16-2012 09:11 AM - edited 05-16-2012 09:15 AM
Because I can even make my old MX518 (optical) feel the same as the G5 (laser), but only because both allow me to set sensitivity in Setpoint.
And I meant "4/11", sorry. What I mean by that is the mouse sensitivity setting I usually use in Setpoint pointer speed.
There are 11 levels and I use the 4th one.
05-17-2012 11:18 AM
The setting need to be a lot higher in LGS to be the same speed as setpoint but you can get the same result. But I think the difference is the acceleration.
But maybe am wrong !!
You're life in ending one minute at a time.
If I did helped you just click on Kudos... It's Free !
05-18-2012 12:08 PM
Asclepius - You realize those settings mimic the windows settings, which means if it's not at the middle setting, 6, then you're getting tracking that isn't 1:1? The reason why the LGS mouse might feel different is that you shouldn't be getting tracking with rounding in LGS.
Try finding a DPI you like. You can adjust the DPI in 50 DPI incriments. Your tracking will be a lot more accurate with the DPI adjustment and not using the Windows/classic SP adjustment.
05-22-2012 07:41 AM - edited 05-22-2012 08:05 AM
Do they really mimic the Windows settings exactly? That's what I used to believe and I don't want to doubt you, but still can you explain the difference in results with Mouse Movement Recorder?:
9/11 Setpoint sensitivity implementation:
9/11 Windows sensitivity implementation:
They seem to work different somehow? Setpoint reportedly changes "Mouse movement", while Windows keeps it at 1x0. I don't understand why they show up differently.
05-22-2012 10:29 AM - edited 05-24-2012 09:54 AM
SO, I'm more than willing to eat my hat if I'm wrong, but there's something interesting with your results below:
1) I'm not sure how mouse movement recorder works when it pulls the pre/post windows values, but KHAL, which the G700 uses, is a fairly deep driver. If KHAL is catching the data on a level before mouse movement recorder captures Windows' initial setting, then it'll provide results like what you see below. I think this is the case because if you compare the movement, there are no tracking bangs, which means the system is executing on what KHAL is reporting, whereas you can see the bangs all over the windows report.
2) If the speed adjustment is being handled before Windows can grab it, KHAL will be sending the pre-increased values and windows will execute on it 1:1. This appears to be the case if you look at your first screenshot. Windows wont be applying the speed changes on post-data reception, which is why there's no bangs.
3) Mimic=imitate. Obviously the execution will be different as we're using KHAL for this and not adjusting the windows values. They should be pretty darn close to identical in feel. Though, for maximum accuracy with an LGS enabled mouse, I'd use 6/11 in Windows (or apply MarkC's Windows 7 fix if you want) and adjust the mouse's DPI.