Fiery
-
Posts
12122 -
Joined
-
Last visited
-
Days Won
532
Content Type
Profiles
Forums
Events
Everything posted by Fiery
-
Request for AIDA64 Support for Thorsianway's GPU and Display System
Fiery replied to nacao's topic in Hardware monitoring
Thank you, I've sent you an email about this matter. -
We cannot really do much about a device that has a slow screen update rate.
-
Thank you for your feedback!
-
I'm glad to hear that Thank you!
-
You can activate it from the right-click context menu on the SensorPanel, or by pressing Ctrl+G on the SensorPanel. You can adjust the properties of the grid in the right-click context menu on the SensorPanel
-
Thank you for your feedback. I forgot to mention that the grid density value (in pixels) will not scale with DPI. This is a deliberate choice on our part to offer one-pixel precision grid display.
-
@kirtangl @osxdude You can check the VU Dials LCD module in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta Please note that it has a few limitations: 1) The icons design aren't finalized just yet. Please also let us know if you'd prefer 24x24 pixel icons (that we currently use) or larger ones. The VU1 Demo Application uses 30x30 pixel icons for example. 2) Currently up to four VU1 devices are supported. Let us know if you have more devices daisy-chained in your setup. 3) Only one LCD page is supported per device. It's due to the issue of slow background image update as well as due to our concerns of shortening the lifespan of the e-ink display. So in effect you need to use each VU1 device for a single indicator. 4) Since this is a special kind of LCD device (as managed internally by AIDA64), you can only place a single item on the LCD layout. That single item will handle everything: the behavior of the needle, the background image (including the icon, label, unit, and scale) displayed on the dial, and the backlight (RGB) configuration as well. 5) The background image is only updated twice a minute. This is due to our concerns of shortening the lifespan of the e-ink display. We've tried to get in touch with the developer of VU1 (Sasa Karanovic) to discuss our concerns with him. We've tried to contact him on multiple channels without luck so far though. 6) At exit AIDA64 doesn't blank (clear) the background image on the dial. This is once again, due to our concerns of shortening the lifespan of the e-ink display. AIDA64 will however return the needle to the left-most (zero) position and switches the backlight off.
-
It's been implemented in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta We've also increased the maximum image size that can be transferred without slicing it up to multiple pieces. That will allow you to build more complex layouts without having to live with the flickering artifact.
-
It's just been rolled out: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.
-
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.
-
We've added SensorPanel grid in the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta Let us know how it works for you
-
@osxdude We're getting close to presenting you the first beta build that supports VU1. Our only remaining concern is updating the image on the e-ink display. We're not quite sure if it's a good idea to update the image everytime you make any small adjustment to the display layout. We wouldn't wanna shorten the lifespan of the display. Do you guys have an idea on what the best practice may be about managing this issue?
-
Thank you, the issue will be fixed in the next AIDA64 beta update.
-
It says access denied.
-
I'm afraid that's a generic error message of the Android Battery API. And Google doesn't explain what it means or could mean: https://developer.android.com/reference/android/os/BatteryManager#BATTERY_HEALTH_UNSPECIFIED_FAILURE
-
Please check my previous post.
-
No, I'm afraid the issue cannot be resolved in a short time frame since the communication protocol has been changed in your keyboard revision
-
It's because the AIDA64 LCD and SensorPanel modules are not the same, but they're mostly compatible with each other. For example, multiple pages aren't supported by the SensorPanel.
-
It's not possible to use such alignment on the LCD.
-
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 us know how it works.
-
We'll increase the limitation on PNG file size from 512KB to 1MB in the next beta update. This will enable you to design more complex layouts without the flickering effect. However, anything beyond 1MB is not safe, since it locks the firmware of the device up
-
We're working on it
-
It all depends on the final size of the rendered PNG image that is to be submitted to the device. If the PNG is no more than 512KB in size, it can be displayed using a single USB command, and then no flickering will be experienced. If however the PNG is larger than 512KB, it has to be sliced up and then you have to live with the flickering issue I assume the manufacturer of the 8.8-inch v1.1 Turing screen will fix or mitigate this issue in an upcoming firmware, but I'm not sure if it will be possible to update the firmware at home. So you may need to buy a new screen to get the fix
-
You can get around it only by lowering the rendered image size. For example, by using a simpler background image (or no background image at all).
-
@psg237 @balaM @DavidA @Tamerz @johnskiller @Zaeedi @Amex72 @DracoCW @MaxOut @sancho76 We've been able to implement full support for Turing (Turzx) 8.8-inch v1.1 LCD screens. Please check it out and let us know how it works. https://www.aida64.com/downloads/latesta64xebeta Please note that due to firmware limitations (of the 8.8-inch v1.1 screen), complex LCD layouts may be forced to be sliced up to multiple parts before submitting the image via the USB connection. It yields to a certain flashing effect that we sadly cannot avoid. You can mitigate the issue by using a lower LCD update frequency like 2 or 3 seconds.
