Jump to content
Corsair Community

Syberon

Members
  • Posts

    112
  • Joined

Everything posted by Syberon

  1. Unfortunately this looks like the hardware switch problem. Some days ago i replaced the switch under scroll wheel and the problem is gone for me.
  2. I found that Ironclaw mouse has this problem of double click. Especially on scroll wheel button. This is my second Ironclaw Wireless mouse and i have problem of double click of scroll wheel after 4 months of use. First mouse starts to double click after 3 months on use and i replaced it by RMA. In this time a decided to replace the scroll switch by myself. Today i bougth a new switch with the same size and replaced it.
  3. I found that Ironclaw mouse has this problem of double click. Especially on scroll wheel button. This is my second Ironclaw Wireless mouse and i have problem of double click of scroll wheel after 4 months of use. First mouse starts to double click after 3 months on use and i replaced it by RMA. In this time a decided to replace the scroll switch by myself. Today i bougth a new switch with the same size and replaced it.
  4. I'm get the double click problem on my scroll wheel button too. This happens sometimes and restarting of all corsair services in service manager helps to resolve it for a some time. Restarting of iCUE only not resolves problem. This means that this is software (iCUE or services) problem. First click registered when i hold button and second when i releasing it. Normally the click should be registered only on release of button.
  5. Great fix! This bug prevents me to use RAM lighting for about year)) Now i can use it all the time)
  6. This is a common tech support practice. When I came up with a problem with my Ironclaw Wireless, tech support also asked me to look for a reset pinhole ... on the receiver. After I wrote that there were no pinholes there, I was asked to send a mouse to them for replacement. Replacing the mouse did not help - the receiver still freezes periodically when the computer wakes up from sleep and i still need to replug it sometimes. Nothing chages and support still asks to find a fantom pinhole :))
  7. This problem didn’t disappeared for me and tormented me all the time with this mouse own. I opened a ticket in support and get RMAed my mouse, but the problem doesn't disappeared on new mouse that i received from Corsair service. And now support stuff saying to me that they can't repeat this behavior on their systems.
  8. Yes, agreed. It would be usefull option.
  9. There are also Ironclaw RGB Wireless mouse in store)
  10. I have Windows 1903 and this issue is still occur. I think that problem is in dongle because switching mouse to "on - off - on" doesn't helps. Only replugging of dongle or set pc to sleep mode and wake it up again helps. I tried to use dongle with different USB ports (USB 2.0/3.0/3.1 what provided by different controllers on motherboard) but it doesn't helped.
  11. I also have this problem some time - my Ironclaw Wireless doesn't wake from sleep then PC wakes from sleep mode. Turning switch to "off - on" doesn't resolve this problem. The resolution is to: 1. replug USB dongle 2. set PC to sleep mode again and wake it up After re out of sleep mode the mouse starts to work. The problem only occurs then PC wakes from sleep. When mouse normally wakes it doesn't disconnects or other problems. This problem occurs quite often. I'm using last versions of iCUE and firmware.
  12. Tried to reproduce this on my new Ironclaw Wireless but didn't get this issue - disabling or remapping DPI buttons worked as it should.
  13. Yesterday i received my new Ironclaw Wireless and found bug described in this patch notes when mouse not detected in iCUE after waking form sleep. Today i wanted to write about this bug in support but found this update that resolves this issue))) This is good)
  14. This is old known ploblem, but dev team still not resolved it.
  15. So sad that Vengeance RGB PRO still generate high CPU load in full software control mode, this update doesn't resolved this issue.
  16. This is a matter of luck. Even if you have the same kits you can have the troubles. Earlyer i has a Vengeance LPX 3000 (15-17-17-35) 2 x 8Gb ver 5.20 and wanted to extend by getting of another same kit. I got another kit with vesion 3.20 (or some, i forgot) and all worked stable, but after some time kit 3.20 are broken and i changed it in store. Replacement kit has version 5.30 and it worked stable with kit version 5.20 only on default frequencies 2133Mhz. After i select XMP profile or manually set parameters for 3000Mhz system wont boot up. After couple of months of trying to get worked it together i sold both this kits and buy one kit of 4 modules and now it works good.
  17. My RGB PRO updated to 096.57 without any problems.
  18. I have same problem too with my K65 and K70 and beta testers team member is aware of this problem and translated it to developers.
  19. Oops! It's really doesn't work in current version. Something brokes.
  20. Make sure that option "Enable Full Software Control" unchecked. Delete all lighting effects from existing profiles to turn lighting off. After this check "Enable Full Software Control" and setup any needed color effects again. Now it will work only when iCUE is running and turns off when PC goest to sleep mode. But keep in mind that current version of iCUE have unresolved issue that gets high CPU load when "Enable Full Software Control" option activated.
  21. I have K65 too (RGB Rapidfire) and don't have this problem with latest iCUE 3.10.125 - "Save static lighting and performance to device" is present.
  22. This is not full solution, beacuse if disable sofware control then RAM lighting stay turned on in sleep mode.
  23. This option only present on motherboard that have build-in RGB lighting. My ASUS Z270H doesn't have this and only way to turn off RGB PRO lighting is to enable "Software control"....but as i wrote earlier after turning on this option iCUE starts to load CPU at 15-20%.
  24. That sad but issue with high CPU load with Vangeance RGB PRO isn't resolved. But now process that generate this load changes their name from "Corsair.Service" to "Corsair.Service.CpuldRemote".
  25. When i activate "allow full control" in Vengeance RGB Pro settings in iCUE 3.9.93 then "Corsair.Service" starts to generate 15-20% CPU load in my 7700K even without any lighting assigned to RAM. I used this option because only this function allow to turn off RAM lighting when PC goes to sleep but because of this issue i had to disable all lighting. Is the dev team aware of this issue?
×
×
  • Create New...