SensorPanel loads on the wrong monitor

[sensorblue]

Hi all, same issue here.

The beta linked by @Fiery finally fixes the broken Sensor Panel UI when using multiple monitors with different scaling factors — thank you! However, it still doesn't fix the positioning problem. After every Windows restart, the Sensor Panel appears on a different monitor.

I haven’t been able to identify any consistent pattern, even after experimenting with various settings like Pin to screen, Fix console size, and others.

(By the way, what exactly is the “console” in this context? Does it refer to the Sensor Panel itself?)

[Frk]

It's absolutely baffling that the positioning of the SensorPanel is still an issue. The SensorPanel is literally the only selling point of this piece of software; all other features can be achieved with free or open-source tools. Anyway, I 'fixed' it by creating a PowerShell script that runs on boot and moves the SensorPanel process to the correct display based on the resolution of the target display. This does require the display running your SensorPanel to have a unique resolution compared to your other monitors, but that's often the case, as these are usually lower-resolution screens. Feel free to try it out yourself, I've put the code on GitHub: https://github.com/Freekers/AIDA64-SensorPanel-Mover

P.S. For non-commercial use only. Please don't incorporate my code into AIDA64.

[VintageOffice]

Sorry to say there's still an issue with the sensor panel positioning. At first it looked all right, but I've had several occasions where the sensor panel was shown in the main display. All displays started before Windows logon. The Wallpaper Engine app (available on Steam) always shows the correct background on the correct display, never had an issue with that.

 

Also would like to note that if the enumeration of the network adapter changes, the wrong stats are shown in the sensor panels. Please use ID's (which are unique) instead of the values of enumeration (which are subject to change).