So the preview version does work for the cpu temp now but there are a ton of other issues IMO with the preview version. Loads in the middle of my main monitor on reboot. My HUE led strips turn off when cam loads on startup. Can not change interface colors at all except for dark mode which IMO is to dark. There is waaaay to many things going on with monitoring in the display window now. Why can’t we pick what is displayed for monitoring instead of you guys picking for us? Only shows 3 of my 4 sticks of memory. At this point I don’t care about my cpu temp in cams. I have afterburner that displays it now and HWINFO that has worked since day 1 of new Ryzen launch. I already got rid of my x62 last month and went with H115i Platinum because of this software. This is insane. Switching to Corsair was the the best thing I could have done. Temps went down on 3900x significantly oh and their software works.
Hello, thanks for the input. We are aware of this issue but it is not in our list of priorities to take care of yet. We hope to fix it in a future update, but there is no ETA right now. Sorry.
Placement issue still not fixed with 3.7.0!!!!!!
How close are you guys to fixing the placement issue? It still loads in the middle of my main screen EVERY TIME no matter where I place the CAM window!!!! Seems like should be an easy fix!!!
Sorry, what I meant was, please update to 3.6.5 and if your issue continues to occur, provide us with your program logs so we can verify why this is happening. Thank you.
UMMMM yeah same here. I have the Ryzen 1800x and the only issue I had with 3.6.3 was that the cam window would not load on my 2nd monitor instead would load in the middle of my main screen. NOW with 3.6.4 I still have the same issue as well as the cpu temp stuck and my cpu overclock is at 1998MHz not 3999MHZ. PLEASE FIX THIS! Why is all of the fixes seem to getting worse and breaking other things????
Thank you for informing us of this, we have informed the developers so they can fix it in a future update.Kory supported this idea ·
same issue here. I hope the hotfix on the 20th fixes this! VERY ANNOYING!!