M65 RGB Pro lags and/or increases DPI when idle

My M65 works perfectly fine except for two issues that usually happen when the mouse is idle for a few seconds:

 

1. A one-second delay between moving the mouse and the cursor beginning to move, as if the mouse or the sensor has been shut off and needs to start up again. Once the cursor starts moving there is no lag or unusual behavior.

 

2. The mouse sets itself to a very high DPI for no reason. This persists until I press and release the sniper button or change DPI modes.

 

Both of these issues occur on multiple computers (all using Windows 10), using either USB2 or USB3 ports.

I'm having the same issue stated in no.1

I'm having same issue as #2, spent several hours with this new mouse last nite. I even tried disabling all but one dpi selection, and somehow while playing Planetside2 it's not long before the dpi changes to some high value. If I have 2 dpi settings to switch between, it will switch to other not currently selected, and then be back to normal. I can then switch back to dpi i was using.

 

I remapped thumb switch to "down arrow", first upper thumb switch to "up arrow", and upper forward switch to "z" key. I use these a lot in game, could the arrow keys be my culprit? I just got the mouse, updated firmware to latest, and latest version CUE.

I've notice the same behavior and after looking that the CUE log files, this is what it shows:

 

[2016-05-06T13:16:48]: Requesting working state enter because session connected.
[2016-05-06T13:16:48]: Entering working state.
[2016-05-06T13:16:48]: UserSessionInfo: locked changed to 0.
[2016-05-06T13:16:48]: UserSessionInfo: locked changed to 0.
[2016-05-06T13:16:48]: SdkController. Requesting working state enter because session connected.
[2016-05-06T13:16:48]: Device profile (meta) for device vid=51d pid=2 not found.
[2016-05-06T13:16:48]: Device profile (meta) for device vid=2516 pid=20 not found.
[2016-05-06T13:16:48]: Device profile (meta) for device vid=2516 pid=20 not found.
[2016-05-06T13:16:48]: Device profile (meta) for device vid=2516 pid=20 not found.
[2016-05-06T13:16:48]: Device profile (meta) for device vid=2516 pid=20 not found.
[2016-05-06T13:16:48]: Device profile (meta) for device vid=2516 pid=20 not found.
[2016-05-06T13:16:48]: Device vid=1b1c pid=1b2e is marked 'slow startup'.
[2016-05-06T13:16:48]: Device vid=1b1c pid=1b2e is marked 'slow startup'.
[2016-05-06T13:16:48]: Device vid=1b1c pid=1b2e is marked 'slow startup'.
[2016-05-06T13:16:48]: Device vid=1b1c pid=1b2e is marked 'slow startup'.
[2016-05-06T13:16:48]: Device vid=1b1c pid=1b2e is marked 'slow startup'.
[2016-05-06T13:16:48]: Device vid=1b1c pid=1b2e is marked 'slow startup'.
[2016-05-06T13:16:49]: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_00#7&1a406a50&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-05-06T13:16:49]: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_01&col01#7&3203f695&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-05-06T13:16:49]: Created new device object: M65 PRO RGB; ready: 0
[2016-05-06T13:16:49]: Attached to device object M65 PRO RGB: b=1 a=1
[2016-05-06T13:16:49]: Attached to device object M65 PRO RGB: b=1 a=1
[2016-05-06T13:16:49]: Attached to device object M65 PRO RGB: b=1 a=0
[2016-05-06T13:16:49]: Initializing M65 PRO RGB...
[2016-05-06T13:16:49]: M65 PRO RGB : trying to force P00 instead of P04
[2016-05-06T13:16:49]: M65 PRO RGB : success, continue initialization on P00
[2016-05-06T13:16:52]: Initialized (st=1) M65 PRO RGB.
[2016-05-06T13:16:53]: Device insertion processing complete for M65 PRO RGB.

 

(Running Windows 10 BTW). I don't know what all this means to the CUE, but it looks like it is having some problems starting up. Are others seeing the similar things in their log files? (CUE/SETTINGS/SUPPORT/VIEW LOGS)

 

Dusty

[2016-05-06T19:11:56]: UserSessionInfo: locked changed to 0.
[2016-05-06T19:11:56]: UserSessionInfo: connected changed to 1.
[2016-05-06T19:11:56]: UserSessionInfo: local changed to 1.
[2016-05-06T19:11:59]: UserSessionInfo: locked changed to 0.
[2016-05-06T19:11:59]: UserSessionInfo: connected changed to 1.
[2016-05-06T19:11:59]: UserSessionInfo: local changed to 1.
[2016-05-06T19:12:01]: UserSessionInfo: locked changed to 0.
[2016-05-06T19:12:01]: UserSessionInfo: connected changed to 1.
[2016-05-06T19:12:01]: UserSessionInfo: local changed to 1.
[2016-05-06T19:12:01]: Device profile (meta) for device vid=1532 pid=11a not found.
[2016-05-06T19:12:01]: Device profile (meta) for device vid=1532 pid=11a not found.
[2016-05-06T19:12:01]: Device profile (meta) for device vid=1532 pid=11a not found.
[2016-05-06T19:12:01]: Device profile (meta) for device vid=1532 pid=11a not found.
[2016-05-06T19:12:01]: Device profile (meta) for device vid=1532 pid=11a not found.
[2016-05-06T19:12:01]: Device profile (meta) for device vid=1532 pid=11a not found.
[2016-05-06T19:12:01]: Device profile (meta) for device vid=1532 pid=11a not found.
[2016-05-06T19:12:01]: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_00#7&2ef134dd&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-05-06T19:12:01]: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_01&col01#7&172da898&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-05-06T19:12:01]: Created new device object: M65 PRO RGB; ready: 0
[2016-05-06T19:12:01]: Attached to device object M65 PRO RGB: b=1 a=1
[2016-05-06T19:12:02]: Attached to device object M65 PRO RGB: b=1 a=1
[2016-05-06T19:12:02]: Attached to device object M65 PRO RGB: b=1 a=0
[2016-05-06T19:12:02]: Initializing M65 PRO RGB...
[2016-05-06T19:12:02]: M65 PRO RGB : trying to force P00 instead of P04
[2016-05-06T19:12:02]: M65 PRO RGB : success, continue initialization on P00
[2016-05-06T19:12:04]: Initialized (st=1) M65 PRO RGB.
[2016-05-06T19:12:06]: Device insertion processing complete for M65 PRO RGB.

 

There's my startup log

Looks like about 5-10 seconds of the CUE software trying to get restarted; which must about matches the amount of time the mouse cursor stutters on my screen.

I tried disabling lighting on the mouse and noticed it helped with the delay.

 

Still waiting to find out how to fix this as it's still a very persistent and very annoying issue.