Rem0o

@kristofferR

@Hairless Monkey Boy has part of the solution. You also need to set slow ramp up/ramp down% on your controls. You can also set a high hysteresis and response time on your graph/curve to avoid detecting small spikes all together.

Hi, FanControl dev here, Just saw this. Indeed the name and overall UI seem similar. Some recognizable names in the industry have contacted me in the last year, but CoolerMaster was not one of them. Now about the software looking like FanControl, I'm not upset or mad at it. As people said, I didn't create that UI design, just type in "material design dashboard" on google and you'll see. They just figured out what a good/simple modern layout looks like. Side note, I *do* have a monetization scheme for FanControl, it's called a donationware. Since Jay'z video, that amount is non-negligible, but money was never the priority here, it just gives me extra flexibility and motivation to keep on going. What makes FanControl, well FanControl (IMO, I'm biased), is its feature set and overall premise: * free * the hardware support aspect is open-source https://github.com/LibreHardwareMonitor/LibreHardwareMonitor * plugins: the selection getting better over the year (https://github.com/Rem0o/FanControl.Releases#plugins) * minimal design/footprint 100 mb of RAM with UI on, drops to 15-30 with UI off. Next to 0% cpu usage. * the "modular" aspect of constructing your config from small building blocks/functions into a complex logic pattern Right now they seem to be aiming it as a "center hub" for your lightning, cooling, monitoring and so on, kinda like every manufacturer's software right now, so nothing new here. So you can probably forget about the small footprint. I'd be curious about the cooling feature set, and what kind of hardware support (motherboard fan control, especially) they offer beyond the typical monitoring and their own stuff. Also curious if they will try to make it expandable to import new sensors/hardware into it, and how that plays out. I'll keep a curious eye open. That custom image/background look cute though, might be "inspired" by it

Not intended! I always have slow ramp up on all my test configs, and I missed the ramp up on graphs and linear fan curves for the first cycle when deserializing a config. Covered the case with automated tests, shouldn't happen in the future.

Ding ding ding, we have a winner.

Could you add code in the plugin to identify which one goes missing when UpdateValues returns false? Otherwise I guess I will do that anyway as it will make it easier to track down issues.

Could you identify which sensor went missing ?

@Gamer Guy Nvidia driver has a hard limit of 30% that I can't go below for some newer cards. Can't do anything about it until some advancement in the driver is made public. @RejZoRI'm aware, you are most likely in light mode in W10. Tried to sync with your windows setting, but it's a mess with all possible setups. Next version will provide an override to choose your own color. @Alvin853try and add /high to your scheduled task. Task Scheduler => FanControl => Action /C start /B /high FanControl.exe

V114 fixes the issue. Sorry about the inconvenient. BTW I update the plugin also to use the gadget stuff instead of the shared memory, so no more 12 hour limit and you can use the latest HWInfo versions.

Ask the manufacturers.

There is no API hook yet to manually tell these newer cards to go 0 rpm. Their default behavior (built-in) does it, but you can't "ask" for it from the API level.

You have to keep the software running all the time.

Restarting your computer or putting it to sleep will reset everything.

@CASS2021 your memory map file from HWInfo is not active.

It's always at reboot where things go wrong.