Jump to content

Freeblazin

Members
  • Posts

    19
  • Joined

Reputation

10 Good
  1. I am also experiencing issues with Color Wave and type lighting. Effects are very choppy and they have reversed the led order and direction for these effects as well which screwed up all my lighting patterns. Hope the support team is able to resolve those issues or I will have to roll back and stay at the previous version.
  2. I have verified that my CoPro is running the latest 0.07.199 firmware. It sounds like you are experiencing a similar issue as I am, however in my case, Windows has never recognized the CoPro Hub when connected to the internal headers through all of my troubleshooting. Seems as if there is still some minor programmatic issues between my USB Host Controller Drivers and the CoPro firmware. Where in your case, you have had the CoPro hub recognized in Windows and it seems to drop out. The cable from the link is correct for attempting the workaround that I am currently using. It may not be a guaranteed success for you though, factors depend on if your rear IO ports actually use a different USB Host Controller that does not have the programmatic issues and your root cause could potentially be different given that you have had it detected successfully and it drops. For the cost of the cable though, I personally would attempt the workaround just to see. I also picked up an internal USB 3.0 to USB 2.0 Header adapter, which did not resolve my issue as the motherboard 3.0 header still uses the same internal USB Host Controller.
  3. I am also experiencing this issue in where the Commander Pro Hub (CLCH) or attached devices are not recognized when connected to the internal motherboard headers of the ASUS Zenith Extreme. I have verified that XHCI handoff and Legacy USB Devices are enabled in the BIOS. I have the latest ASUS chipset drivers installed as well. To note, the ASUS chipset installer package for this motherboard did not install the USB Host Controller drivers for windows 10, leaving the Microsoft generic driver to install. I also tested a manual driver upgrade to the latest AMD Controller and Hub drivers with the same results. My current workaround is a DIY USB header to dual USB cables plugged into the rear IO panel, which is working for now so I may enjoy the incredible RGB goodness of the new iCUE suite and Far Cry 5!! :biggrin: I would appreciate if this bug could remain on the list, even down near the bottom with all the iCUE dev efforts getting all the attention. I am also available to test any beta firmware towards this issue as well. Commander Pro connected to internal header Commander Pro connected to rear IO USB Host Controller AMD USB Host Controller SIV Details AMD USB Host Controller Driver Details
  4. I received my RMA mouse in today and in the process of setting it up, I have identified and resolved the root cause of the issue!! Turns out that there is an option in the global settings under the WiFi options called "Enable Power Saving Mode". I had checked this option somewhere along the way and one of the main actions of this feature is to disable the RGB lighting to save battery!! Somehow myself and Corsair tech support had missed checking this option during all of our troubleshooting. Verified that the original mouse RGB lighting works just fine. Hope this thread helps someone else with troubleshooting down the road.
  5. I currently have an open ticket, and yes it was purchased directly from Corsair. Unfortunately I have tested with different variations of zones enabled/disabled and stacked lighting effects with no success. One interesting thing I have identified though; is when I place the mouse on a wireless charging pad, all RGB zones flash white once and fade out. I assume that is the programmed visual notification for wireless charging. So that reflects that the RGB hardware controller circuit in the mouse is still operating and the issue seems to be with the software RGB portion of the profile on the device.
  6. Thanks for the reply. I had previously deleted/forgotten the mouse via Windows bluetooth settings. To make sure I just performed the following troubleshooting. I unplugged the USB Wireless Receiver and switched the mouse off. Plugged in an old usb mouse. Uninstalled CUE and checked the option to delete saved user/profile data. In Device Manager I enabled the option to show Hidden Devices and deleted all Bluetooth/USB Hubs/Mouse/HID devices to make sure Windows wasn't holding on to some saved hardware configurations. Rebooted the system. Downloaded and installed a fresh copy of the latest CUE software. Plugged the USB Wireless Receiver in and Windows successfully installed the device and it poped up in CUE. I then powered the mouse on in 2.4GHz mode. It was recognized in CUE, but still with dead RGB lighting. I then plugged the mouse in with the USB cable, Windows successfully installed the device. Cue pulled down the stored profiles from the mouse, which were the default ones with RGB enabled. I then performed another force firmware update which was successful, but still no joy with RGB lighting. When I enable Advance mode and modify configurations I have the same results, any other config changes such as reassigning keys or DPI settings will push to the mouse and work correctly but it seems as the RGB lighting has been corrupted via a hardware/software issue on the mouse itself as CUE doesn't error on profile/config pushes to the mouse and all other functionality is working correctly. I assume the firmware update is as close to a "factory reset" on the device and Corsair support will have to end up RMA'ing as almost all troubleshooting has been exhausted. I will continue to post progress with troubleshooting or replacement. I am betting that this is just a one off issue as seen with any initial production run electronic device and would not let this post discourage any viewers from picking up this mouse for their system.
  7. I just received the new Dark Core RGB SE and after initial setup, the RGB lighting no longer functions. I opened a support ticket and also wanted to reach out to the community for any additional thoughts and suggestions. Setup description and troubleshooting summary performed below: After unboxing, I charged the mouse fully using the USB cable. I then powered it on in Bluetooth mode, paired with my system which is running Win 10 and the CUE version prior to 2.22.83. The mouse entered Rainbow mode and had basic functionality. I then updated CUE to 2.22.83 via the in software upgrade feature. I attempted to adjust the lighting modes for the mouse via CUE, but the mouse stayed in rainbow mode and did not respond. I was also simultaneously exploring the button functionality and clicking through the profile, sniper. and DPI buttons. I rebooted the system, and retested adjusting the lighting modes with no affect. I then plugged in the USB Wireless receiver, which was recognized by Windows and CUE. Still unable to adjust lighting from rainbow mode. Switched back and forth between 2.4 wireless and bluetooth mode during troubleshooting and noticed the RGB lights would cut out completely some times. Then after a few minutes they cut out and have not turned back on since. Additional troubleshooting performed. Tested lighting configs in basic and advanced modes. Power cycled numerous times. Plugged the mouse in direct via USB cable. Verified the mouse came shipped with the latest firmware (0.33) via CUE. Created an Action to modify a button to successfully verify that the mouse was responding to CUE configuration changes. Cleared the onboard storage, customized the 3 separate profiles with different lighting and modified Actions, and copied over to mouse, successfully changing the actions as I change profiles. Performed a complete uninstall/reinstall of Mouse/USB Wireless Receiver/Drivers/CUE. Executed a successful force update to overwrite firmware 0.33. I have exhausted all troubleshooting efforts that I can think of at this time and believe the RGB functionality to have died somehow on the device. In reviewing the symptoms and the timing of everything, I believe the issue happened once I plugged in the USB Wireless Receiver and CUE was actually able to push configs to the device for the first time. Currently all other functionality of the mouse is working. I appreciate any suggestions and support. Thanks in advance!! **UPDATE RESOLVED** Turns out that there is an option in the global settings under the WiFi options called "Enable Power Saving Mode". I had checked this option somewhere along the way and one of the main actions of this feature is to disable the RGB lighting to save battery!! Somehow myself and Corsair tech support had missed checking this option during all of our troubleshooting. Verified that the original mouse RGB lighting works just fine. Hope this thread helps someone else with troubleshooting down the road.
  8. I decided to go ahead and test the parallel setup and yes, the strips synchronize successfully in parallel!! :biggrin: Now to see if you can chain parallel sections in serial on each channel.
  9. Is it possible to wire addressable LED strips in parallel on the same channel? I am wiring up a few strips to light up the reservoirs in my new build and have two vertical channels per reservoir that will hold 7 leds per strip. I would like to have each pair of the two 7 led strips in sync as one addressable unit. I have wired up a single 7 LED strip to the Lighting Node Pro for initial testing, but I'm hesitant on testing the parallel config as I'm not sure if the SPI interface protocol allows for that and don't want to damage the controller.
×
×
  • Create New...