![]() ![]() However, the key location with the most utility is the rear exhaust - either inside or outside the case. I think this will affect the Commander Core the same way, but the CUE Link Hub and it's connected devices appear to work normally when using CPU package temp.Īs for the temp probes, you can put them anywhere you want for informational purposes. I did not go through the rest of the variables, but it is near certain they will the same. No doubt there is an issue with the fan curve on the Commander Pro when the variable is CPU or GPU temp. Operating System: Microsoft Windows 11 Home (64-Bit) Here's the core of the build in case you need:ĪMD Ryzen 7 7800X3D (8-Core) 5.0 GHz TurboĪSUS ROG Strix X670E-E Gaming (Wi-Fi) (AMD X670 Chipset)Ħ4GB DDR5 6000MHz Kingston FURY Beast RGB Go figure, first week I'm already running into AMD only issues. Told my friends I was gonna give the AMD 7 7800X3D a go, I've been a Intel person since the 80's but the reviews and had some bad experiences with some way older AMD chips, but the stellar reviews on the chip convinced me otherwise. Regardless, you're right though, seems after a update this started happening and seems from other posts to be only affecting AMD users go figure lol. Why does Commander pro only have one temp registering then? As you can see in the pictures above (Sensor labeled Commander Pro) I checked to see if i can add another Commander Pro Sensor but there is only the one.Īs a side question, where does the commander pro pick up the GPU temps from? (GPU Temp sensor 1,2,3) Is it picking up the rest of this data from the Bios/MB?Īfter digging around, looks like the Bios is controlling the Coolermaster AIO fan curve and one chassis fan (I'm betting it's the one on the back of the MB) The other 6 fans are controlled by the Commander Pro. I can follow those leads to one being behind the CPU MB with a fan directly on it (Picture 1) and the 2nd looks to go to the front and taped under the GPU. So Commander pro has the two temp leads in slot 1 and 2. ![]() So I had Digital Storm build it, I'm just trying to figure out the reasoning they used. Hey There C-Attack, I've seen you reply to thousands of posts as i was researching the problem, so I know I'm in good hands lol.įirst let me be honest, I didn't build the system, my condition with my hands doesn't warrant me getting my hands into tight cabinets, with tiny screws unless I'm trying to check my level of PSTD. I don’t think AMD owners have gpu temps at all right now. Possible there was an unintended casualty in trying to correct that. ![]() It’s probably going to be linked to how the data is fetched/presented for the fan curve which has been something of an ongoing issue for a while. Regardless of the above, this is a problem and is likely going to need a software correction. You don’t want the case fans to drop off for 3 seconds because you opened a game map and the GPU load/temp dropped to a fraction. You’ll have to figure out the normal range for that exact sensor position, but it is a more consistent control method. The fans don’t directly cool the CPU or GPU. The case fans help control the ambient case temperature and the probe measures that in a specific place. ![]() It’s also native to the controller, so it works with or without CUE running and no max fan blast when you boot up and shutdown. The Commander Pro Temp probe(s) is the right control source to use in most applications. There have been several user posts complaining about malfunctioning fan curves on this 5.7 release, but most had zero detail. CUE 4.33 and older did not have the extra temp data for some models, so that part is expected. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |