Request: Fire the AURA team.

[RGBJOY]

The amount of AURA problems associated in these forums is astonishing. Then you have the audacity to ask for new feature ideas? What sort of leadership is going on with this particular software? Even uninstalling leaves like 8+ registry keys. It's the junkiest **** I've ever seen and it's unacceptable.

ASUS, hire new talent to develop new AURA software please.

Better yet, the whole ASUS software suite is a littered mess of ideas. I'd just start over. It's a complete joke...

[Terepin]

Hear hear!

[Korth]

ASUS has always had strong hardware and weak software.

In my RGB experience (which is admittedly not exhaustive), the RGB implementations created by MSI, Gigabyte, Corsair, SteelSeries, Logitech, G.Skill, and NZXT each have their own issues/limitations and while some are better than ASUS AURA in some specifics none of them are any better overall.

What we really need is some sort of RGB LED technology group (with ASUS and all the other RGB-using OEMs as members) which would create and maintain a unified set of RGB platform standards, one set of RGB hardware interfaces and one set of RGB software libraries compatible with all RGB products. Or - if we're lucky - Intel/AMD will design native RGB support into upcoming chipsets, forcing all the motherboard OEMs to comply with their minimum rated specs. But until then, we just gotta live with all the faults of each OEM's RGB "ecosystem", along with all the incompatibilities and conflicts between them.

As for messy uninstalls ... it is what it is. Eight extra (and entirely unused) ASUS Registry keys isn't as offensive as hundreds or thousands of extra (and entirely unused) Microsoft Registry keys, lol. Of course there's always alternative operating systems (like most flavours of linux) which do not use messy (un)installers or Registry keys at all.

[davemon50]

Personally I think the sheer number of Aura software version updates is a testament to the good effort of the Aura team. They were probably slow to catch on that it was such an issue, but RGB's haven't been a big trend until more recent computer history, and once the team got mobilized they were probably well into catch-up mode. I feel like the proper amount of attention is given by Asus to the RGB issues (now), and as Korth says above it is a complex issue because of all the hardware and software on the market with few industry standards. Don't be too quick to throw stones, they are giving this feature more attention than many others we could discuss. The other thing Asus is being proactive about is collecting feedback in separate threads for each of the versions, and addressing issues in the next version to their best ability. And honestly I don't know what more you want.

[AlexB121]

Same here never had a issue

[jagomez]

having very less aura issues now with new updates. pretty good so far.

[panzlock]

When I use static or breathing functions the RGB light comes on for a few seconds then suddenly blink off never to return unless I change the settings to something else. Why would the static and breathing functions not work? Anyone else have this problem?

[mpoffo]

ASUS has always had strong hardware and weak software.

In my RGB experience (which is admittedly not exhaustive), the RGB implementations created by MSI, Gigabyte, Corsair, SteelSeries, Logitech, G.Skill, and NZXT each have their own issues/limitations and while some are better than ASUS AURA in some specifics none of them are any better overall.

What we really need is some sort of RGB LED technology group (with ASUS and all the other RGB-using OEMs as members) which would create and maintain a unified set of RGB platform standards, one set of RGB hardware interfaces and one set of RGB software libraries compatible with all RGB products. Or - if we're lucky - Intel/AMD will design native RGB support into upcoming chipsets, forcing all the motherboard OEMs to comply with their minimum rated specs. But until then, we just gotta live with all the faults of each OEM's RGB "ecosystem", along with all the incompatibilities and conflicts between them.

+ 1

I left a similar message on the Corsair forums. There really needs to be some standards in this area or at least some cooperation that results in better implementation for us users.