GTMoraes
Member
Hello,
I'm using HWiNFO to control my CPU speed when working and gaming. When I'm gaming, I like to lock the CPU speed to a certain frequency in order to avoid overheating on long gaming sessions, and when I'm working, I like to have maximum performance when it's needed.
I use ThrottleStop for this, and keybinds to change profiles. I, then, use AutoHotKey to execute the hotkeys. I've set two alarms in HWiNFO to loosely detect what am I doing at the moment: If any FPS is registered (which RTSS registers when a game is opened), it changes to Game Profile. When the the GPU temperature is 0°C (because Optimus disabled it), it changes to Normal Profile.
The latter is not a very good method, but I used because I was out of options
Currently, ThrottleStop and keybinds work great, and HWiNFO's new "Trigger Only Once" alarm toggle does a great job triggering the keybinds automatically with AutoHotKey-made .exe scripts for these scenarios
Many thanks for adding this toggle, by the way
However, the temperature reading isn't a very reliable method to detect whether I'm Gaming or Working.
But I found out that I can pass the current sensor reading as an argument, so I made a quick script that chooses the correct profile given the FPS. Below 5 FPS, Normal Profile. Above that, Game Profile.
So the HWiNFO sensor alert is set like this:
RTSS FPS Sensor
Enable Alerting:
[X] If Value < 5
[X] If Value >= 32
[X] Run a program [script.exe %v]
The script parses the argument correctly, but when Trigger Only Once is checked, HWiNFO doesn't run the "If Value >=" alarm correctly, only "If Value <", for some reason
I know when the profile is switched because I've set the script to play a tune whenever it happens
Example 1:
Trigger Only Once is checked
- FPS reading is at 0FPS
- HWiNFO has triggered the "If Value < 5" alarm for this sensor (long ago)
- I open a game
- FPS reading is at 120FPS
- HWiNFO doesn't trigger the "If Value >= 32" alarm for this sensor
- "Game Profile" Tune doesn't play
- I close the game
- FPS reading is now back at 0
- HWiNFO triggers the "If Value < 5" alarm.
- "Normal Profile" Tune plays
Example 2:
Trigger Only Once is NOT checked
- FPS reading is at 0FPS
- HWiNFO keeps triggering the alarm because the "If Value < 5" is true for this sensor (long ago)
- Sporadically the "Normal Profile" tune plays
- I open a game
- FPS reading is now at 120FPS
- Now the "Game Profile" tune plays sporadically, so the "If Value >= 32" is being correctly interpreted
- I close the game
- FPS Reading returns to 0
- The "Normal Profile" tune plays now
I hope I wasn't too confusing in my explanation, I can't think of a better way to explain it.
Basically HWiNFO doesn't seem to trigger the "If Value >=" alarm when Trigger Only Once is set, and the sensor value was already below the "If Value <" alarm.
Or maybe I'm doing something wrong. If so, please tell me where I did wrong
Thanks
I'm using HWiNFO to control my CPU speed when working and gaming. When I'm gaming, I like to lock the CPU speed to a certain frequency in order to avoid overheating on long gaming sessions, and when I'm working, I like to have maximum performance when it's needed.
I use ThrottleStop for this, and keybinds to change profiles. I, then, use AutoHotKey to execute the hotkeys. I've set two alarms in HWiNFO to loosely detect what am I doing at the moment: If any FPS is registered (which RTSS registers when a game is opened), it changes to Game Profile. When the the GPU temperature is 0°C (because Optimus disabled it), it changes to Normal Profile.
The latter is not a very good method, but I used because I was out of options
Currently, ThrottleStop and keybinds work great, and HWiNFO's new "Trigger Only Once" alarm toggle does a great job triggering the keybinds automatically with AutoHotKey-made .exe scripts for these scenarios
Many thanks for adding this toggle, by the way
However, the temperature reading isn't a very reliable method to detect whether I'm Gaming or Working.
But I found out that I can pass the current sensor reading as an argument, so I made a quick script that chooses the correct profile given the FPS. Below 5 FPS, Normal Profile. Above that, Game Profile.
So the HWiNFO sensor alert is set like this:
RTSS FPS Sensor
Enable Alerting:
[X] If Value < 5
[X] If Value >= 32
[X] Run a program [script.exe %v]
The script parses the argument correctly, but when Trigger Only Once is checked, HWiNFO doesn't run the "If Value >=" alarm correctly, only "If Value <", for some reason
I know when the profile is switched because I've set the script to play a tune whenever it happens
Example 1:
Trigger Only Once is checked
- FPS reading is at 0FPS
- HWiNFO has triggered the "If Value < 5" alarm for this sensor (long ago)
- I open a game
- FPS reading is at 120FPS
- HWiNFO doesn't trigger the "If Value >= 32" alarm for this sensor
- "Game Profile" Tune doesn't play
- I close the game
- FPS reading is now back at 0
- HWiNFO triggers the "If Value < 5" alarm.
- "Normal Profile" Tune plays
Example 2:
Trigger Only Once is NOT checked
- FPS reading is at 0FPS
- HWiNFO keeps triggering the alarm because the "If Value < 5" is true for this sensor (long ago)
- Sporadically the "Normal Profile" tune plays
- I open a game
- FPS reading is now at 120FPS
- Now the "Game Profile" tune plays sporadically, so the "If Value >= 32" is being correctly interpreted
- I close the game
- FPS Reading returns to 0
- The "Normal Profile" tune plays now
I hope I wasn't too confusing in my explanation, I can't think of a better way to explain it.
Basically HWiNFO doesn't seem to trigger the "If Value >=" alarm when Trigger Only Once is set, and the sensor value was already below the "If Value <" alarm.
Or maybe I'm doing something wrong. If so, please tell me where I did wrong
Thanks