Hello.

Recently, I have used a water-cooling system pumped by D5 Next and control my system under Aquasuite program plus BIOS. Before proceeding further, let me introduce relevant parts of my computer :


Monitor : 32GP850 (QHD 2560X1440), 32UN650 (UHD 3840X2160), no-brand (resolution 3840X1100)
CPU : 5950x
Graphics : Galax RTX 3090 HOF Limeted Edition
RAM : G.Skill Trident NEO 3800 CL14 XMP
Watercooling : TechN waterblock, MO-RA3 420 Pro, D5 Next, etc.
OS : Windows 10 Home Build 19044.1645
Aquasuite X.53


Added : I correct the exact resolution. Many thanks for comment.

While dual moniotrs are used, I need a 3rd small monitor having 3840X1100 resolution for the purpose of only monitoring sensors. I like HWiNFO64 program as a monitoring tool but try to use another tool, Aquasuite program. Although I am not expert at XML language, with the help of googling, I managed to make a layout for sensor-display panel, based on tools and function of Aquasuite. Here is the screenshot,


layout_sensors.jpg


However, I have a few things to be setteled down.



1. How can I correct resolutions of monitors?

In Windows 10, triple monitors are recognized perfectly and located by this configuration

monitors_windows.jpg,


where monitor 2 is QHD, monitor 1 UHD, and monitor 3 a panel for sensor-displays of resolution 3840X1100. But a mystery happen in Aquasuite, which realize the triple monitors as

monitors_aquasuite.jpg


So, I set up a coordinate for the window of the sensor-display layout at (2560+2560,0), neither (2560+3840+1,0) nor (2560+2560+1,0). Maybe, the grid option will affect the +1 offset to be ignored. This is fine. More than worse, Aquasuite actually realized the vertical resolution of the 3rd monitor as 720p, not 1100p ! Aquasuite told me that the 3rd monitor has a resolution 3840X1100 but, in reality, I can use only 720p. That is quite odd. How can I resolve this problem?


2. How can I optimize my layout?

Maybe, I may include too many sensor displays in the layout, which cause my system to slow down while the GPU only consumes just 160W. For example, while sensor-monitoring on, Youtube or Neflix have instaneous stoppings occasionaly and this cannot be happend when I played AAA games consuming over 400W. With only a Youtube window, GPU consume 130~150W. That is huge. Anyway, I can endure this point. The problem is that there exist mismatches reported by Aquasuite, HWiNFO64, and HOF AI Suite. The mismatched sensors are values of GPU core usage, GPU Memory Controller, GPU Memory Used, etc. About the sensors of the graphic card, the two program, HWiNFO and HOF AI Suite report the same values, although the additional monitoring panel for HOF Limeted Edition show the breaking graphs. But the values reported by Aquasuite are different. According to Aquasuite, my GPU is almost working of 1995MHz GPU clock and 9751 MHz Memory clock, etc. For reference, I do not overclock my graphics card, which, as a default, has maximum clocks 1860 MHz and 9751 MHz of GPU and GPU Memory, respectively. How can I fix this situation?

For comparison, I attach another screenshots of HWiNFO64 and HOF Ai Suite, reporting the states of turning on and off on-sensor-display panel by Aquasuite respectively (Of course, the sensor panel shows different values for GPU relevant.)

sensor_panel_off.jpg

sensor_panel_on.jpg



Thank you very much for your kind reading and useful comments in advance.

Thank you very much for valuable comments.

At first, your correction to the exact resolutions of QHD and UHD is right. So I corrected that information in the original writing. I appreciate it again.

Secondly, I checked resolutions of the three monitors accoding to your advice. I check the resolutions by using the site of calculating screen size and identifying again both Windows and NVIDIA setting pages. The result is that AQS report the wrong resolution.

May different connections of monitors to VGA ouput ports cause any problems? I think that it be rarely occurred at the present modern era. However, QHD and UHD are linked via DP and the small monitor via HDMI. Sometimes, the fast way to decide where a booting screen appear between monitors is to just use the leftmost DP port.

Here are a few screen shots of my whole monitors by using boxes of size 2560X1100 and 3840X1100. I hope that one can tell the difference by seeing the names of the uploaded files.

box_2560x1100_set.png


box_2560x1100.png


box_3840x1100.png


And I agree your opinion about y coordinate offset since using the Grid option of AQS.

Finally, I made up my mind to postpone using sensor display made by AQS. Instead, I will try another ways, for example, using only the pure HWiNFO program running either on the current small monitor although the text looks very small, or on an appropriate monitor which I may buy again. I love AQS graphical results but they consumes so much power in the "Desktop mode." T_T

1. Global Offset

During making my own sensor-display layout for a small panel, I aslo need a function to enable global offsets of various objects and wish that AQS be equipped with those functionalies.


2. Using AQS in Windows mode

Actually, I considered this method as an alternative, although there were a few unexpected things. Thanks Remayz for reminding me again to use AQS in Windows mode. At first, it is tedious for me to re-medy the existing layout to fit AQS in Windows mode on the small panel, but not difficult. The real problem, especially for me, is hidden behind. However, I'd like to check again how much AQS in the various modes impact the graphic performance of my computer. Usual usages like opening many web-browsers, watching Youtube or Neflix, etc looks fine, while AQS in Windows mode is running on my little panel. Nextly, I ran Diablo II Resurrected (D2R) and moitored sensors about graphic card by using HWiNFO, HOF AI Suite, and AQS. Qualitive observations seem to indicate that I may run games wilth AQS in Desktop mode. I did not measure FPS intentionally.


D2R.jpg


Now I ran Time Spy of 3DMark and also observed several things qualitively.

Time Spy.jpg


Up to this point, AQS running in Windows mode operates quite well, compared to HWiNFO. But there is a serious problem from the viewpoint of me. My graphic card has an additional LCD panel, which correspond to one of the discriminations to the other line-ups of Galax RTX 3090. The LCD panel shows the information from HOF AI Suite program via USB. During obsevation, the sensor panel showed insane fluctuations about GPU status. For example, my memory clock seemed to forget to go lower than 9,751 MHz.

• HOF AI Suite + HWiNFO => No problem
  
• HOF AI Suite + HWiNFO + AQS => HOF panel behaves madly.
  
• HWiNFO+AQS => Not perfect but I can endure.
  
• HOF AI Suite + AQS => Just imagine..
  

The real problem is that I can not give up the HOF sensor panel. So I will use AQS when D5 Next pump is needed to setting-up and decide to buy another portable monitor to use HWiNFO usually and dual monitor for my old laptop outside. That is my story.

Thank you very much for interesting posts. Those are good to me.

ps) I am sorry for not uploading the images of monitoring result because of the file size.

ps) I failed to create tables by only characters so uploaded screen shots.