Alright, so last night I had some very interesting bugs.
Firstly, my mouse keeps disconnecting recently. This ONLY occurs when running PR, it never occurs at any other time. It's the same kind of disconnect you'd get if you pulled out the USB then plugged it back in again, it lasts 5-6 seconds. Logitech G500.
It's done this for a few days now, can occur at any time randomly.
Secondly, last night I had some interesting issues that made me think this issue might be linked to mumble. Upon one of my disconnects last night it caused my comms to lock open, squad chat. I use the three mouse buttons on the left side of this mouse for local, squad and squad leader comms respectively.
After closing mumble and restarting it the problem persisted, so I tried a restart of the game. The problem persisted. It was only at this time that I realised mumble had changed my keybinds, or, in fact, it hadn't changed my keybinds but somehow changed my logitech's profile settings. This mouse allows you to map the mouse to any layout you like you see.
To resolve the issue I had to open setpoint and rebind the correct layout for the mouse.
I'll be playing more tonight and hope to run into the problem again. Hopefully this detailed account will lead to some sort of solution, I am 100% sure this isn't a hardware, driver or software related problem at my end. This only occurs when running PR and has only occurred since the most recent update. The changing of my binds upon mouse disconnect has only occurred once in this timespan though, last night. Presumably the game isn't actually causing those bind changes but merely the disconnects, there was probably a setpoint related issue for mouse recognition that caused it to assign the wrong bind upon gaining connection that one time.
However, if any of the dev team have any thoughts on resolving or methods of looking into this issue in greater detail I'd be happy to carry out any suggested tests in order to further diagnose the issue. Having random disconnects of my mouse during combat is proving to be quite an annoying issue.
Mouse disconnection related bugs
-
Skitrel
- Posts: 81
- Joined: 2013-07-31 12:12
-
nAyo
- Posts: 571
- Joined: 2008-10-29 22:07
Re: Mouse disconnection related bugs
OH JESUS CHRIST, I finally find someone else with some weird logitech-mouse issues that make no sense. I have no idea if my problem is related to mumble, but now that you say that I will look out.
So first I had a G300 (using the same logitech software, with mumble keys on its buttons), and it kept disconnecting along with my keyboard, completely randomly. Sometimes unplugging/plugging back in worked, sometimes not, and what not, therefor absolutely random.
After figuring out that it was likely my mouse being dysfunctional (I presumed), I bought a new one, the logitech G400S (the new version of the G400).
I have set my mumble communication keys on my mouse buttons as well, like you, and I use the same logitech software with profiles and shit. I still have some random 'disconnections' (not that often though) like my mouse just freezing, not sure if it disconnects from USB port, and I have to reboot my PC pretty much everytime. Actually I noticed that sometimes it only temporarily freezes, like a couple of seconds, and it is apparently due to my CPU being used up to 100%.
This issue baffles me, it doesn't make much sense, but thanks to this thread I am now wondering if it can't be related to mumble, since it used to cause high CPU usage?
All my drivers are up-to-date, and just like you Skitrel I feel like it's not hardware, especially with a brand new mouse. I'm very confused by all this to be honest, I don't understand much!
So first I had a G300 (using the same logitech software, with mumble keys on its buttons), and it kept disconnecting along with my keyboard, completely randomly. Sometimes unplugging/plugging back in worked, sometimes not, and what not, therefor absolutely random.
After figuring out that it was likely my mouse being dysfunctional (I presumed), I bought a new one, the logitech G400S (the new version of the G400).
I have set my mumble communication keys on my mouse buttons as well, like you, and I use the same logitech software with profiles and shit. I still have some random 'disconnections' (not that often though) like my mouse just freezing, not sure if it disconnects from USB port, and I have to reboot my PC pretty much everytime. Actually I noticed that sometimes it only temporarily freezes, like a couple of seconds, and it is apparently due to my CPU being used up to 100%.
This issue baffles me, it doesn't make much sense, but thanks to this thread I am now wondering if it can't be related to mumble, since it used to cause high CPU usage?
All my drivers are up-to-date, and just like you Skitrel I feel like it's not hardware, especially with a brand new mouse. I'm very confused by all this to be honest, I don't understand much!
"I, for one, am not a dictator. I'm the Supreme Leader" - Master
-
saXoni
- Posts: 4180
- Joined: 2010-10-17 21:20
Re: Mouse disconnection related bugs
I only had this issue during the closed beta, I've got the G500 too.
-
Skitrel
- Posts: 81
- Joined: 2013-07-31 12:12
Re: Mouse disconnection related bugs
CPU usage is a very good call. Tonight I noticed that it occurs for me directly after large framerate drops.
Why would that cause mouse disconnection issues though? And why only when running PR? I tried to force it to occur using stress test software just now to cause 100% usage, can't get it to occur without PR being the cause.
Why would that cause mouse disconnection issues though? And why only when running PR? I tried to force it to occur using stress test software just now to cause 100% usage, can't get it to occur without PR being the cause.
-
tjaze
- Posts: 8
- Joined: 2010-10-30 19:21
Re: Mouse disconnection related bugs
I have G700, but I have no issues whatsoever.
You can try closing the Logitech SetPoint, maybe it'll help.
You can try closing the Logitech SetPoint, maybe it'll help.
Maybe it's the other way around - mouse disconnection causes huge CPU load, therefore low FPS in PR.Skitrel wrote:CPU usage is a very good call. Tonight I noticed that it occurs for me directly after large framerate drops.
-
nAyo
- Posts: 571
- Joined: 2008-10-29 22:07
Re: Mouse disconnection related bugs
Hm, could it be the logitech software being kind of 'dysfunctional' and conflicting with mumble? just throwing it there, no idea if this could even be any relevanttjaze wrote:Maybe it's the other way around - mouse disconnection causes huge CPU load, therefore low FPS in PR.
"I, for one, am not a dictator. I'm the Supreme Leader" - Master
-
Skitrel
- Posts: 81
- Joined: 2013-07-31 12:12
Re: Mouse disconnection related bugs
I've discovered the problem and found a solution to this issue. Others may have another issue but this worked for me.
There is apparently a common issue with Logitech mice and disconnects with spiking cpu usage. This is caused by the polling rate in setpoint, which the software overclocks by default to 500, when the cpu spikes too much it can cause disconnects when the driver doesn't receive enough responses from the mouse within a set period of time, prompting the software to reset the device to reaquire a smooth connection with it.
In short, reduce the polling rate (labelled "report rate") within setpoint to 125, this solves the problem. I haven't had it now for 24 hours, which is excellent.
If others receive the issue further, or if I re-encounter it. I'm willing to do further testing and research on the topic to help people out with it. This however appears to be the most likely culprit on account of PR's current cpu spikes that frequently occur. Everything ties together quite well.
There is apparently a common issue with Logitech mice and disconnects with spiking cpu usage. This is caused by the polling rate in setpoint, which the software overclocks by default to 500, when the cpu spikes too much it can cause disconnects when the driver doesn't receive enough responses from the mouse within a set period of time, prompting the software to reset the device to reaquire a smooth connection with it.
In short, reduce the polling rate (labelled "report rate") within setpoint to 125, this solves the problem. I haven't had it now for 24 hours, which is excellent.
If others receive the issue further, or if I re-encounter it. I'm willing to do further testing and research on the topic to help people out with it. This however appears to be the most likely culprit on account of PR's current cpu spikes that frequently occur. Everything ties together quite well.
