ROG Armoury II - V2.04.07

[MasterC]

ROG Armoury Version 2.04.07 is now available for download.
https://www.asuswebstorage.com/navigate/s/2C2BEC4330D04A4482B68FCF941F3BEA4
or
https://www.asus.com/ROG-Republic-Of-Gamers/ROG-Strix-Flare/HelpDesk_Download/
Supports: Windows 10 (64-bit) and 7 (64 & 32-bit)

*** New in Version 2.04.07 ***
- New user interface
- Mouse driver base - software simulated functions are now enabled even without Armoury II running in the background. e.g. mouse macros.
- More options for lighting customization





*** ROG Gladuis and Sica are not yet supported. ***

[MasterC]

travisandcarriekinnett wrote:
Hi all...i see where it's been reported and I also seen where they were told that all lighting effects should be working and to make sure that nothing was set to dim, but there isnt even a place to chose the ROG logo when you're doing custom lighting effects on the Claymore. You used to be able to kind of control the ROG logo by setting the spacebar color to whatever color you wanted for the logo...now it doesnt even light up that way. It kind of defeats the purpose of custom lighting effects if you cant proudly display the wicked little gaming eye that is the logo. I have the Gladius 2, Spatha, Claymore, and all ROG mousepads you make as well sitting on my desk...I would like for all of them to work together properly please. I set custom lighting effect lighting certain keys on a per game basis for the keyboard and atleast one of the mice depending on game. I use the logo color to make sure the mouse and keyboard are on the same gaming profile. Its supposed to load automatically when I launch the game...but even that doesnt work all the time. So can you please make sure the ROG logo is able to be changed in the custom lighting effect menu...even if you have to change the sapce bar color to get it to do so. Thank you for your time and effort and I look forward to the whole ROG experience that I'm so desperately seeking.

We are aware of the dim lighting in the logo, and we are working to resolve it asap. Thanks.

[krisfr92]

Just got my new laptop.

ASUS SCAR-GL503VM-ED033T
ROG PUGIO MOUSE

All out of the box, unable to install Armoury 2.04.07, neither any previous version.

All with error :

Dll function call crashed: IsSupported.IsASUSMB

[lexpolicarpio]

Still no fix best software team ever I WONT BUY ANY ASUS PRODUCT ANYMORE

[F0x135]

Unsure if these have been posted yet, but these are some of the issues i've found so far in CUSTOM mode:

Breathing/Color Cycle/WAVE/Ripple/Reactive/Starry Night/all white color despite being set differently.

Quicksand only displays purple despite picking different colors.

WAVE cannot set direction. Will only go left --> right.

All default profiles seem to work fine. Just custom colors.

I am on:

Software Version: 2.04.07
80% version: 1.09.01
Keypad version 1.02.02

[MasterC]

F0x135 wrote:
Unsure if these have been posted yet, but these are some of the issues i've found so far in CUSTOM mode:

Breathing/Color Cycle/WAVE/Ripple/Reactive/Starry Night/all white color despite being set differently.

Quicksand only displays purple despite picking different colors.

WAVE cannot set direction. Will only go left --> right.

All default profiles seem to work fine. Just custom colors.

I am on:

Software Version: 2.04.07
80% version: 1.09.01
Keypad version 1.02.02

Thanks for reporting this issue. We will rectify this by the next update.
You can update your keypad to version 1.03.00.

[F0x135]

MasterC@ASUS wrote:
Thanks for reporting this issue. We will rectify this by the next update.
You can update your keypad to version 1.03.00.

Thanks MasterC. Looking forward to the next update!

I pressed 'live update' and Armoury is saying i've got the latest; how do you update the Keypad version?

[Kincaid]

F0x135 wrote:
Thanks MasterC. Looking forward to the next update!

I pressed 'live update' and Armoury is saying i've got the latest; how do you update the Keypad version?

In the Armoury settings do you have "Check for firmware updates" enabled at Startup? If not give it a shot. Then reboot. If that doesn't work try dropping back to Armoury 1.02.26 and do the same.

I had a heck of a time getting my keypad firmware to update from 1.02.02 to 1.03.00. I used the methods listed above and finally was able to get Armoury to actually detect that 1.02.02 wasn't the latest firmware.

NOTE: ASUS, please PLEASE deal with the fact that the reCAPTCHA you are using in the forums stopped working as of 2018-03-31. It's now 2018-04-02. reCAPTCHA nicely tells users to tell site owners to visit http://g.co/recaptcha/upgrade. I just wasted 10 minutes screwing around trying to get this to post and by all rights I shouldn't have been able to but I got reCAPTCHA to finally cough up a verification code through sheer force of will and repeatedly requesting a new one.

[F0x135]

Kincaid wrote:
In the Armoury settings do you have "Check for firmware updates" enabled at Startup? If not give it a shot. Then reboot. If that doesn't work try dropping back to Armoury 1.02.26 and do the same.

I had a heck of a time getting my keypad firmware to update from 1.02.02 to 1.03.00. I used the methods listed above and finally was able to get Armoury to actually detect that 1.02.02 wasn't the latest firmware.

NOTE: ASUS, please PLEASE deal with the fact that the reCAPTCHA you are using in the forums stopped working as of 2018-03-31. It's now 2018-04-02. reCAPTCHA nicely tells users to tell site owners to visit http://g.co/recaptcha/upgrade. I just wasted 10 minutes screwing around trying to get this to post and by all rights I shouldn't have been able to but I got reCAPTCHA to finally cough up a verification code through sheer force of will and repeatedly requesting a new one.

Huh, it's weird. Yes i did have the 'Check for firmware updates' ticked. I did the rollback like you said anyway but now the 'keyboard version' has disappeared off the settings menu!



As for the captcha, i have to refresh it at least once or twice to get it to show.

[Kincaid]

F0x135 wrote:
Huh, it's weird. Yes i did have the 'Check for firmware updates' ticked. I did the rollback like you said anyway but now the 'keyboard version' has disappeared off the settings menu!

I see the 80% (keyboard) firmware listed in your image but no listing for the keypad firmware. Both should be listed, obviously. Why it won't even show the keypad is connected is beyond me unless it's not properly connected so it isn't being detected? I've found it rather easy to unintentionally cause a disconnection by moving my keyboard on my desk and not paying attention.

Armoury II is a hassle that just doesn't seem to be worth it at this point and that's what's in your screenshot. Personally, I'd uninstall and go back to 1.02.26 from the Armoury download page and don't use the internal SW Update button because it'll make you update to Armoury v2 again. Just leave the check for updates at startup enabled and let it do it's thing and hopefully it will finally detect the update. The automatic firmware update won't force you to install newer Armoury software but if you manually use the SW Update/Live Update button you will.

Hopefully, the ASUS developers will do what I requested previously and provide a standalone firmware update that users can download to get this done without Armoury being part of the process.

On a sidenote, for awhile I have suspected that ASUS' update checking mechanism has problems and is lacking in proper feedback to the user. What I mean is that when a check is done there are only 2 possible results: (1) an update is available or (2) you are running the latest version. What happens if the server is down, there are routing issues, no network connection, etc? Well, I tested. I killed my network connection and checked for an update. Armoury told me that I had the latest version of the Armoury software. I'm currently running 1.02.26 so I am most certainly not running the latest version and I had no connection to the internet so how could the software possibly have performed an actual check? It didn't. It tried, it failed, and it gave me inaccurate information. ASUS, please have the update mechanism provide proper information so that you aren't making troubleshooting even harder than it already is.

F0x135 wrote:
As for the captcha, i have to refresh it at least once or twice to get it to show.

Lucky you. I have to hit it a LOT of times 99% of the results telling me that the service shut down as of 2018-03-31 and to tell the site owner, blah, blah, blah.

[F0x135]

I haven't checked the connection, but you'd assume it'd be correctly plugged in for me to type! I'm at work now so i'll check when i get home.

I did try however, to manually update to .07 via the downloads section on the official Rog Claymore Asus page instead of the firmware update. Maybe that's why Keyboard version page disappeared? Who knows but the Asus techs.

EDIT: It turns out i was missing the 'keyboard version' as i had removed the tenkeys. The '80% version' tipped me off. Looks like Armoury needs it attached to get the full metadata. However, i'm still at keypad version 1.02.02 after all that.