Kaijester

Necro'ing an old thread I know, but it seems there hasn't been much in the way of support here for this issue, and since this is literally day ONE of using a similar product (M65 Pro RGB) I thought I'd create an account and post a reply here showing specifically what I did that actually worked. My problem was as follows ~ back and forward buttons didn't work. Sniper button worked fine in games for lowering the dpi, but that's it. I tried repairing, reinstalling, hell I even sacrificed a cat to the digital gods. Nothing worked, at least, not for more than 5 minutes into boot. So for giggles I killed the CUE process. Miraculously the forward and back buttons came to life. Started CUE again, they stopped. Killed it, they worked. Tried this a couple times, always same result. Obviously its CUE causing the problem. Unfortunately I also have the Void Pro USB headset, and killing CUE causes the audio to go flat. Still works, but sounds like listening to AM radio. Terrible. Sadly, I must have CUE, for that as well as the pretty RGB effects I paid money for. I tried creating actions on the default profile to a->b remap the back key to the mouse back button and the forward key to the forward mouse button. No luck. Still not working. Then I noticed the light for "Advanced Mode" at the top wasn't lit. I clicked that, then noticed a new button appeared on the key selection section of the remap key part that looked like a wrench and screwdriver. I clicked it. New checkbox appeared. "Retain original key output". I checked it for both remapped actions. The buttons worked! Unfortunately, I saw no rainbow option for the RGB. Only static colors, gradients, and what have you. Rainbow only shows up under lighting effects when "Advanced" isn't on. So i turned it off. Now my mouse rolls through the colors and surprisingly, the "retain original key output" settings on both the back and forward buttons remained! Now its working! If for some reason it stops, I'll reply again, but for now ~ it's working. Un-effing-believable that you have to be Sherlock freaking Holmes to figure out how to fix a product that doesn't work right out of the box on day one several YEARS after the issue is already well known. Really Corsair? Really?