Sensorpanel Manager: Enhanced Image Management and Gauge Assignment Calculation - (NEW Feature Request)

[Surjeet]

Hi AIDA Developers and Dear @Fiery,

We appreciate the recent addition of the ability to add multiple images for States 0-15 while using a Custom Gauge, with AIDA seamlessly sorting them. This feature has proven to be extremely beneficial in streamlining the user experience.

Building upon this functionality, we would like to request the following enhancement:

Feature Request: Allow users to add any number of images to the Custom Gauges, and for AIDA to automatically calculate the total count of images. Based on this count, AIDA should be able to dynamically calculate and adjust the corresponding Step or Gauge percentage assignment to the image added.

This improvement would provide greater flexibility and accuracy, ensuring that users can seamlessly manage a variable number of images while maintaining consistent and reliable performance in their sensor panel setups.

We will not be required to use multiple 8 Layers for 100 states and just simply need to fill Min/Max value and AIDA algorithm will work as per the following examples!!

For example:

If I select 16 images, the rule is:

Images Used	Maximum Number	Sensor valuue from AIDA	Step
0	15 (Or 16-1)	<=	0%
1		<=	7%
2		<=	13%
3		<=	20%
4		<=	27%
5		<=	33%
6		<=	40%
7		<=	47%
8		<=	53%
9		<=	60%
10		<=	67%
11		<=	73%
12		<=	80%
13		<=	87%
14		<=	93%
15		<=	100%

If I select 31 images:

Images Used	Maximum Number	Sensor valuue from AIDA	Step
0	30 (Or 31-1)	<=	0%
1		<=	3%
2		<=	7%
3		<=	10%
4		<=	13%
5		<=	17%
6		<=	20%
7		<=	23%
8		<=	27%
9		<=	30%
10		<=	33%
11		<=	37%
12		<=	40%
13		<=	43%
14		<=	47%
15		<=	50%
16		<=	53%
17		<=	57%
18		<=	60%
19		<=	63%
20		<=	67%
21		<=	70%
22		<=	73%
23		<=	77%
24		<=	80%
25		<=	83%
26		<=	87%
27		<=	90%
28		<=	93%
29		<=	97%
30		<=	100%

If 101 images are selected:
 

Images Used	Maximum Number	Sensor valuue from AIDA	Step
0	100 (101-1)	<=	0%
1		<=	1%
2		<=	2%
3		<=	3%
4		<=	4%
5		<=	5%
6		<=	6%
7		<=	7%
8		<=	8%
9		<=	9%
10		<=	10%
11		<=	11%
12		<=	12%
13		<=	13%
14		<=	14%
15		<=	15%
16		<=	16%
17		<=	17%
18		<=	18%
19		<=	19%
20		<=	20%
21		<=	21%
22		<=	22%
23		<=	23%
24		<=	24%
25		<=	25%
26		<=	26%
27		<=	27%
28		<=	28%
29		<=	29%
30		<=	30%
31		<=	31%
32		<=	32%
33		<=	33%
34		<=	34%
35		<=	35%
36		<=	36%
37		<=	37%
38		<=	38%
39		<=	39%
40		<=	40%
41		<=	41%
42		<=	42%
43		<=	43%
44		<=	44%
45		<=	45%
46		<=	46%
47		<=	47%
48		<=	48%
49		<=	49%
50		<=	50%
51		<=	51%
52		<=	52%
53		<=	53%
54		<=	54%
55		<=	55%
56		<=	56%
57		<=	57%
58		<=	58%
59		<=	59%
60		<=	60%
61		<=	61%
62		<=	62%
63		<=	63%
64		<=	64%
65		<=	65%
66		<=	66%
67		<=	67%
68		<=	68%
69		<=	69%
70		<=	70%
71		<=	71%
72		<=	72%
73		<=	73%
74		<=	74%
75		<=	75%
76		<=	76%
77		<=	77%
78		<=	78%
79		<=	79%
80		<=	80%
81		<=	81%
82		<=	82%
83		<=	83%
84		<=	84%
85		<=	85%
86		<=	86%
87		<=	87%
88		<=	88%
89		<=	89%
90		<=	90%
91		<=	91%
92		<=	92%
93		<=	93%
94		<=	94%
95		<=	95%
96		<=	96%
97		<=	97%
98		<=	98%
99		<=	99%
100		<=	100%

 

We believe this feature would significantly enhance user experience by offering more control and adaptability to different panel configurations.

Thank you for considering this request. We look forward to your feedback and any further possibilities for improvement.

[Surjeet]

@Fiery This message was lost somewhere and never addressed. Please let us know if this is possible and can be used?

@BHSY @JariKoi @COSTAJUNIOR What do you think regarding this request as it will help a LOT while making Custom gauges using any images.

[JariKoi]

This would be a truly excellent improvement and would certainly make it easier to create these sensors. I support it!👍

[BHSY]

Yes. I like this idea and I support it too. If we can have more options to select different types of custom gauges, as shown in the screenshot below, we don't have to create 8 sensors for a 101-image for CPU/GPU temperature, utilization or other sensors like voltage, wattage and fans. However, when using the States button to import 0-101 images (the 3 dots button) it will be too long to fit on our screen, and it might need to be broken down into 4 portions.

As for causing laggy, slowing down the system and files takes too long to save: If we create a dial gauge, say, just a needle image with 101 images (0%-100%) and there are 4 or more custom dial gauges, it wouldn't cause the system to lag or takes too long to save the file. Unless the needle image included the dial base/body image, which causes the image size to become large, then it might cause lagging in the AIDA64 program and a longer time to save the file.

The newly added 'Change Source' is a great option so if more selection for custom types of gauges can be implemented, the 'Change Source' feature can be a great asset too.

If 0%-100% is not possible, how about 0%-50%? 

We knew this would be a big overhaul but we hope that it can be implemented and this will be a great addition to the next-generation AIDA64 feature.😉 

Thank you!

[Surjeet]

19 hours ago, JariKoi said:

This would be a truly excellent improvement and would certainly make it easier to create these sensors. I support it!👍

Thank you!

7 hours ago, BHSY said:

Yes. I like this idea and I support it too. If we can have more options to select different types of custom gauges, as shown in the screenshot below, we don't have to create 8 sensors for a 101-image for CPU/GPU temperature, utilization or other sensors like voltage, wattage and fans. However, when using the States button to import 0-101 images (the 3 dots button) it will be too long to fit on our screen, and it might need to be broken down into 4 portions.

As for causing laggy, slowing down the system and files takes too long to save: If we create a dial gauge, say, just a needle image with 101 images (0%-100%) and there are 4 or more custom dial gauges, it wouldn't cause the system to lag or takes too long to save the file. Unless the needle image included the dial base/body image, which causes the image size to become large, then it might cause lagging in the AIDA64 program and a longer time to save the file.

The newly added 'Change Source' is a great option so if more selection for custom types of gauges can be implemented, the 'Change Source' feature can be a great asset too.

If 0%-100% is not possible, how about 0%-50%? 

We knew this would be a big overhaul but we hope that it can be implemented and this will be a great addition to the next-generation AIDA64 feature.😉 

Thank you!

Thank you and I really liked the idea I was thinking on dynamic lines as I using this formula for the examples shared above, AIDA can easily calculate Step% and respective Gauge Flow:  

Images Used Divided by Maximum Number  = Step %

Lets hope that this can be implemented and is do-able thing. Lets wait for @Fiery to see if this feature is something that can be considered and worth implementing!!

 

[Fiery]

On 6/14/2025 at 4:58 PM, Surjeet said:

@Fiery This message was lost somewhere and never addressed. Please let us know if this is possible and can be used?

@BHSY @JariKoi @COSTAJUNIOR What do you think regarding this request as it will help a LOT while making Custom gauges using any images.

Before moving forward with this request, it would be crucial to clarify whether you need more gauges states only, or you'd want to also have full flexibility on the number of states?  In other words, if we pick a number of states for the expanded custom gauge variant, let's say 50 or 101 states specifically, would it suit all your needs, or you'd have special layouts or special gauges where neither 16, 50 or 101 states would be ideal?

[BHSY]

20 minutes ago, Fiery said:

Before moving forward with this request, it would be crucial to clarify whether you need more gauges states only, or you'd want to also have full flexibility on the number of states?  In other words, if we pick a number of states for the expanded custom gauge variant, let's say 50 or 101 states specifically, would it suit all your needs, or you'd have special layouts or special gauges where neither 16, 50 or 101 states would be ideal?

Regarding the full flexibility on the number of states. Do you mean the option will show, for example, 15, 30, 100, as shown in the screenshot below? If it is, then my answer is YES! I prefer the original 15 states to remain so our old panel gauges wouldn't be affected. The additional numbers of states that I want are 30, 50 and 100.

Thank you.

[Surjeet]

5 hours ago, Fiery said:

Before moving forward with this request, it would be crucial to clarify whether you need more gauges states only, or you'd want to also have full flexibility on the number of states?  In other words, if we pick a number of states for the expanded custom gauge variant, let's say 50 or 101 states specifically, would it suit all your needs, or you'd have special layouts or special gauges where neither 16, 50 or 101 states would be ideal?

Thank you so much for getting back to us - we really appreciate the time you're taking to evaluate this request.

If we understand the question correctly, the intent behind the feature request:

1. Full Flexibility (if feasible):
Ideally, we’re hoping for the ability to add any number of images to a custom gauge (e.g. 0-15, 0-30, 0-50, 0-60, 0-100, etc.), with AIDA automatically calculating the step or percentage mapping based on the image count.

2. Predefined Options (if full flexibility is too resource-intensive):
If implementing dynamic flexibility is too time-consuming or resource-heavy, then predefined options like 0-15, 0-30, 0-50, 0-60, and 0-100 states would still be very helpful. We believe this set would likely cover most common use cases.

The overall goal is to eliminate the need for workarounds like multiple 8-layer stacks (especially for high-state gauges like 101 images) and to make the setup process more seamless and user-friendly.

We truly believe this enhancement would significantly improve the user experience and provide more creative freedom for building custom panels.

Thank you again for considering this - please don’t hesitate to let us know if there’s anything more we can provide from our side or if there are any roadblocks with the request (and something can be tweaked easily the other way round).

[COSTAJUNIOR]

I agree with @BHSY. Keeping the original 15 states intact is essential so it doesn’t affect the sensors that have already been created.
But it would be amazing to have new options like 30, 50, and 101 states — that would open up a huge range for creating even more personalized and detailed sensors. It would be a major step forward in customization!

[Fiery]

On 6/16/2025 at 5:45 PM, COSTAJUNIOR said:

I agree with @BHSY. Keeping the original 15 states intact is essential so it doesn’t affect the sensors that have already been created.
But it would be amazing to have new options like 30, 50, and 101 states — that would open up a huge range for creating even more personalized and detailed sensors. It would be a major step forward in customization!

@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.

[Surjeet]

20 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.

Oh Man!

Wow, this is incredible!

I’m genuinely speechless 🤐 - what you’ve done here is absolutely amazing.
I just tested it with 30 states with Volume, and it’s working flawlessly!

You’re a genius, GOD Man 😇 - truly impressive work!

I will check it with more states and also will wait for reply from our AMAZING creators:

 @BHSY, @JariKoi and @COSTAJUNIOR

 

[Fiery]

12 minutes ago, Surjeet said:

Oh Man!

Wow, this is incredible!

I’m genuinely speechless 🤐 - what you’ve done here is absolutely amazing.
I just tested it with 30 states with Volume, and it’s working flawlessly!

You’re a genius, GOD Man 😇 - truly impressive work!

I will check it with more states and also will wait for reply from our AMAZING creators:

 @BHSY, @JariKoi and @COSTAJUNIOR

Thank you for your feedback I hope the new interface is intuitive or at least not too confusing

[COSTAJUNIOR]

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?

[JariKoi]

I updated and will test this when I get the chance.🙇‍♂️ Now that I'm on vacation, I'm taking it easy.🍻 I'll shout out if I notice any issues, but from what I've heard, it went excellently.💪🔥 Thank you for listening to the users and developing the program.

[Fiery]

1 hour ago, COSTAJUNIOR said:

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?

I appreciate your feedback and kind words.  The Change Source and the expanded gauge states are two independent features, they will continue to co-exist in AIDA64.

Forgot to mention: the new 101-state gauge is a new sensor item sub-type that is only supported by the next-generation of AIDA64 right now.  We will soon roll out a last stable update to the old AIDA64 generation, version 7.70.  If you wanna use the new 101-state gauges on your SensorPanel layout and share your layout with other AIDA64 users, make sure to emphasize the fact that due to the new gauges the layouts are only compatible with AIDA64 v7.70 and later versions.

[BHSY]

21 hours 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.

I-AM-GOING-CRAZY.....!!! 🤪YOU DID IT!👍 I tested it and it works marvelously. I used only one sensor instead of eight, and I don't even need to use a blank image. The Change Source is still a great additional feature; I don't have to click modify to change the sensor unless I need to change the value.👍

Thank you @Fiery for making this feature possible. YOU THE MAN!👏

 

I have two things I would like to inquire about.

1st inquiry: When the images were added using the 'Custom (n states)', we can't view the latest image file unless we manually scroll down. Is it possible for the scroll bar to scroll down automatically when a new image file is added?

 

2nd Inquiry: When I convert the existing Custom (16 states) to the 'custom (n states), it accepts image filenames without the  "-N.png", and still works. I tried to add an image filename, for example, led_blank.png, but it won't accept it. Is it possible for the custom (n states) to accept an image filename as text instead of -N.png?

The screenshots below show a CPU temperature sensor gauge used as a blinking light to alert the user that the CPU temperature has reached a minimum of 75 degrees. With the new 'custom (n states)', I can create a more accurate temperature alert but I have to create a 0-100 image that consists of a blank and light image. If the new custom gauge can accept a filename without using the -N/NN/NNN.png, I only need to use 1 blank image (for states 0-74) and 1 blinking light image (for 75-100). If not possible, then I'll use the Custom (16 states) for a less accurate blinking light image.

I hope you understand what I have mentioned.

[Fiery]

24 minutes ago, BHSY said:

I-AM-GOING-CRAZY.....!!! 🤪YOU DID IT!👍 I tested it and it works marvelously. I used only one sensor instead of eight, and I don't even need to use a blank image. The Change Source is still a great additional feature; I don't have to click modify to change the sensor unless I need to change the value.👍

Thank you @Fiery for making this feature possible. YOU THE MAN!👏

I have two things I would like to inquire about.

1st inquiry: When the images were added using the 'Custom (n states)', we can't view the latest image file unless we manually scroll down. Is it possible for the scroll bar to scroll down automatically when a new image file is added?

2nd Inquiry: When I convert the existing Custom (16 states) to the 'custom (n states), it accepts image filenames without the  "-N.png", and still works. I tried to add an image filename, for example, led_blank.png, but it won't accept it. Is it possible for the custom (n states) to accept an image filename as text instead of -N.png?

The screenshots below show a CPU temperature sensor gauge used as a blinking light to alert the user that the CPU temperature has reached a minimum of 75 degrees. With the new 'custom (n states)', I can create a more accurate temperature alert but I have to create a 0-100 image that consists of a blank and light image. If the new custom gauge can accept a filename without using the -N/NN/NNN.png, I only need to use 1 blank image (for states 0-74) and 1 blinking light image (for 75-100). If not possible, then I'll use the Custom (16 states) for a less accurate blinking light image.

I hope you understand what I have mentioned.

Thank you for your feedback!

1st inquiry: When you add multiple images, do you want the last one in the list to be visible or the first one?

2nd inquiry: Why don't you simply use a range of 0 to 100 Celsius for your CPU temperature gauge and only 4 states with the new "Custom (n states)" gauge type? That way you could use 3 blank images for 0 to 75 Celsius and a single blinking light image for 75-100 Celsius.

Maybe you've got slightly confused by me referring to the new feature as 101-state gauge.  It supports up to 101 states, but it can even be just 2 states, or 10 states, whatever number between 2 and 101.

We've designed the new 101-state gauge configuration window to go by the filename, so you cannot assign an image with whatever filename to any of the 101 slots anymore.  We figured because of the large number of states (and image files) it's best if you managed the state indexes straight in the filenames anyway, then you'd drop a bunch of image files in the list and AIDA64 will figure out how to assign them to each gauge state index automatically.

[BHSY]

7 minutes ago, Fiery said:

Thank you for your feedback!

1st inquiry: When you add multiple images, do you want the last one in the list to be visible or the first one?

2nd inquiry: Why don't you simply use a range of 0 to 100 Celsius for your CPU temperature gauge and only 4 states with the new "Custom (n states)" gauge type? That way you could use 3 blank images for 0 to 75 Celsius and a single blinking light image for 75-100 Celsius.

Thank you for your fast response.

1st inquiry:  I want the last one in the list to be visible. Thank you!🙏

2nd inquiry: Ok. I get where you're going. If I want the CPU temp to alert me when it reaches, for example, 80 degrees, I'll create a 5 states gauge. 4 blank images for 0 to 80 Celsius and a single blinking light image for 80-100 Celsius. Each state contains 20 Celsius. Brillant!

20 minutes ago, Fiery said:

We've designed the new 101-state gauge configuration window to go by the filename, so you cannot assign an image with whatever filename to any of the 101 slots anymore.  We figured because of the large number of states (and image files) it's best if you managed the state indexes straight in the filenames anyway, then you'd drop a bunch of image files in the list and AIDA64 will figure out how to assign them to each gauge state index automatically.

Understood, thank you for the explanation. The new "Custom (n states)" gauge is perfect for our needs.👍

[Fiery]

11 hours ago, BHSY said:

1st inquiry:  I want the last one in the list to be visible. Thank you!🙏

Done 🤘