Armoury crate v4.2.5.0 [report here if any issues]

[MasterC]

A new major update is being rolled out. There are several improvement and new features, many of the issues reported have also been fixed.

Suggest to uninstall Aura Sync software if already installed.

Armoury Crate v4.2.5

Core Service Updates:
Armoury Crate Service v4.2.5
Armoury Crate Lite Service v4.2.8
ROG Live Service v1.2.18.0
AURA Service (Lighting service) v3.05.18
AuraLayerManager(AURA lighting effect add-on) V0.0.18

New Features
Added AniMe Matrix Editor multi-device support
Added FanXpert feature for Motherboard device type
Added "ROG CITATEL XV" direct link to "Recommended"
Compatibility for Windows 11

Bug Fixes & Enhancements:
Fixed system suspend/resume lighting effect frozen issue
Fixed Dashboard CPU usage bug
Fixed low frequency service crash issue
Fieed G-Skill DRAM Aura Sync issue
Fixed Bluetooth headset connection bug
Optimized component update process & Fix update failed issues
Enhanced GUI layout and UI interactive behavior

Newly Supported Models:
[Mouse] TUF GAMING MOUSE X KIMETSU NO YAIBA
[Headset] TUF GAMING H1 WIRELESS
[Webcam] ROG EYE S

--------------------------------------------------------------------------------------------------------------------------
To update to the latest version of Armoury Crate, reboot and the update will run in the background automatically (do not open Armoury Crate for 10-15 minutes, and plug in the power for notebooks).

Before reporting issues, please make sure you have the latest software and firmware.
Be clear about the key issue. Mark/edit posts which are no longer relevant, tracking multiple posts in several pages not only takes time but the issue becomes unclear.

When reporting a new issue, include the following info:
1. Clear description of your issue
2. PC / Laptop
3. Aura Sync products
4. 3rd-party peripheral, audio, or lighting software
5. Wired / wireless connection
6. Reinstalled Windows?
7. Windows version & build
8. Previous version of firmware or software that worked as expected
9. Any screenshots of the issue
10. Use our log collection function: Settings=>About=>App diagnostics
Please provide a log, it's much easier to provide fixes if we can replicate as accurately as possible.

NEW - When your issue has already been reported
To make reporting easier for you, if you see another member post the same issue you are experiencing:
1. Simply reply and add your name at the bottom of the post. (If someone else has already replied, then reply to that post and add your name to the list)
2. Record and generate a log.
3. Private message me and include the following:
a. The post link at the top right of your post (copy and paste the link)

b. Link to your log file stored in cloud, and screenshots if any.
c. Service version info


--------------------------------------------------------------------------------------------------------------------------
Log Collection Tool - Instructions
First, check the Record log box to start recording
Agree to the disclaimer
Replicate the issue you are having
Click on the Generate log data button
Save the log file to a location of your choice.
Stop the recording

Even though the log file is encrypted, share the log file with me by PM (provide link to file in cloud).

Many issues have been posted previously, but a very small percentage of people have PM'd me their log. If in doubt, just send a log and remember to record first. If the issue is after shutdown: provide a log for before shutdown and one after (2 logs). Thanks everyone!

[Jimbo93]

Rossocuore wrote:
Hi all. I have been reading throug the thread and I see that it's quite known that lighting service causes a CPU usage of 5-7% when we set any effect other than static colour on RGB devices. Still no fix for this? I regret buying RGB memory sticks now; I could have been saving money and having a better CPU usage.

With 3 RGB devices and any of the basic light programs total cpu usage of all armoury crate related process is well below 2% on my system. If the cpu is in high performance clock then it will read less than .5 total for all ac process.

[Rossocuore]

Jimbo93 wrote:
With 3 RGB devices and any of the basic light programs total cpu usage of all armoury crate related process is well below 2% on my system. If the cpu is in high performance clock then it will read less than .5 total for all ac process.

Why should there be such a different behaviour between our systems?

[Jimbo93]

Rossocuore wrote:
Why should there be such a different behaviour between our systems?

there should not be in my mind. Ill post more exact info when I am home tonight.

[Jimbo93]

Add up the AC processes. The light pattern is strobe, and there is a keyboard, mouse and LED Strip being controlled. Less than .30?

[Rossocuore]

What kind of pattern are you using for your RGB devices? Did you see what happens if for example you select rainbow? Thanks.

[Jimbo93]

Rossocuore wrote:
What kind of pattern are you using for your RGB devices? Did you see what happens if for example you select rainbow? Thanks.

the pattern was strobing but there will not be a significant difference with rainbow.

[Rossocuore]

Jimbo93 wrote:
the pattern was strobing but there will not be a significant difference with rainbow.

Thanks man. I am thinking abuout giving back my RGB memory modules. 5% CPU usage is a bit too much to drive some lights.

[Jimbo93]

Rossocuore wrote:
Thanks man. I am thinking abuout giving back my RGB memory modules. 5% CPU usage is a bit too much to drive some lights.

Agree that cpu usage is too high, shouldnt be, some kind of issue going on.

[Rossocuore]

Jimbo93 wrote:
Agree that cpu usage is too high, shouldnt be, some kind of issue going on.

Any suggestion? I would appreciate it.

[Jimbo93]

Rossocuore wrote:
Any suggestion? I would appreciate it.

Have you looked at my thread about uninstalling and reinstalling? It might be helpful to review that. It is also possible that just resetting the armoury crate app followed by logging out of profile, logging back in, waiting for all cpu activity to slow, launch AC, and repeat the logout/login/launch app/open device pages, might sort it.