Open AndreaBaccolini opened 6 months ago
Is there a reason why you wouldn't create a curve based on temperature instead? That's what the program is meant for.
Is there a reason why you wouldn't create a curve based on temperature instead? That's what the program is meant for.
You didn't understand. The fans start when I open a program and follow the curves I set. So a certain program activates a certain control of one or more fans.
I get your feature request, it is not the first time I get it. My question is to you, is why. If your program generates heat, your fan curves will kick in. If your program doesn't generate heat, fan curves won't kick in.
So why do you need to have an other feature that forces the fan on or off based on a process starting ?
Not the fan but the fan control. I mean I for example turn on the GPU fan control only with games and 3D programs like Spline and Blender otherwise I just need the default control. So I don't have to open apps every time and turn the control on. Because I have noticed at least in my GPU that the fan turns off and on many times if I use these apps with native control. That's why I use the one from Fan control
You will find me annoying, but why don't you just leave it on? That's the whole point.
For eg:
This is mine. Under load (over 50) I get the the fan spinning, otherwise it sits at 0 RPM.
Because I have noticed at least in my GPU that the fan turns off and on many times if I use these apps with native control.
Which GPU you got? We can probably handle that properly. Also show what settings you got in FanControl, ideally screenshots.
I had tried setting with yours but it didn't work for me. I mainly play Guild wars 2 and if I set like yours I would have the fans going off and on all the time so I have to set them to go to idle all the time and then increase with the temperature.
Have you tried a "trigger" instead of a graph? Set the idle temp low enough so that while in game it never reaches it, and you'll have the desired behavior.
Yes. But the problem remains. Unfortunately in old games I think it's easy for that to happen. That's why it would be useful in these cases that the fan control could be operated on a game-by-game basis. So you could also make ad hoc curves by game/program.
I'd like to add, that there are situations, when a fan in a system should target a device, that doesn't provide any kind of temperature readings (and does also not notably raise common temperatures, when in use); I do, for example, use a bunch of DSP cards, that I'd like to provide some extra airflow once they're get going.
My workaround is to use the File "sensor" along with a scheduled task, which traces application start/stop events, which then writes a particular value into that file (using a PowerShell script)... together with some "sensor math" it allows me to accomplish that task fully automated.
Another reason might simply be, that you'd just like to have more aggressive cooling under certain situations, and (of course) want to automate that...
I'm not really understanding the need for this, either, except for t3t3's point, but perhaps profiles with the ability to switch them via the tray icon and possible hotkeys would be a solution.
Hi, I would like the GPU fans (or fan of my choice) to run by themselves when I start a game (or program) without having to run them first each time. Thanks