Tryshutting down the PC and flip the PSU off. Wait 30 seconds or hold down the case power button for 10 seconds to drain any residual power. Flip the PSU back on and start normally. This should put the Commander XT into a hardware level check for connections.
That was a typing error on my phone. I intended to write 5.14 -- that is the debut of this new User Interface. I saw one or two people mention some trouble with their Commander Core/XT lighting, but there were not any details to even categorize it. I also am not sure why this would affect those devices as changes to their main lighting setup were not part of the change. The big change is renaming "Hardware Mode" to Device Memory Mode and making it a separate operating state within the CUE app via the toggle switch. That put a lot of older devices that auto-saved data into a different category. A Commander Core/XT should not have trouble with this, but it's the only string left to pull on. I'll keep an eye for others.
1) Uninstall CUE 5. You do not need to check the box to "erase all settings", but if you haven't put a lot of effort into your profiles yet, I would delete the settings so you can start over clean after.
3) Set-up your devices. You don't need to do much beyond checking everything works, including the Commander XT. Set a few lighting effects to verify. If it works here, we have removed hardware or circuit types of defects and it almost surely means this is a CUE 5.14 error.
I can't guarantee this will work, but it should help determine whether this is software or hardware. If it doesn't work on CUE 4, then there likely is some very unusual issue. No meaningful differences for CUE between Win 10 and 11. Anything like that would cause problems on the installation, registry, or general app behavior, not very specific device issues like this.
Don't spend too much time chasing the motherboard lighting. Motherboard 5v ARGB headers are not controllable through CUE. It is a competing pathway for gear not made by Corsair. 12v RGB headers are, but not too many things using that anymore. Motherboard IO shield lighting may or may not be controllable. Some of the newer boards with complex Polymo lighting (or whatever Asus is calling it) are complex addressable arrays and not controllable through CUE. Also, when testing devices or lighting make sure you use "Lighting Effects" from the main device tab in CUE. Don't use Murals for testing. It adds a layer of complexity for testing and not all devices are Murals capable.
Ok, I did steps 1-3, was able to manually detected 1 fan, and kept adding until I had 4 fans and 1 pump. Nothing lit up but the correct things are listed for the correct ports. Updated to 5, they are still there, tried auto and manual detect in 5, still would not find anything. Regardless they are there.
I have a 14 year old using this computer quite a bit. I'm quite strongly tempted to flash C drive, and re-install windows. I don't know that he hasn't put something on that's conflicting, but this is kind of ridiculous amount of troubleshooting! ?
I'd hold off on the reinstalling Windows for the moment unless you have another reason. From my end, the drop back to 4.33 and immediate detection resolution proves this is an issue with the new 5.14 release. I am not sure why, but it likely is tied to the implementation of the new Device Memory Mode. Now that the fans are detected, go to "8 series LED fans" and Pump Cap and use the yellow + to add a new lighting effect. That should turn the lights on.
I don't know what to tell you on the motherboard support. I stopped trying to troubleshoot or use it a long time ago and prefer the board to stay off and Armory Crate uninstalled. Your MB is clearly detected, but if all it shows is the two 12v RGB headers, it is of no value to you. Might as well turn off the Asus plugin and use AC when needed to change motherboard lighting.
I've got the same problem since 5.14.93. Only difference is autodetect finds some of my fans, and lightning is working on those, I have one sp140 that does not autodetect, has been this way since the start, but always could set it up manually, but manually does not work since 5.14. I can connect a detectable fan on the port and than connect the SP140 but those are different model so not all leds work (only 4).
You can't go back to a prior 5.xx version. It's all server side, so no way to pull down the file. The workaround for mdwflyer was to uninstall CUE 5, then install CUE 4.33 and run the normal lighting wizard. Then proceed to install CUE 5 again over the top of CUE 4. The configurations files stay and the lighting config remains intact. Note this only works for solving a configuration issue. It did not resolve the end of the line physical lighting issue and we are still working on that.
i can see it both ways. On one hand, Flashaholic Should (and almost should be expected to) review the product exactly how they get it, faults and all. Because that could be the way any of us would receive it and there is value in that. For us to know that this can happen to us even when ordering more expensive lights with good reputations.
On the other hand, there is also value in Flashaholic reaching out to the company and affording them the opportunity to make it right, explain the product, explain how to find the manual (that is just odd and kind of inexcusable), and let us know if the company did any of the aforementioned things or just told him to "deal with it".
I watch reviews of other people & products where the reviewer handles it both ways. I appreciate knowing how a product may show up to me in the mail (that it could be faulty) but i more so appreciate knowing that if it Does show up faulty, the company is going to make it right, or if the company is going to ignore me.
Seems AT gets a very mixed reputation here on BLF and I can understand why based on some limited users experiences. That said, my Wizard Pro WW is my go-to travel and DIY/car repair light. It has seen many late night jobs , many trips and has yet to let me down. Tint is great, versatility is great, CRI acceptable and UI is excellent and strangely close to Zebralight
3a8082e126