Jump to content

COSTAJUNIOR

Sensor Moderators
  • Posts

    499
  • Joined

  • Last visited

  • Days Won

    77

Posts posted by COSTAJUNIOR

  1. ────── ✦✧✦✧✦ ───── LIQUIDFORGE 1920x480 ──────── ✦✧✦✧✦ ───────────

    Modelo-LiquidForge-1920X480.thumb.png.2469661c8567b2148b37619ff49675a8.png

    ───── ✦✧✦✧✦ ──── THERMOFLUX MONITOR (600x1024)──── ✦✧✦✧✦ ───────

    Modelo-ThermoFlux-Monitor-600x1024.thumb.png.11c8940ac66b8748ccc25662a934d098.png

    ⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬⌬

    🔹 LIQUIDFORGE (1920x480)
    Style: Horizontal panel split into 3 blocks (CPU / GPU / RAM-VRAM)
    Visuals: Realistic tubing, animated fluid, and analog indicators

    Sensors:
    • CPU: temperature, usage, clock, voltage, power draw
    • GPU: temperature, clock, hotspot, usage, power draw
    • RAM & VRAM: usage, clock, fans, download/upload

    Perfect for those who love that “futuristic test bench” look.


    🔸 THERMOFLUX MONITOR (600x1024)
    Style: Vertical panel with a mecha/sci-fi vibe and a cyber-industrial touch
    Visuals: Two side tubes with bubbling fluid, energy lines, and brushed metal structure

    Sensors:
    • CPU + GPU with central gauges
    • RAM, VRAM, Drive C and D usage
    • Network speed with digital bars


    📐 Resolutions:
    LIQUIDFORGE: 1920x480 – perfect for a horizontal secondary screen
            1024x600 – optimized for compact auxiliary displays

    THERMOFLUX: 600x1024 – designed for a vertical side panel


    Wanna turn your setup into a futuristic lab or sci-fi control panel? These skins deliver it all — clean layout, functional data, and a striking visual experience.

    🧪 Like what you see? This is just the beginning — there’s a lot more coming on our website. [AidaSkins]

    • Like 1
    • Thanks 1
  2. 6 hours ago, Surjeet said:

    Hi AIDA Team,

    We all really LOVED the new colour picker dialogue which is an awesome feature addition to next generation of AIDA. I was thinking can we add something same for the Font picker too? Right now we have drop drop from where we need to use the font. Let the functionality remain the same.

    Here are a few suggestions that could enhance the Font Picker:

    • Introduce sections such as "Recent Fonts" and "Favourite Fonts" with options to Add, Save, Rename, Delete, and Clear
    • Display fonts using their initials (or small names/abbreviations in boxes, with customized names appearing on mouse hover
    • Optionally, integrate these customized fonts into the Right Click Context Menu, similar to the one used in the Colour Picker - which is absolutely fantastic, by the way!

    @Fiery 

    I completely understand that this could be a substantial and complex feature to implement. Still, I’d love to hear your thoughts, suggestions, or any feedback on the feasibility of this idea.

    Thank you so much for your continued efforts and brilliant innovations!

    Font Picker Enhancements Inspired by the New Colour Picker

    image.thumb.jpeg.8466fbe67ff19f1df1c3b7d45cf33051.jpeg

    @COSTAJUNIOR @BHSY @JariKoi 

    You all have been truly amazing with your support and feedback - thank you so much for that! 🙏

    I’d really appreciate it if you could take a moment to check out this feature request and share your thoughts or suggestions as well. Your input would mean a lot!

     

    I support this new update because I believe it can make the experience faster and more intuitive. While I'm at it, I'd like to suggest adding a search field to make it easier to find specific fonts. When the list is long, manually searching becomes tiresome. 😁

    • Like 1
  3. 3 hours ago, Fiery said:

    @Surjeet @BHSY @JariKoi @COSTAJUNIOR @rinaldop @Garageman

    Here's the next update with the following new sensor items implemented ;)

    • hour (1-12)
    • hour (0-23)
    • minute
    • second

    https://www.aida64.com/downloads/latesta64xebeta

    Awesome! Excellent update — these new hour, minute, and second sensors will open up more possibilities for real-time visuals. Thank you so much for this! I’m already imagining tons of ideas 😎👏 Let’s test it out!

  4. 1 hour ago, BHSY said:

    When I import and export my old sensor panel skin that contains many states and sensors using the latest AIDA64 Beta version, the saving time is normal (fast).

    In the older version, the time to save my file is around 1 min 30s. I'm not sure if it has something to do with my newly upgraded memory RAM. I'm using 64GB CL30 6000 MHz. My older RAM is 32GB CL 40, so that it's a big difference in response time.

    Also, if you're still worried about saving time, I advise you to use a smaller image size. For example, save all 100 images using only the clock hand and the base as part of the background image. See screenshot below.

    Screenshot-2025-06-28-194357.png

    Interesting comparison! The difference between 32GB CL40 and 64GB CL30 is definitely significant, especially for tasks that involve reading and writing large files — so it makes sense that the save time improved with the new RAM.

    I also agree with the tip about optimizing images: the smaller and fewer the unique files in the skin, the faster the saving process will be. Using a common base as the background and separating only the dynamic elements (like the clock hand) is a great practice to maintain performance. Smart move! 😉

  5. 16 minutes ago, BHSY said:

    Hi @Fiery,

    Additional Request: 

    I'm aware that this has been brought up a few times in the past, but is it still possible to have the option to add units like °C, %, RPM, V, W, etc., show on the custom sensor gauge reading? 

    Thank you.

    @Surjeet @COSTAJUNIOR @JariKoi

    I fully support these suggestions.

    Being able to format values with leading zeros, like in Excel, would make sensor readings much more consistent — especially in fixed-layout designs. It would be great if this option worked across various sensors such as usage, clock, power, temperature, time, network, memory, and others.

    Ideally, this should be configurable directly within the Modify Item menu, without relying on manual adjustments in Hardware Monitoring.

    I also believe it’s essential to allow units like °C, %, RPM, W, V, etc. to be displayed directly on custom sensors — this would make the data clearer and more complete.

    These are simple improvements, but they would make a significant difference in the customization and visual quality of the skins. 👊😉

    • Thanks 1
  6. 4 hours ago, BHSY said:

    I tried the new date gauge sensors on my existing panel skin that came with the clock hands, and I love them. Thank you so much for implementing the date gauge sensor.🥰

    Now I'm waiting patiently for the Hour, minute, and second sensors to be implemented so that I can replace the old time gauge sensors, which use four sensors for hours and 15 sensors for minutes using the (n states). 😋 

    Screenshot-2025-06-28-150304.png

    Screenshot-2025-06-28-143016.png

    The project is turning out great! But with that many states, isn't the save process getting heavier or taking longer than usual?

  7. 2 hours ago, Fiery said:

    @rinaldop @BHSY @JariKoi @Garageman @COSTAJUNIOR

    In the latest AIDA64 beta updated we've added a few new sensor items to provide more flexibility for date representation on the SensorPanel:

    https://www.aida64.com/downloads/latesta64xebeta

    The new items are:

    • year
    • month (1 to 12)
    • month name
    • day of month (1 to 31)
    • day of week (1 to 7)
    • day of week Name
    • week of year (1 to 52)

     

    This is music to the eyes of those who live for creating creative SensorPanel interfaces! With these new date sensors, we can now turn any skin into a living panel that breathes real-time data. Imagine a dashboard that dynamically changes with the day of the week or stylishly displays the month’s name — it’s like giving the layout a soul. Congrats on this addition, AIDA64 is becoming more and more powerful for those who see design as functional art. Now it’s time to play with time!

    Thank you so much for listening to the community and evolving the software with such care! ❤️

    • Like 1
  8. 2 hours ago, Fiery said:

    @Surjeet @BHSY @JariKoi @COSTAJUNIOR @Loyd

    In the latest AIDA64 beta build we've implemented the finalized color picker all across the UI:

    https://www.aida64.com/downloads/latesta64xebeta

    When configuring a SensorPanel item the new right-click context menu to allow you to pick a custom color quick & easy is also available now.

    Whoa! 😍 This is exactly what I had in mind. The new right-click context menu for quick and easy color customization in the SensorPanel is a game changer 🎨. So much faster and more intuitive now! 🙌 Huge thanks for listening to the community ❤️. We truly appreciate this kind of update 🔧🔥. Keep up the amazing work! 🚀👏

  9. 33 minutes ago, Fiery said:

    I'm not sure what you mean.  Please wait for the next build, and then you will see how we imagined the whole thing to work.  What you can see now is not the final logic of operation.

    Okay, I don't speak English, so I have to rely on translators, which never manage to interpret my ideas correctly 🤦‍♂️. In the end, all I can do is sit with a bag of popcorn 🍿, waiting for another update that will surely turn out amazing 😅.

    • Like 1
  10. 9 minutes ago, Fiery said:

    Thanks for your feedback.  The right-click access is only a temporary solution.  We wanted to wait for the new color picker dialog to mature and receive all requested updates and features before we replace the old (Windows standard) color picker dialog.  That's why we kept the old functionality with left-click and added the new color picker dialog via right-click.  Not everyone on the AIDA64 beta channel is aware of the "under construction" new color picker dialog, that's why we kept the old one using the old method (left-click) and added a "secret" right-click access to open the new dialog.

    What will happen next: we sack the old color picker dialog and make the new one open with left-click.  We then will use the right-click to open the context menu with the list of custom colors to offer you a shortcut to select your predefined colors with only 2 clicks.

    Wouldn't it be simpler to keep access the same as it is in the current palette? Clicking on a color would open the new selection box with all the new features built in.

  11. 35 minutes ago, Fiery said:

    @Surjeet @BHSY @COSTAJUNIOR @JariKoi

    Here's the next beta build:

    https://www.aida64.com/downloads/latesta64xebeta

    In this build we've implemented both a set of custom colors and recents colors, as per your request.  We've sacked the previous set of basic colors and went with the standard set that MS Paint uses.  You can now save and load the custom colors palette using the standard GPL file format.  We've slightly increased the size of the color patches and added frame around them as well.

    In case you guys give your blessings to the current state of the new color picker dialog, then we implement it all across the AIDA64 UI.  That will enable us to also implement the proposed right-click context menu with the list of custom colors (since right now the right-click on the color patches is "occupied" by the new color picker dialog).

     Perfect 😍, this update is very well on track and represents a big leap in usability. Switching to the MS Paint color set was a great choice, and the compatibility with the GPL format makes things much easier for those who work with custom palettes. The ability to easily save and load colors is a major plus.

    The new patch size (18x18px) with borders makes everything cleaner, more functional, and pleasant to use — especially with the automatic scaling based on Windows settings. That ensures accessibility in all scenarios.

    The only thing that still bothers me a little is having to use the right mouse button to access the new color palette. I hope to see it available more directly, without relying on that shortcut.
    That said, the recent colors system looks great, and the palette customization method is clear and intuitive. Keep up the great work — the refinement is looking impeccable! 😉

  12. 🟡 Radiation Protocol - in 1024x600 and 1920x480

    This skin was forged in the core of a fictional nuclear reactor — post-apocalyptic aesthetic, industrial vibe, and visuals inspired by radioactive containment panels. Every detail crafted for those who crave extreme monitoring with a brutalist flair.

    🔥 Features:

    Full monitoring for CPU and GPU (temperature, load, voltage, power draw, fan speed, RAM/VRAM usage).

    Analog gauges styled after industrial emergency dials.

    Storage indicators with custom SSD icons.

    Nuclear-themed visuals with radiation icons, worn metal textures, and glowing green/amber tones.

    The "High Temperature" nuclear symbols dynamically reflect the CPU (left) and GPU (right) temperature states.

    Discover this and other models at: [AidaSkins]

    Radiation-Protocol-1024X600.thumb.png.ac3d8fe5225d1b9b1f9ee5fe57853d79.png

     

    • Like 2
    • Thanks 2
  13. 8 hours ago, Fiery said:

    Thank you!  Please let me ask a few specifics about your ideas -- which are very much aligned with how we imagine the next steps for this feature.  These are of course such matters where everyone else could chime in as well  @BHSY @JariKoi @Surjeet @Lord

    1) Is it okay to have a single palette, just how it is managed by e.g. MS Paint?  So only a single set of Custom Colors.  We of course would add a Save and Load button to let you export/import the palette.

    1/b) ... or you'd like to have multiple palettes shown on the GUI, and you could switch between them via a tabcontrol visual element for example?

    2) How many custom colors would you like to have on the custom palette?  MS Paint (of Win11 24H2) for instance has 24 entries there, is it enough, is it too many, too few?

    3) When it comes to exporting the custom colors, is there an industry standard palette file format that we should use or should we define our own file format?

    4) When you add the current color to the custom colors palette, would you like to have the ability to name the color?

    5) Would you like to have a special right-click context menu added to the color patches (in e.g. the SensorPanel item configuration dialog) to show a popup menu of the custom colors?  That way you could save a few clicks when you would use the new color picker dialog just to pick a custom color from your existing set.  I hope you understand my concept.  If not, let me know, and I'll make a mockup to show you how would it look like.

    6) As for recent color history, how many colors would you like to see there?

    7) What do you think about the current size of the basic color patches on the color picker dialog?  They're currently 16x16 pixel squares.  Are they properly sized or should they be a bit larger?  For example MS Paint (of Win11 24H2) uses 20 pixel diameter circles.

    1) Yes, a single custom palette like in MS Paint is perfectly fine. Having Save and Load options is enough to give flexibility.

    1/b) No, I don't see the need for multiple palettes with tabs at this point. I prefer keeping the interface simple and focused, with just one customizable palette.

    2) 24 custom colors is a good number. It's a balanced amount — not too many, not too few — and it keeps things organized.

    3) If possible, using a standard format like .ASE (Adobe) or .GPL (GIMP) would be great for compatibility. But if it's easier to create a custom format, that's fine too — as long as it's easy to read and edit.

    4) Yes, naming the custom colors would be very helpful. It makes it easier to identify specific colors used in a project.

    5) Yes, a right-click context menu on the color patches (like in the SensorPanel item configuration) would be very useful. It would save time by allowing quick access to saved colors without opening the entire color picker dialog.

    6) 10 recent colors would be ideal. That gives good recall without taking up too much space.

    7) 20x20 px would be a better size than the current 16x16 px. Slightly larger patches — like the 20 px circles used in MS Paint — would improve usability, especially on high-DPI or 4K screens.

    • Like 1
  14. 15 minutes ago, Surjeet said:

    Thank you for your re-consideration :)

    I also got a notification that @COSTAJUNIOR quoted me on this topic; however, I am unable to find his message. Would love to see the feedback if this feature is worth to be implemented!!

    Hey! I also found the idea interesting and fully support the implementation of this new feature. I've developed a few projects in this style, but I noticed that the saving process became quite slow due to the large number of states created.😉

    • Like 1
  15. 1 hour ago, Fiery said:

    @BHSY @JariKoi @COSTAJUNIOR

    Please check the first implementation of the new color picker dialog in the latest AIDA64 beta build:

    https://www.aida64.com/downloads/latesta64xebeta

    new color picker.png

    light.png

    It's not yet finished, so it's not implemented all across the UI just yet.  You can check it out by using right-click on the color patches instead of the usual left-click.  It's only available in the SensorPanel item configuration dialog at this time.

    What's left from our planned set of features is the management of the set of custom colors.  However, you may have more ideas on how to make the new panel more usable, more powerful for your purposes.  So please let us know how you like it so far, what's missing, what do you see in other color picker dialogs that you'd like us to replicate in ours.

    Wow! 😍 Once again, you’ve surprised us with these amazing updates. Congratulations on fulfilling yet another one of our requests — it really shows your care and attention to the community.
    I'd like to take the opportunity to suggest a few improvements, if possible.

    Customizable and Saved Color Palette: Managing custom colors is essential. Being able to save, name, and even export/import palettes would help a lot, especially for those who create multiple skins and need to maintain a consistent visual identity.

    Recent Color History: A small history of recently used colors would also make a big difference in the creative workflow.

    Also, it would be great to make the new panel more intuitive. I’m not sure if the old version will be replaced when this one is officially released, but removing the need for a right-click to access the new color picker would definitely improve the usability. A more accessible and straightforward interaction would benefit all users.  👊😉

    • Like 1
  16. 43 minutes ago, Fiery said:

    @BHSY @Surjeet @JariKoi We've implemented the new feature in the latest AIDA64 beta update available at:

    https://www.aida64.com/downloads/latesta64xebeta

    We've tried to implement it in a smooth way to provide support for up to 101 gauge states.  You need to use the Add button on the new gauge states management dialog to add your state images.  They all have to end with either "-N.png", "-NN.png", "-NNN.png", "_N.png", "_NN.png", "_NNN.png" where N is a 1-digit number, NN is a 2-digit number and NNN is a 3-digit number.  AIDA64 will fill the gaps with empty states to make the states list continuous.

    Let us know how it works.

    Man… I don’t even know where to start. This update turned out crazy good! I tested it with 101 states and the result was insane — seriously, you nailed it. Congrats on the work, it’s getting better and better, and huge thanks for always listening to us and delivering more than we expect.
    I N C R E D I B L E. No exaggeration. 😍 😍

    Now, just one question: with this change, does the “Change Source” option still make sense, or did it lose its purpose?

  17. 3 hours ago, Fiery said:

    @BHSY @JariKoi @Loyd @Surjeet We've improved on the source changing feature in the latest AIDA64 beta update available at:

    https://www.aida64.com/downloads/latesta64xebeta

    Improvements are:

    1) You can now change source on multiple items at once

    2) All sensor items are listed in the Change Source dialog, not just the type of the sensor item selected

    3) Labels are updated automatically, as long as the label is not shown on the layout

    Thanks, it looks perfect! 😀

  18. 16 hours ago, Fiery said:

    It's strange, it works for others.  And we've checked, and the minium/maximum values aren't altered at all.

    I managed to find the function. It was actually there all along — the trick is to right-click on the sensor you want to change and select the Change Source option. I was double-clicking instead, which is why that option never showed up.😁

    I’d like to suggest an improvement: when selecting Change Source, the system should display all available sensors, not just those in the same category. For example, if I click on a CPU temperature sensor, it only shows other temperature-related sensors. This really limits customization.

    Another important suggestion: it would be great to have an option to select multiple sensors at once and apply changes to all of them automatically. That would save a lot of time instead of having to update each one manually.

  19. 4 hours ago, Fiery said:

    @BHSY @COSTAJUNIOR @Surjeet @Loyd @JariKoi

    We've implemented the new Change Source item in the right-click context menu of the SensorPanel Manager in the latest AIDA64 beta update available at:

    https://www.aida64.com/downloads/latesta64xebeta

    Let me know how you like it.

    Thank you again for the update. However, in my case, it had no practical effect, even after applying it. When I replace a sensor — for example, switching the CPU temperature sensor to the GPU — the minimum and maximum values are not preserved. I'm specifically referring to the use of sensors with 100 states distributed across 8 custom sensors.

    I would also like to suggest adding the option to select all 8 custom sensors at once and change them simultaneously, instead of having to modify each one individually.

  20. 4 hours ago, Fiery said:

    @BHSY @COSTAJUNIOR

    Okay, so only the sensor item source will be updated with the one you select from the list of similar type sensor items.  The label and every other aspect of the sensor item will be left intact.  It's coming with the next beta update ;)

    Thanks a ton for always responding so quickly and bringing these awesome improvements to the community. Can’t wait to try out the next beta!
    Now all that’s left is that legendary update everyone’s dreaming of: the glorious animated GIF! 😂🔥

    • Thanks 1
  21. 58 minutes ago, Surjeet said:

     

       😍 First of all, Heartiest Thank you for checking and working on this new feature request 😍

     

    Behaviour may vary depending on the user’s specific use case.

    However, if labels could automatically update (when used) while maintaining the same font style, that would be a fantastic improvement - both visually appealing and time-saving!

    We all are curious and excited to know regarding this:

    One of the most important aspects for users is whether the Minimum and Maximum values remain unchanged when a sensor item is replaced.

    For example, in a setup using 100 states (with 8 sensors), each sensor typically has unique Min/Max values. If these values persist and remain intact after replacing a sensor, it would be a huge benefit - eliminating the need to manually re-enter values. This makes the system far more user-friendly, especially for users who might not be familiar with the exact Min/Max configurations.

    Absolutely, I’m fully on board!

    For setups using 100 states across 8 sensors, this would definitely make a huge difference.

    Keeping the minimum and maximum values preserved when switching sensors isn’t just convenient — it’s essential for anyone managing complex layouts. It saves time, reduces errors, and makes the whole process much smoother. 👊

    • Like 1
  22. 16 hours ago, Fiery said:

    The scaling feature only scales SensorPanel items but not images.  So the image files (BMP, PNG, JPG) you use for either regular images or as custom gauge states will not be altered during the scaling process.  The only aspect about images that is altered is the resizing dimensions.  But your layout doesn't seem to use resizing for images.

    In order to make sure your panel is suitable for various DPI settings, you need to use high-resolution images for still images and custom gauge states and use the resizing facility.  As an example: if you need a 250x300 pixel sized custom gauge, try to use a set of gauge state images sized at 200% of that, so 500x600 pixels each.  Then, after placing the images on your layout, use the Resize parameter for the gauge and enter 250x300 there.

    If you'd like to see an example of how resizing high-resolution images work for both still images and custom gauges, check the file called sensorpanel_default.spzip in the AIDA64 installation folder.

    I’ve been following along, but it’s very confusing to me. @Fiery @BHSY, @Surjeet, I opened the sensorpanel_default.spzip file and the images are sized at 896x896 pixels with a resolution of 288. To ensure all scales work correctly without errors, do we need to create the gauges at this resolution?

×
×
  • Create New...