-
Posts
12273 -
Joined
-
Last visited
-
Days Won
541
Content Type
Profiles
Forums
Events
Everything posted by Fiery
-
AIDA64 uses Asus' own API to send images to their display devices. Asus can implement an option in Armoury Crate to let you rotate the screen image.
-
We haven't implemented rotation support for that display because Asus said they will implement it in their software framework.
-
It's already there, in the Tools menu As for a GPU-Z alternative, we currently have no plans to develop such a panel for AIDA64.
-
Choosing a LCD USB IPS 5 inch… (prime day suggestions?)
Fiery replied to ThomasK's topic in General Discussion
Maybe BeadaPanel would suit your needs? -
The $ sign at the end of the folder names means that those are hidden shares. They are default shares of every Windows installation.
-
Matrix Orbital EVE3x-43A-IPS-800 x 480 Support ?
Fiery replied to morpheon's topic in Hardware monitoring
I've just realized you're using an old AIDA64 version. Can you please try it with the latest version of 6.88 too? We've checked v6.88 with EVE3-50 setting, and it doesn't crash for us. -
You use incorrect custom labels for your drives. The temperatures are correct, but you need to rename "M.2 980 PRO 2TB" to "KINGSTON 2TB" and "M.2 980 PRO 2TB #2" to "KINGSTON 2TB #2". You of course need to do the same with the current "KINGSTON 2TB" labels too.
-
No liquid temp sensor for NZXT New Karken(2023)
Fiery replied to Wrangler's topic in General Discussion
Please avoid posting a single issue into multiple topics. I've replied you in your other topic. This topic closed. -
fixed: NZXT New Karken (2023) not supported?
Fiery replied to Wrangler's topic in Hardware monitoring
Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery- 22 replies
-
- aio
- kraken 2023
-
(and 4 more)
Tagged with:
-
AIDA64 test memory does not display Ryzen name (Ryzen 5 5500)
Fiery replied to KseniyaTeaKisa's topic in Bug reports
Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. -
Chipset Fan Not Listed (Latest Build) (MSI MS-7C37)
Fiery replied to BillieJackFu's topic in Hardware monitoring
Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery -
I've sent you a private message about this.
-
DIMM temp not showing (MSI Pro Z790-A WiFi)
Fiery replied to tacolemons's topic in Hardware monitoring
Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. -
Matrix Orbital EVE3x-43A-IPS-800 x 480 Support ?
Fiery replied to morpheon's topic in Hardware monitoring
That's quite odd, it shouldn't crash. Does it crash with EVE3-43 setting too? Meanwhile we've also contacted the great folks at Matrix Orbital to find out what they may have changed about handling the EVE2/3/4 protocol when they created the EVE3x-43A display that you got. -
Matrix Orbital EVE3x-43A-IPS-800 x 480 Support ?
Fiery replied to morpheon's topic in Hardware monitoring
Can you please check if it works if you set it to EVE3-50? -
AIDA64 test memory does not display Ryzen name (Ryzen 5 5500)
Fiery replied to KseniyaTeaKisa's topic in Bug reports
We've already fixed that issue in to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. -
I'm afraid we have no information on where to read that setting from. It may be an internal setting in X1 software that is only accessible by X1.
-
I'm afraid it's a tough issue since AIDA64 has an automatic mechanism to detect when it falls onto a desktop location where it would be invisible. In which case it "jumps" back to the top-left coordinate (x=0, y=0) of the desktop. When you re-arrange your monitors and AIDA64 finds itself in a place where you wouldn't be able to see it, it fights it way back to your visible desktop area