Jump to content

The Mac

Members
  • Content Count

    88
  • Joined

  • Last visited

  • Days Won

    2

The Mac last won the day on July 16 2016

The Mac had the most liked content!

Community Reputation

2 Neutral

About The Mac

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. so im guessing no one has figured out which one to use yet? perhaps a description of the source of the 3 different sensors woulds be helpful...
  2. Which of the 3 CPU sensors is the one i should be watching for throttling (cpu, package or diode)? They all report different temps. None of them seem to match what ryzen master reports. Supposedly thats the one that throttles at 90 degrees. Ryzen 5800x....
  3. similar issue I have the 5800x. None of the 3 cpu temp sensors (cpu, package, or diode) match what ryzen master reports. since that is the temp that throttles the cpu at 90 degrees, its the one we need to monitor.
  4. looks like it reappeared in the new aug18 beta. now its called GPU PowerControl.
  5. R9-290 (SAPPHIRE R9-290 Vapor-X) Crimson 16.8.2
  6. Looks like the AMD Powertune sensor item has gone missing. Although now in Crimson, they call it Power Limit. No sensor for that either. Is it coming back?
  7. i see the latest beta has "improved support" what does that mean exactly? edit: looks like you guys fixed the static duty cycle issue. sweet. Thanx! This kind of support is why i gladly open my wallet every year to you guys...
  8. well, thats certainly good to hear. im guessing you solution involves the corsair driver abstraction layer passing the info rather than trying to read the sensor directly which would obviously only be useful for corsair products..
  9. understood. based on corsair's track record of fixing their own program, im not going to hold my breath. How hard can it be to expose an interface for an external program to passively read values? Their own damn software does it. They make outstanding hardware, but they need to hire some real software engineers, not that group of muppets they have coding for them currently. in the mean time, no monitoring for me.
  10. unfortunately, all setting the fan% in aida64 does is raise the rpm. its still locked in place and wont use the fan curves in CL. im not interested in a static RPM, i want the fan curves to increase and decrease the rpm as needed based on the coolant temp.
  11. ill try when i get home. but im trying to use the default or custom fan curves supplied by CL, not a dedicated duty cycle. After re-reading my post, i wanted to clarify. having the aida64 asetek monitor enabled is what disables fan control, not me disabling it to get the sensors to work. The sensors themself work fine.
  12. gotcha, i dont have a commander module, so i guess i can disable it. I am using both the latest Corsait link (4.2.3.41) and the latest aida64 beta (3908). The behavior persists. I cannot monitor the CL sensors in aida64 without completely disabling all automated and manual fan control within CL. perhaps i need to downgrade the version on one or both? Do you happen to know approx when the next version of CL is due? their forums are awful and rarely have any offical replies.
  13. confirmed, Asustek LC sensor support cause complete loss of fan control and disabling of all fan curves through consair link. closing corsair link does not return normal behavior. H80i. so, either no sensors, or no fan control not much of a choice there. if enabled, fan rpms drop to 780 and stays there, and coolant temp quickly rises over 45c (red zone) under load. what is the corsair link sensor support for if it doesn't do anything?
×
×
  • Create New...