This is the DPI level the mouse will return to when you: To change the default, click a DPI level that doesn't have a blue diamond above it, and then click "Assign Default". Assign Default - (Required) One DPI level must always be the default.For each DPI level you set, you'll see a tick mark rounded to the nearest 50.Įxample: If you type in "632", the software will round to 650DPI. NOTE: If you prefer, you can edit the list of DPI values to the left of the graph from 200-3600. For each DPI level you set, you'll see a tick mark. Under DPI Sensitivity Levels, drag the tick mark along the graph. Start > All Programs > Logitech > Logitech Gaming Software 8.x Acceleration - Enhance pointer precision.Separate X/Y axis settings - Configure X and Y DPI levels independently.Per profile pointer settings - Enable different pointer behavior for each profile.Report rate - Update from 125/sec (8ms response time) to 1000/sec (1ms response time).DPI levels - Configure up to five from 200-3600 in 50 DPI increments.Could you elaborate more on the process?Ĭurrently experimenting and trying to figure out what will get the job done, but more information would be helpful.The G400 gaming mouse supports these pointer customizations: Without the driver installed, these buttons always send "Virtual Key Codes" - the technique I outlined was to use AutoHotkey to remap these virtual key codes to something that MWO can recognize.Īlright, I can see how this would work, but I'm unfamiliar with AutoHotKey to the point that I don't understand how to create and run the script that you outlined.
XMouse is a 3rd party driver, but does not support custom buttons such as Zoom and Appswitch found on his mouse. Without the logitech driver installed, he is unable to remap these functions. His mouse has some other buttons apart from that ("Zoom", "AppSwitch") which are NOT native windows buttons for mice.
LMB, RMB, MMB, WheelUp/Down/Left/Right, Side Button 1/2 (Forward/Back) When you uninstall SetPoint, only buttons that windows natively supports are recognised. SetPoint is causing him problems, he cannot run it. I don't know why Logitech hasn't advanced the gaming software with the newer mice.Įdited by 9erRed, 25 October 2013 - 11:23 PM. That's my mouse, but it should see and identify yours also.Īnd uninstall the set point as it is doing you no good. You should be looking at a screen like this to set, program buttons, set the ranges for DPI, report rate, and profiles. If it doesn't work for you, it's a simple uninstall. That's the drivers for my G700 but the gamming software is the correct version you should be able to run. But I give you the link for the Gaming software, I assuming your running Win7 and 64bit. I see that the MX only shows the set point, flow control, and unifying downloads. (although once I set up the thumb and DPI buttons I haven't had to change then in months.) Once it's turned on and residing on the taskbar I have no issues, all the buttons work and MWO can "see" any changes I make. I do not have set point running during MWO only the gamming software as that is where I set the mouse DPI parameters and buttons. Which controls all the settings for both. I run a G110 and G700 and only run the gamming software 8.50 version. You can uncheck the "install set point" during the full program install, I have the unifying software for the keyboard and mouse. Install and run all the other components of the Logitech programs except the set point components. Has anyone else experienced this problem? Does anyone have a solution that doesn't involve switching devices? I love the mouse, but the software/drivers are killing me here. I've looked into UberOptions and X-MouseButton, but these solutions will not work for this mouse, as UberOptions only supports SetPoint 4.80 (Which doesn't support the Performance MX), and X-MouseButton doesn't allow me to bind Zoom and AppSwitch. Running the game along side SetPoint (As Admin), I experience significant drops in FPS, rendering the added mouse functionality relatively useless. Without SetPoint, I can run the game on max settings without a hitch. If I run SetPoint as Admin, then the game recognizes the thumb buttons, but it causes the game to suffer significantly. The latter two have been rebound to keystrokes 3 and 6 respectively).
If I run SetPoint as normal, MWO doesn't even recognize the thumb buttons (Forward, Back, Zoom, and AppSwitch. I recently purchased a Logitech Performance Mouse MX to use with MWO, and am having some trouble with the SetPoint 6.61 software that is used to program the mouse.