Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
HWiNFO32 and HWiNFO64 v5.21-2805 Beta released
#1
HWiNFO32/64 v5.21-2805 Beta available.
   
Changes:
  • Fixed a possible hang in sensors when system is using multiple page files.
  • Added hotkeys to disable/hide sensors.
Reply
#2
Question 
Hi Martin,

I am confused!  Huh  I don't understand why some developers don't seem to believe why everything should not be Right Clickable?

I just went to right click in your "About" because I didn't want to open the link in my "Default Browser" BUT I couldn't Right Click for a context menu  Huh

My foible  is, I just don't like to type anymore than I absolutely have to O.o  Tongue 


Best Regards,  Big Grin

Crysta
Reply
#3
Martin, I'm unsure if that's something you know about but as far as I can tell this issue popped up recently, it didn't happen before.

Check this gif/webm http://gfycat.com/LimitedShowyGrouper (ignore the terrible quality, idk what happened there)
In either case, see "PSU" it keeps disappearing, prob because it can't read the value? I don't have corsair link running and its the same PSU as before AX860i..
I tried playing with refresh values, didn't help.
Any idea if this is a problem on my side?

Note this is happening in rivatuner overlay AND in the Hwinfo UI.
[Image: TWzfm1D.png]
Reply
#4
Yes, this must be because the Corsair Link protocol is quite unstable and sometimes HWiNFO is not able to read correct values.
Can you please attach a HWiNFO Debug File capturing such situation ?
Reply
#5
(02-17-2016, 04:17 PM)Martin Wrote: Yes, this must be because the Corsair Link protocol is quite unstable and sometimes HWiNFO is not able to read correct values.
Can you please attach a HWiNFO Debug File capturing such situation ?

I've sent you a PM with a link to the debug file.
[Image: TWzfm1D.png]
Reply
#6
Thank you. I can see that indeed the protocol reading data from PSU is very erratic.
I'll change it so that the next build of HWiNFO when unable to read some value will show the previous valid instead of not showing it. This will avoid the flickering in RTSS, however the user won't know if the value showing there is valid, or a previous value since HWiNFO wasn't able to retrieve the actual one.
In HWiNFO sensors screen, such a value will be shown in grey color to denote that it's not the actual one.
Reply
#7
(02-17-2016, 06:00 PM)Martin Wrote: Thank you. I can see that indeed the protocol reading data from PSU is very erratic.
I'll change it so that the next build of HWiNFO when unable to read some value will show the previous valid instead of not showing it. This will avoid the flickering in RTSS, however the user won't know if the value showing there is valid, or a previous value since HWiNFO wasn't able to retrieve the actual one.
In HWiNFO sensors screen, such a value will be shown in grey color to denote that it's not the actual one.

Yep I also had the idea of making it show the previous value. To avoid issues, that could be disabled with a toggle-checkbox on rightclick on a specific sensor I thought.

In either case, thanks a lot Smile!
[Image: TWzfm1D.png]
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)