08-22-2018
11:38 AM
- last edited on
03-06-2024
08:56 PM
by
ROGBot
11-11-2018 11:12 PM
11-12-2018 06:55 AM
MasterC@ASUS wrote:
Now the original Gladius and Sica are supported in Armoury V3.00.11.
https://dlcdnets.asus.com/pub/ASUS/mb/Utility/ROG_Armoury_v30011.zip?_ga=2.165629759.1466631899.1541...
Anyone else having this issue? We can't replicate it and there are only 2 people reporting this.
11-12-2018 07:56 AM
Hypnotic wrote:
So are i need to make movie how happening every time ? and may be not much people care for last firmware and not much people buy gladius first version - there is too much variables mate but one thing is sure (there exist real problem in your firmware).
i just hope someone will take us seriously on the end because in some point more and more people with gladius v1 will get this problem and here the trust is ruining.
There are no bad feelings...
11-12-2018 12:27 AM
11-12-2018 08:37 AM
11-12-2018 08:49 AM
Hypnotic wrote:
Sorry theare is no new for my ROG Gladius I
You write about ROG Gladius II ! - as you can see Marco1971 have even newer problems with not right software and firmware...
11-12-2018 09:18 AM
Marco1971 wrote:
Hi, for me i must reverted back to 1.29 firmware (Gladius 1) to have full reboot functionality (i.e. without deadlocking my Asuy FX 753VD).
Thanks.
11-12-2018 10:22 AM
MoKiChU wrote:
With the firmware 1.30, have you tried to see on your BIOS boot priorities and configure so that the BIOS does not attempt to boot on the memory of your mouse ? I tell you this because your mouse can be seen as a storage device because there is an internal memory for storing your dpi settings etc. (hence the black screen that you see when the BIOS boot on)