Apophis3

Legacy driver issue? Try another machine to test if it still does it.

Thanks for confirming, just need confirmation from Corsair that they noticed this.

On 1809 Win 10 Pro 17763.107 Lighting tab works for Dark Core, but keeps causing app shutdown with K63 (wired, I normally use it in BT mode). I can try reflashing, but I doubt it's the issue. I also tried doing a repair install with iCUE, but still does it. EDIT: reflashed, still doing it. EDIT2: appears issue is with the old default profile. Making a new profile allows me access to the tab, so some old data is causing the crash. Was able to cause the profile to crash again by adjusting the kb lighting using the preset brightness levels. EDIT3: Setting lighting to "Ice Blue" in Settings causes shutdown. Everything works even with old profiles if it's set to "Blue"

If you select the Lighting Effects tab for the K63 Wireless, iCUE shuts down and closes. Just updated the firmwares on my kb and Dark Core.

open a ticket

Agreed. A toggle switch would have been better, but I'm glad to hear that you have a working solution.

I'm a RPG'er, so I play: Diablo 3 SWTOR Dragon Age: Inquisitor Skyrim and when I get in the mood, Neverwinter Nights 2 :D

Can't you just unplug it, hold down F1+Lock and plug it in?

No firmware/software updates I am aware of. Only thing to do is open a ticket so that they can tally complaints, so they can let the engineers know what is needed.

The Qi charger is probably overheating the mouse's battery, affecting the PCB. Which is why after a while it works normally because it cooled down. The mouse needs the ability to turn off charging when full, or is not reporting max charge properly. (Like on the dashboard where it always reports 75%)

The ACPI-like monitor component may appreciate being recalibrated by doing this, however. :) Draining the battery may recalibrate the battery monitor's readings.

Same here. Still lasts as long as it should, so I believe it's an error on the software's end. If it was overcharging, the mouse would get very warm.

Try using the mouse til it goes dead, and then recharge it via wired.

I've noticed some people have issues with the mice or dongles when using USB3.1 ports vs USB3.

Wired or Qi Spot? Did you do a factory reset?

A WU update may have turned on a feature, like say Fast Boot. That's notorious for issues like this.

Power Saving settings could be turning off your USB port(s).

Wanted to chime in with my experience: I started playing Dragon Age: Inquisition again, and I noticed after a bit that my mouse would jump an extra 90 degrees when panning the camera, or running in a new direction by itself. After a lot of troubleshooting, I managed to fix the issue by addressing two issues: 1) Game was using VSync, and I discovered the game was rather laggy in response to mouse and key entries. Solved by disabling in-game VSync, and forcing Fast Sync via driver profile, in conjunction with RTSS frame capping to maxfps-0.1, which in my case is 59.987. Game is much more responsive, mouse jumping was far less severe, but still happened, which led to... 2) Cleaning my cloth Thermaltake Dasher pad. (To test, I swapped in a Ratpadz) Apparently the residue build-up on the pad was causing tracking issues. Wiped it down with warm water and some dish soap, and a sponge. Let dry overnight. Tracking is solid again. EDIT: Issue came back. After further testing with other hardware, it turns out it's the game's camera panning.

Can you test the kb using Bluetooth to see how it works?

Try enabling Legacy USB support in BIOS. You booting with UEFI?

The iCUE install also includes the drivers for the mouse, which one of them is for your side buttons. You probably just needed to do a repair install of iCUE to fix. Why they have so many different HID entries for the mouse, I don't know.

Turn off, hold down Esc and turn back on, this will restore factory settings. I think something in the fw got befuddled.

It's the encryption. The PS4 doesn't support encrypted communications.

The alternative is an icepick to your ears, which may not be desirable.

IIRC it is the advanced BT features that are enabled that prevent the PS4 from working with the Dongle, tho I don't know why it doesn't work via BlueTooth. Would be nice if there was a HW config for Consoles that we could switch to.