Fiery

SensorPanel is affected by the scaling setting of your primary display, so that shrunk effect is normal. What you can do: 1) Upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta 2) Take your original SensorPanel layout, import it into SensorPanel. 3) On the SensorPanel window press right-click --> Scale --> choose the scaling setting of your main display 4) Export the scaled SensorPanel layout and import it into Turing LCD

BTW, do you use the dynamic keys with AIDA64, to e.g. configure the LCD layout or to switch between LCD pages?

You can activate VU1 support in AIDA64 / Preferences / Hardware Monitoring / LCD / VU Dials.

In AIDA64 please press Ctrl+D --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

At bootup can you recognize which software is started first, Synapse or AIDA64?

I've sent you a private message about this.

Next month.

Do you mean that both AIDA64 itself and Razer Synapse would also auto-start AIDA64 at Windows startup?

We'll check if it's possible to develop a 64-bit DLL on ourselves. It'd be much easier to switch to direct USB communication, but then you'd lose the ability of changing the lighting. We'll try to find a middle ground: maybe it's possible to keep the Synapse framework and only take over the handling of the LCD screen by effectively "stealing" access to the LCD from Synapse. That way you could continue changing the lighting.

Thank you for your feedback! We keep pushing hard to polish out the remaining issues in the next-generation AIDA64 beta channel.

In your particular case the advantage of using higher than 100% resolution for your images would be that the rendered SensorPanel would look sharp on your 4K main monitor (with 150% display scale) as well as your small secondary display. Of course if you never wanted to use your layout on a high-DPI screen and/or you never wanted to share your layout with anyone, having blurry images on a high-DPI screen may not be of an issue.

You can create any still images and gauge state images at any pixel dimensions, it's completely up to you. But, if you wanna have for example a 288x288 pixel gauge at 100% display scale setting, in order to support high-DPI screens it's recommended to use at least 2x resolution images. So in this particular example a 2x resolution image you should use would have a resolution of 576x576 pixels. That means your layout would look great up to 200% display scaling which is what the vast majority of people use today. In other words, rarely anyone goes above 200% display scale today. However, since 5K, 6K and 8K screens are about to become more affordable and so more popular, shooting for 3x or even 4x resolution is not a bad practice either if you wanna future-proof your SensorPanel layouts.

I haven't found you in customer database. It _may_ mean that you purchased a license from an illegitimate store that sells counterfeit AIDA64 product keys. Please send me your AIDA64 product key in private message.

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. Let me know if it helps.

Thank you! Funnily enough, none of the thermal readings correspond to the CPU temperature So we will simply remove it. You can focus on the CPU Diode temperature reading that is directly read from the CPU itself.

Please check the latest beta version of AIDA64 too: https://www.aida64.com/downloads/latesta64xebeta

Thank you for your feedback!

Thank you for your feedback!

Thank you for your feedback. Please note that on many devices the standard Android Battery API is inadequately implemented, and fails to provide proper charge counter information for the battery. If you want, you can hide the incorrect charge counter information from the Battery page by unchecking the charge counter option in the AIDA64 Settings.

Thank you for your feedback! I've responded in the HEX code topic too.

@Surjeet @BHSY @COSTAJUNIOR @JariKoi Thank you for your input. Soon we will get to work

Thank you! Can you please create 2 different ISA Sensor Dumps, one at idle, the other one at load, and also check both the CPU temperature and TSensor temperature reading in IPMI and send those to me as well? Problem is, there're a bunch of thermal readings for your motherboard and it's quite difficult to figure out which is which Here's the list: 10 11 12 13 15 16 1B 20 52 57 65 71 73 75 7C T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 T: 36 36 86 102 104 50 86 36 0 0 255 11 11 36 255 Obviously stuff like zero, 11, 102, 104 and 255 Celsius are bogus readings, but the rest could well be the CPU temperature.

Please try to turn it off. The next-generation AIDA64 should position the SensorPanel correctly even without pinning.

Here's the fix: https://www.aida64.com/downloads/latesta64xebeta

@Bauze We've fixed the issue in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.