Jump to content

Treadpool

Members
  • Posts

    35
  • Joined

Reputation

10 Good
  1. Upon setting it up in v4, it prompted me to authorize it by connecting to the Hub. Every other scene manager app I've used allows that by reading the scenes available on the Hue Hub. Is this something the team didn't want to do? I guess then you'd have to somehow match the other components (keyboard, mouse, memory, fan etc) to the Hue scene too. Overall I'm going to hold off on this upgrade and stay on v3. Even if it's because I don't feel like learning a completely new UI/UX. Took long enough to figure v3 out.
  2. The Hue integration is pretty useless. Seems to be only one way and forces rgb rainbow on everything at first. I can't even set a scene from the Hue Hub that I synced it to - why is that? I have a ton of scenes already created there.
  3. Yes. The "sz Ryzen Balanced V4" profile + the 1usmus bios settings + PBO on is perfect. All cores except one or two sleep on idle. I've kept iCue disabled though since it doesn't let cores sleep at all.
  4. Interesting - I just added that to my power plan arsenal and you are right. I'm consistently down at .95 while Discord and iCue are open. Sweet. It also doesn't seem to let any cores sleep though unless Discord is closed out - then one sleeps. Pretty cool - will see how it works out for a day or so. Thanks for sharing that!
  5. Noticed something else interesting. When I closed out Discord while iCue was running, my system properly set 4/8 cores to sleep and everything was perfect, voltages drop as they should. When I have Discord open with iCue, it keeps core voltage at 1.05-1.10 and only sleeps 2/8 cores. When I close iCue and Discord is running, behavior is perfect again and it sleeps 4/8 cores, voltages drop again. Guess they don't like each other? None of my other programs seem to impact anything: Chrome (11 tabs open), Rainmeter, Spotify, LGS, 1Password, MSI Afterburner.
  6. Well I was using Ryzen Balanced power profile and decided to try the 1usmus profile and disable PBO in bios (which I had enabled before) and it seems to let my voltage drop now. It now drops to about 1.05v with iCue enabled and about two cores sleep. When iCue is closed though, a couple more cores sleep and the idle voltage drops even more. I might take this balance and roll with it, assuming gaming performance doesn't take a hit either from this new setting or from iCue being activated again. Edit: I'm actually not sure if the 1usmus profile vs Ryzen balanced actually makes a difference. It's probably just from disabling PBO. Edit2: It 100% makes a difference to use 1usmus profile. Now I'm wondering if that's the key - and PBO on or off doesn't matter. Will test Edit3: TLDR; use 1usmus profile and problem solved with the voltages not settling and cores not sleeping with iCue enabled But note that with iCue disabled the core voltage drops further, bringing temps down further so there's still something funky going on.
  7. Thanks for the response. It just seems crazy to me to have my voltage constantly at 1.4v and not even be overclocking (yes I know it technically does overclock with small boosts via PBO). Also, with iCue enabled not only are my voltages higher, but temps are about 5-10c higher. I use a Corsair H115i AIO cooler too. I guess this is a trade-off. I need to figure out what's more important to me, but it drives me nuts that nothing else I use causes this behavior - and I use MSI Afterburner, Rainmeter with monitoring GPU. Also, C20 score went from 4715 to 4887. Not sure if this will result in better gaming performance, but interesting nonetheless.
  8. I also have a 3700x and noticed that iCue revs up the core voltage to around 1.38-1.4 consistently. I close it and voltage drops properly while idle. Removing iCue after many years of using it, which really sucks. Not getting to use the nice SDK / The Division 2 integration is really going to blow.
×
×
  • Create New...