...

[MoKiChU]

...

[Zammin]

Ah I made a new thread today which I probably should have just posted here. Apologies, I did not see this thread beforehand. Here is the issue I ran into this morning.

Zammin wrote:
Hi

Just wanted to report an issue I ran into with AURA this morning. For some reason it would only detect 2 of my 4 RAM sticks (G.Skill F4-3200C16Q-32GTZR) even though windows was detecing all 32GB of RAM. I restarted my PC and then AURA would detect none of them at all. Only after shutting down, switching off the PSU, draining the system entirely of power and starting again did it finally detect them all again. Not sure if this is related but after this Chrome started taking a long time to open, so I restarted again and it seems to be back to normal.

My motherboard is the Maximus X Code on the latest BIOS 1602 and my RAM (model listed above) is running at it's rated/tested settings of 3200Mhz 16-18-18-38 2N 1.35V VCCIO 1.15V VCCIO 1.15V. Everything has been running nice and smooth up until this bug. Hopefully it was just a one time hiccup..

Hope this helps and can be prevented in future versions of AURA. If I have any more trouble I will report it as well.

[MoKiChU]

...

[bkgolden]

Yep, new version just crashes. Asus, nice hardware but your software is pretty bad. You should step up your service here if you expect people to continue to pay your premium prices.

[force256]

I was very happy when I saw the new version, hoping that the problem with the CPU load and other bugs will be fixed. Before installation, I even performed a complete removal, I used aura cleaner and cleaned the registry ... As a result, CRUSH. Asus, is it really so bad for you with software developers that you can not even perform a basic software check before releasing an update? I think that my next motherboard will not be products from ASUS.

[katlani]

Anyone who it actually works for him..?

[crashniels]

i just cant get this to work. it always crashes. do you know anything about the updated sdk? any documentation?

[infraction2008]

CPU usage is stupid, tbh it's always been stupid but this latest update is even stupider.

Up to 100 points lost in Cinebench just by enabling lighting effects, that's a little too much don't you think?

I've also figured out a possible "positive" bug/unintended addition. If you set the mode to color cycle but stop the lighting service it carries on but falls out of sync after a while giving you a weird rainbow puke effect but with zero CPU usage.

[Zammin]

So this morning I ran into the issue again where AURA was not detecting 2 of my 4 RAM sticks. This time I tried the same thing as last time (shut down, drain all power and power back on) but it didn't work. I then tried reseating the two ram sticks that were affected and it was still happening. Bloody hell.

I found there was a new version of AURA so I uninstalled my current version and installed the new one. I got the same crashing problem as the others here. It would always fail to start. However I managed to get it working by uninstalling it and reinstalling it but using "setup.exe" instead of "AsusSetup.exe".

My RAM is fully detected by AURA again but this version has some issues.. When I try to change more than one thing at a time (under static colours>by area) it changes many of my LEDs to random colours. The only way around it is to hit apply after each individual colour change. The other issue is when I change the number in the "Amount of LEDS" in the ADD STRIP settings screen it reverts all of my settings back to rainbow every time.

This software is truly a mess. Not only does it have very limited/basic functionality but it's incredibly buggy and unreliable. I will be very upset if I wake up tomorrow to find that 2 of my RAM sticks are stuck on their default rainbow effect again.. I don't want to have to go through this crap every day.

I would really appreciate it if one of the Dev's could be present in this thread so we know that they are listening and perhaps give some feedback as to whether these issues are being resolved.

[JohnJohn222]

[Zammin;735175]

I had similar issues as you with the color changes from static. I start with everything as static same color, then change one thing IE: Back-IO and it would additionally change another item to same color. Would not let me change the other item to a different color. Or it would not allow me to change anything. I uninstalled and went back to 1.06.17 and everything works as normal for me.

[Abaidor]

JohnJohn222 wrote:
[Zammin;735175]

I had similar issues as you with the color changes from static. I start with everything as static same color, then change one thing IE: Back-IO and it would additionally change another item to same color. Would not let me change the other item to a different color. Or it would not allow me to change anything. I uninstalled and went back to 1.06.17 and everything works as normal for me.

Hmm, I have 1.06.17 and I have issues to . For example the speed settings do not work on slow - still changing colors fast. My Trident Z RAM does not turn off while on sleep although I think that is because G.Skill powers the led from the modules so no way to turn them off while on sleep (RAM is still powered). However, the RAM will occasionally go out of sync or a module will not light up until a restart.

The back plate of my ROG Strix 1080Ti OC is out of sync with the rest of the system.

There is also lack of proper control on devices. For example how do you set individual effects on each component if not synced?

I have everything set on rainbow gradient mode now and the devices I am using are:

MB - Lights
Phanteks Halo Digital Lux (30 Addressable LEDS - This thing ROCKS!)
Phanteks 1080Ti Waterblock
Heatkiller Reservoir LED Strip
Asus Strix 1080Ti OC
Bitfenix 200mm FAN RGB
Trident Z RGB RAM 4X modules
EK Rampage VI Monoblock RGB


They need to rewrite the software and allow for further control because as it stands right now it leaves a lot to be desired especially compared to Corsairs iCUE. I am on a Rampage VIE.

I am going to build another PC soon will try going full corsair this time.