Rem0o
-
Posts
431 -
Joined
-
Last visited
Content Type
Forums
Status Updates
Blogs
Events
Gallery
Downloads
Store Home
Everything posted by 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.
-
@wege_smalec AFAIK, NZXT stuff is supported. Make sure you got the controller section ticked "on" in the sensor settings.
-
@Sid Vicious @tks1991 @InterClaw Fan curves based on power consumption is a false good idea. Trust me. You think temps are erratic? Take a look at a power consumption graph. Also, a single core boost doesn't consume that much power, but results in really temps. There is no point in trying to "catch" those brief 1-2 seconds temperature spikes, as it takes that much time at least to ramp up your fans anyway, and maybe 3-4X that time for that speed increase to take effect on temperatures. If you find those spikes too high for your liking, increase your idle fan speeds. No other amount of fan tuning will fix it, you'll have to invest in a bigger cooler with a higher thermal mass. I've tuned a FanControl setup with a 3900x with a fairly underpowered cooler and was able to make a fairly decent FanControl config for it. Temps are indeed very erratic in their behavior depending on boost on these CPUs. Solution? A higher that I usually like minimum fan speed, combined with an average custom sensor with the CPU relevant sensors + time average custom sensor over 3-4 seconds. The following screenshot is an example I just made on an Intel computer to showcase what it looks like:
-
It does allow?
-
That's oddly specific and not natively covered, but there is a way to get that exact behavior. Create a graph fan curve next to the target fan curve. Set the ramp you want there. Like 0% at 69, whatever % you want at 70 deg, then 70% at 80 deg. Now create a mix fan curve, set it to max, and set both the graph and target in there. Use that mix curve. Voila.
-
Target Fan curve is exactly that.
-
Anybody would be interested in Commander Pro support? Some guy reverse-engineered the protocol, and it turns out it can be controlled via HID like plenty of other controllers. https://github.com/audiohacked/OpenCorsairLink/issues/70 I don't have a commander pro to test, but it seems like the most popular controller right now, so if enough people are interested, might be worth trying to get my hands on one and start testing.
-
HwInfo have an other way to share sensor values which seems to be more fool-proof with the Windows registry. It doesn't rely on shared memory, which requires HWInfo to start first and all that dance. https://docs.rainmeter.net/tips/hwinfo/ Made it a public issue here https://github.com/Rem0o/FanControl.HWInfo/issues/1, but nobody stepped up to raise a proper PR yet. EDIT: This guy started something https://github.com/ScHAmPi/FanControl.HWInfo
-
Weird. Looked at the PR here, https://github.com/LibreHardwareMonitor/LibreHardwareMonitor/pull/583/files, and the implementation is sketchy at best, seems to be copied over some other guys project, but there is no direct reference to any documentation on to why/how it works, as Nvidia NVApi docs is not up to date. It reads the 10th element of an array returned by a function that is being called with a seemingly random bit mask. It doesn't seem right. Some more investigation was done here, but no clear success. It kinda confirms though that this is undocumented territory, and people are just trying and experimenting in the dark. https://github.com/falahati/NvAPIWrapper/issues/45 It seems like not all cards have the same amount of sensors, and it seems like the memory-junction sensor is only on high-end cards with GDDR6X memory, like the RTX 3090. For eg, the previously mentioned 10 size array only has 2 values on my GTX 1060, [Core, Hotspot, 0, 0, 0, 0, 0, 0, 0, 0]. Both are being detected properly into FanControl. HWInfo devs must either have made a lot of tinkering and somehow found the formula in the API, or it's actually not a real "sensor" value, and it's a "best guess" estimate that is being shown in some cases. HWInfo is one of the only software AFAIK that has it with GPU-Z, so it's hard to know if the value displayed is actually correct, since there is no concrete evidence or documentation to confirm anything. TLDR: All *PUBLIC* development made to read these newer sensors on Nvidia cards is reverse-engineering, tinkering, and guesses, since documentation ain't available.
-
LHM now has mem junction/hotspot built-in, check it out in the settings menu, just untick the NVApiWrapper and make sure LHM GPU checkbox is on.
-
Look for the mix fan curve, it's exactly that.
