04-29-2019 03:59 PM - last edited on 03-06-2024 08:19 PM by ROGBot
04-30-2019 02:15 AM
Cappycot wrote:
Let me preface this with the relevant parts I'm using in my build (also shown in my PC specs, yes this is an odd build I know):
- Asus ROG Ryujin AIO (rad size is irrelevant, this likely applies to Ryuo AIOs too)
- Trident Z RGB (all 4 slots)
- Asus ROG Maximus XI Formula (LiveDash OLED)
- Asus ROG Strix RTX GPU (should be applicable for any caliber)
What I've found about Aura 1.07.57 (and also LiveDash 1.05.02) is that the LightingService seems to improperly start up upon boot, which leads to the following:
- Trying to open Aura (1.07.57) will lead to the program not responding after a notable wait.
- Trying to use LiveDash (1.05.02) will say "Asus device no found !!" or something of that sort.
- I also notice my Trident Z RGB sticks doing the default hardware rainbow lights rather than my Aura profile.
There are two temporary potential solutions to Aura not responding (and LiveDash not finding devices), though this may not solve this particular problem for everyone:
- Try restarting your computer. This may or may not solve the problem, but it has for me at least once when starting from a shutdown.
- Restart the Asus LightingService: Go to Task Manager --> Services and find "LightingService". Right-click it and select "Restart".
- Try opening Aura/LiveDash again. It might take a bit before the window appears but it should work.
I've found that the latter seems to work consistently for me, but you would have to restart LightingService every time the computer boots into Windows. I really hope this gets fixed sooner rather than later. (Asus please... can you for at least a quarter of a year stop pushing weird exotic items like the Matrix and Helios and look at your software?)
Now onto the LiveDash issues - even with LightingService restarted and LiveDash successfully finding both the Formula and Ryujin OLEDs, I can't change the Formula OLED to a gif (regardless of whether it is predefined or custom).
The current solution (if you happen to have both OLED parts) to this is to first apply whatever gif animation you want to the Formula (it will not show up at that moment), then go to the AIO Cooler and use the default button to and select yes to setting the AIO to defaults. You will have to change the AIO settings back to whatever you wanted but the Formula OLED will change to the gif you set.
I really hope this somehow helps someone though I have my doubts.
05-01-2019 02:06 PM
05-02-2019 07:54 AM
05-02-2019 10:08 AM
joppiano wrote:
Besides that, everytime you use anything BUT static rgb, Lightingservice.exe uses extremely high CPU resources.
ASUS - Please fix this 😞
05-02-2019 09:35 AM
05-03-2019 05:39 AM
Cappycot wrote:
Let me preface this with the relevant parts I'm using in my build (also shown in my PC specs, yes this is an odd build I know):
- Asus ROG Ryujin AIO (rad size is irrelevant, this likely applies to Ryuo AIOs too)
- Trident Z RGB (all 4 slots)
- Asus ROG Maximus XI Formula (LiveDash OLED)
- Asus ROG Strix RTX GPU (should be applicable for any caliber)
What I've found about Aura 1.07.57 (and also LiveDash 1.05.02) is that the LightingService seems to improperly start up upon boot, which leads to the following:
- Trying to open Aura (1.07.57) will lead to the program not responding after a notable wait.
- Trying to use LiveDash (1.05.02) will say "Asus device no found !!" or something of that sort.
- I also notice my Trident Z RGB sticks doing the default hardware rainbow lights rather than my Aura profile.
There are two temporary potential solutions to Aura not responding (and LiveDash not finding devices), though this may not solve this particular problem for everyone:
- Try restarting your computer. This may or may not solve the problem, but it has for me at least once when starting from a shutdown.
- Restart the Asus LightingService: Go to Task Manager --> Services and find "LightingService". Right-click it and select "Restart".
- Try opening Aura/LiveDash again. It might take a bit before the window appears but it should work.
I've found that the latter seems to work consistently for me, but you would have to restart LightingService every time the computer boots into Windows. I really hope this gets fixed sooner rather than later. (Asus please... can you for at least a quarter of a year stop pushing weird exotic items like the Matrix and Helios and look at your software?)
Now onto the LiveDash issues - even with LightingService restarted and LiveDash successfully finding both the Formula and Ryujin OLEDs, I can't change the Formula OLED to a gif (regardless of whether it is predefined or custom).
The current solution (if you happen to have both OLED parts) to this is to first apply whatever gif animation you want to the Formula (it will not show up at that moment), then go to the AIO Cooler and use the default button to and select yes to setting the AIO to defaults. You will have to change the AIO settings back to whatever you wanted but the Formula OLED will change to the gif you set.
I really hope this somehow helps someone though I have my doubts.
05-03-2019 09:25 AM
nxtlevel_tv wrote:
Thx for this! This helped me to get all that stuff running again.
Hopefully all the settings are still there after restarting my system.
05-04-2019 05:26 AM
Cappycot wrote:
I really hope I'm wrong with your case, but I think you would have to manually restart LightingService every time you start your computer back up.
Maybe I can figure out how to write some script that does the job for us on startup...