Armoury crate asus how to control rgb keys install#
So yeah, it's not a software conflict, it's just bloatware that not only doesn't even offer BASIC functionality, as it forces you to install everything plus the kitchen sink just to control a bunch of colors (and can't even do that properly).❌ You want an adjustable actuation: One handy feature on many of the latest gaming keyboards is that you can adjust the actuation for gaming or typing. I would switch in a heartbeat to the old Win32 Aura Sync instead of this Armoury Crate UWP mess if ONLY it allowed me to set the RGB of my 3090 Strix!ĪSUS promised me individual zone control when I bought this motherboard in 2019, barely two years ago, but now it seems it has left me - and others like me - out to dry.Īs someone who runs his system 24/7, another thing that really, really, gets on my nerves are the CONSTANT updates of Armoury Crate that are not only FORCED onto the user if you want to actually use the application (and if it breaks something that was previously working right, as it happens often, though luck my friend) as they NEVER bring anything new in terms of RGB functionality (and many times they require me to restart my system, as it happened just now - when all I wanted to do was change ONE $""$!" color, aaaargh). So it seems that for SOME devices Armory Crate DOES provide individual control, but not for others (which is why people are getting confused here).
For ALL the others there is no individual control, they either display the same effect and color when synced, or rainbow puke/no RGB if I unsync them. Of those, only the Gladius and the Strix 3090 have individual configurations pages that I can set if I unsync them from the rest (their device squares in the Aura Sync page in Armoury Crate have a little white arrow at the bottom right corner).
In my system I have an entry for the motherboard (which sets the same effect/color for ALL motherboard zones and both RGB headers), another for my Gladius II mouse, another for my STRIX RTX 3090, another for Memory and finally another for Addressable LED Strip (which sets the same color/effect for BOTH ARGB headers in the motherboard). Now here is the kicker: SOME of the devices that show in the Aura page of Armory Crate actually have INDIVIDUAL configuration pages if you unsync them from the rest. I find it mind blowing how ASUS can make such good hardware only to completely ruin the experience with ABYSMAL software, that even manages to go BACKWARDS instead of forward in terms of functionality. I had to throw away a perfectly good ASUS led strip and replace it with a Corsair because at least iCue allows me not only to individually control each device as I can effortlessly set different EFFECTS per device. Likewise for my TridentZ RAM: in AuraSync I could at least set solid colors for each of the leds, now it's ALL the same effect and color AS ALL THE OTHER DEVICES or no RGB/rainbow puke.
It has two ARGB headers and two RGB headers that I could previously control individually, now I cannot do that either - what is the point of giving us multiple headers and then not letting us control those headers individually?! For instance, my motherboard (an Asus Maximus XI Formula) has different zones that I could set different colors to in AuraSync, now it's all handled in block.
At least it did allow you to assign different solid colors to different devices/motherboard zones/RGB headers, etc.Īrmory Crate doesn't even allow that. The truth is that when Asus forced us to move from the Win32 AuraSync to Armory Crate to support the new 3xxx GPUs, etc, they didn't even bother to implement the BASIC functionality that existed in AuraSync.ĪuraSync was bad enough because, despite YEARS in development, it didn't even allow you to assign different **effects** to different devices, like Corsair iCue does without trouble, for instance. How did you do it? Mine doesn't show anything other than the mobo under Devices, and under Aura Sync I can only either set them to be synced or not, but not control each individually.ĭon't listen to those saying you might have a software conflict, that is NOT true.
0 kommentar(er)
