If the "Always On Top" option is enabled in sensor configuration, then also the Independent OSD window will be on top.
FEATURE HWiNFO OSD
- Thread starter Martin
- Start date
Firstly Thanks for this great software.
Secondly, I hope OSD overlay can always be used without running 3D graphics windows (e.g. games). Using the independent window looks not cool with the header of the window and is not good to locate it on the taskbar.
as seen on the screen shoot I use the tray icons to monitor my stuff. It would be great to use the OSD to show them always on and off the game and specify their location - on the left next to the widget and network is even greater and it's the best way to use this empty space in the taskbar.
note: as someone mentioned the overlay disappeared after some time playing the game.
Secondly, I hope OSD overlay can always be used without running 3D graphics windows (e.g. games). Using the independent window looks not cool with the header of the window and is not good to locate it on the taskbar.
as seen on the screen shoot I use the tray icons to monitor my stuff. It would be great to use the OSD to show them always on and off the game and specify their location - on the left next to the widget and network is even greater and it's the best way to use this empty space in the taskbar.
note: as someone mentioned the overlay disappeared after some time playing the game.
Attachments
I was playing around with the OSD today. I had it set to Independent Window mode and had 4 items enabled, 3 of which were from a Corsair H110i AIO cooler. The 4 items were:
Position 1 - H110i Pump RPM (Graph)
Position 2 - H110i Fan 1 RPM (Graph)
Position 3 - H110i Fan 2 RPM (Graph)
Position 4 - Core Temps (Asus Maximus X Hero (Z370) (Graph)
The 2 fan graphs seemed to be erratic - sometimes there, sometimes a flat line. I stepped out of the room for a minute. When I came back, the computer was totally locked up - no cursor, no mouse, no keyboard response. I had to reboot it. When it came back up, in OSD, only Core Temps was still there. The 3 Corsair H110i items were no longer selected in OSD. When I reselected them, the Text, Graph Line, Graph Fill colors, and opacity settings were all back to defaults. Core Temps settings were as I left them, including being in Position #4.
I don't know if the lock-up was caused by the HIWINFO OSD being enabled, or if it has anything to do with having OSD enabled for the Corsair H110i pump and fan, but the machine is normally very stable. I know monitoring Corsair devices can be problematic, but I have been running HWINFO (Pro License) on this computer for years, and it has been reliably reporting data from the Corsair H110i AIO and a Commander Pro. I disabled OSD for now but may try it again and see if it locks up when the Corsair H110i sensor data is enabled in OSD.
Position 1 - H110i Pump RPM (Graph)
Position 2 - H110i Fan 1 RPM (Graph)
Position 3 - H110i Fan 2 RPM (Graph)
Position 4 - Core Temps (Asus Maximus X Hero (Z370) (Graph)
The 2 fan graphs seemed to be erratic - sometimes there, sometimes a flat line. I stepped out of the room for a minute. When I came back, the computer was totally locked up - no cursor, no mouse, no keyboard response. I had to reboot it. When it came back up, in OSD, only Core Temps was still there. The 3 Corsair H110i items were no longer selected in OSD. When I reselected them, the Text, Graph Line, Graph Fill colors, and opacity settings were all back to defaults. Core Temps settings were as I left them, including being in Position #4.
I don't know if the lock-up was caused by the HIWINFO OSD being enabled, or if it has anything to do with having OSD enabled for the Corsair H110i pump and fan, but the machine is normally very stable. I know monitoring Corsair devices can be problematic, but I have been running HWINFO (Pro License) on this computer for years, and it has been reliably reporting data from the Corsair H110i AIO and a Commander Pro. I disabled OSD for now but may try it again and see if it locks up when the Corsair H110i sensor data is enabled in OSD.
Huh. Is an option for this planned? The fixed color isn't terrible, but I would much prefer dark grey or black, especially on an OLED display.
![T[]RK](https://gravatar.com/avatar/9c3dc6a3c52d033d37ede72f0d68738f5a007009692b5a97477b24c78bb2d5d3?s=96){kind=avatar}
T[]RK
Member
Look's like i can't do it. When i try to enter PID (3236) it simply don't allow me to do it. It return back to 0. I even pressed random number, it input 11111111111111111, but right after i relese it - it back to 0.
It also give me tonns of pop-up errros "Enter positive integer".
Thank you for this feature, I wanted Presentmon style graphs that I can add multiple Y axes to and led me to getting a pro license. Also many thanks for integrating the Asus ROG/Matrix 12vhpwr sensors, as I no longer need to keep gpu tweak installed.
One feature I would love is if text values in the overlay can dynamically change colour based on value, as we can do in the sensor window. Is this possible?
One feature I would love is if text values in the overlay can dynamically change colour based on value, as we can do in the sensor window. Is this possible?
Hi,
I purchased a Pro license yesterday to use the internal OSD feature, but I’m experiencing some issues:
The in-game overlay works correctly in some titles (e.g., Call of Duty: Modern Warfare 2), but not in others like Call of Duty: Black Ops 6 or Assassin’s Creed Shadows.
As a workaround, I tried manually entering the PID of Shadows. In that case, the GPU usage is displayed correctly, but the process name appears as "?" and the overlay itself does not show up in the game.
Interestingly, when I use the OSD as a separate window instead of embedding it in-game, everything works as expected.
I’ve tested with default settings and no third-party overlays running. Is this a known issue or are there specific compatibility steps I should follow for these titles?
Update:
After restarting Windows, the overlay now works in Assassin’s Creed Shadows as well. However, there’s still a problem: the first time I switch to the desktop using Alt+Tab and return to the game, the overlay disappears completely.
Even quitting and restarting the game doesn't bring it back. I also tried restarting HWiNFO, but that didn’t help either — the overlay remains missing until I reboot the entire system again.
PS. To be honest, it's a bit disappointing that the one feature I specifically upgraded to Pro for still feels this unreliable. I hope this can be improved in future updates.
Thanks in advance for your support!
Best regards,
I purchased a Pro license yesterday to use the internal OSD feature, but I’m experiencing some issues:
The in-game overlay works correctly in some titles (e.g., Call of Duty: Modern Warfare 2), but not in others like Call of Duty: Black Ops 6 or Assassin’s Creed Shadows.
As a workaround, I tried manually entering the PID of Shadows. In that case, the GPU usage is displayed correctly, but the process name appears as "?" and the overlay itself does not show up in the game.
Interestingly, when I use the OSD as a separate window instead of embedding it in-game, everything works as expected.
I’ve tested with default settings and no third-party overlays running. Is this a known issue or are there specific compatibility steps I should follow for these titles?
Update:
After restarting Windows, the overlay now works in Assassin’s Creed Shadows as well. However, there’s still a problem: the first time I switch to the desktop using Alt+Tab and return to the game, the overlay disappears completely.
Even quitting and restarting the game doesn't bring it back. I also tried restarting HWiNFO, but that didn’t help either — the overlay remains missing until I reboot the entire system again.
PS. To be honest, it's a bit disappointing that the one feature I specifically upgraded to Pro for still feels this unreliable. I hope this can be improved in future updates.
Thanks in advance for your support!
Best regards,
Attachments
Last edited:
I see you used a wrong PID - the correct one is 13588 but you entered 13558.
You're right — my apologies, I definitely need more sleep ;-)
But just to clarify: the issue also occurs when using automatic targeting. The PID is correct, the process name shows up as "?" and there’s still no visible overlay - In AC Shadows, the overlay works occasionally, but in COD Black Ops 6, it doesn't work at all, sometimes it takes 5-10 minutes in game and suddenly it shows up. If there’s anything I can do to help narrow down the issue or provide more detailed information, I’m happy to assist.
But just to clarify: the issue also occurs when using automatic targeting. The PID is correct, the process name shows up as "?" and there’s still no visible overlay - In AC Shadows, the overlay works occasionally, but in COD Black Ops 6, it doesn't work at all, sometimes it takes 5-10 minutes in game and suddenly it shows up. If there’s anything I can do to help narrow down the issue or provide more detailed information, I’m happy to assist.
