Jump to content

c-attack

Members
  • Posts

    20,092
  • Joined

  • Days Won

    267

Everything posted by c-attack

  1. I don’t think it will auto-detect it. You likely need to tell it something is there with a specific LED count. Each AR is 8 LEDs, so 24 in total in that circuit. Perhaps someone who uses Fusion can offer more precise advice.
  2. You are stuck with whatever controls the motherboard. If Asus, its Armory Crate. Gigabyte’s is called Fusion. MSI Mystic Light… and so on. Check your motherboard’s product page. Usually there are a lot of prompts to install. Asus even puts a trick in the BIOS to trigger an automatic download if your Windows security settings are lax enough to allow it.
  3. You likely have some registry corruption preventing CUE 5 from properly launching/opening. This one of the more common issues with the modular CUE 5. Try the clean install directions below. CUE 4 is not modular and installs to a different location and that’s likely why it is functional. However, it is more than a year out of date, so any new products won’t be recognized. https://help.corsair.com/hc/en-us/articles/360025166712-iCUE-How-to-perform-a-clean-reinstallation-of-iCUE No game or other application will recognize the G keys natively. They don’t have a defined meaning in the world at large. You need to use substitute mapping or use them as macro triggers to execute existing game control actions. The simplest version is something like: If “B” is Block in game, in CUE you can assign the keyboard letter B to any of the G keys and it will produce a B any time that profile is active. In game, that results in the intended execution. Combination input can be assigned as well. Most other mouse button can be reassigned, although some have restrictions like left click to prevent you from locking yourself out of an executable state. You can’t directly swap functions, but you can make a different mouse button change profiles and most mice let you reassign the profile button to a different task. “Sniper mode” is a preset DPI level activated when that key is held down. Some mice with dedicated sniper buttons (M65) do this natively. For other mice it can be assigned to most keys if you want it. If you don’t have a key assigned to this function, it’s not operational and irrelevant to use. You can’t delete DPI levels from the interface, but you can uncheck them and the mouse will not shift to them when DPI shift/cycle is used. These should appear grayed out in CUE.
  4. Corsair “AR” fans are an unusual product as they are not designed to work with the CUE control system. They have motherboard style rgb connectors and thus control is passed over to your motherboard rgb program. There is no Corsair controller in the setup and thus no CUE interaction.
  5. There are a couple of ways you can try and address it. 1) 3rd party adapter for the motherboard style ARGB connector. This will allow it to properly connect but it does pass the control to the MB RGB program, which may or may not be useful. That one fan will not change when CUE profiles and lighting do, so this really does separate it. Really only viable if you don't change themes very often and use common effects like static colors, rainbows, etc. 2) Corsair specific fan RGB splitter - This will "twin" two of your fans connected to the Commander Core and they will share a Y-splitter to one port. This will keep all the RGB in the Corsair app and change with everything else. However, if you do moving patterns like visor or any kind of wave effect, the two fans on the Y-splitter will display they effect at the same time. The two fans light and act like one. This means you need to choose the paired fans carefully for the least annoyance. This is a non-issue for static or intra-fan effects like spiral rainbow, rainbow wave, etc. since all fans in the circuit do the same thing at the same time. That makes this usually the best choice for most people. This is an example of Corsair specific RGB splitter for a RGB fan port. You can do the same thing on the PWM side with any common PWM 4+3 splitter.
  6. Had to put which fan on the motherboard rgb? Corsair fans are not designed to connect to your motherboard 5v RGB headers. Your motherboard rgb software is in control if you’ve forced it on.
  7. If you don’t want to disassemble it, can you get a small, thin toothbrush through the fill port? Looking again it looks like it’s on the tube on the wall side as well. That’s going to be difficult. You probably need to take it apart.
  8. Contact Corsair Support. Are there any physical issues with the Commander Core? Lights off, fans don’t run, pump error (!)? Typically when it’s device specific, CUE will reveal it with an error mark on the device or it alone drops from CUE. A full CUE crash is usually something else. If you haven’t done it already, do a full clean install. Corrupt registry files and/or entanglements with other monitoring/control programs is the number one reason for most crashes on CUE 5. Support is also likely to respond with this as a line 1 step, so might as well head them off. This will erase all profiles and settings. https://help.corsair.com/hc/en-us/articles/360025166712-iCUE-How-to-perform-a-clean-reinstallation-of-iCUE I would not pinhole reset the Commander as a troubleshooting measure. It has a limited use in specific hardware misbehavior circumstances, none of which appear to be in evidence. It also tends to create a mess with your profiles and CUE will think you added a second Commander Core.
  9. Losing the usb connection should drop it into HW mode only, which other than changing lighting should not impact performance. If the fans and pump stop, that is a clear sign of power loss and it puts the speed issue into a different light. It appears the unit is experiencing some type of power delivery problem. There is no software mechanism to stop the pump and it should run at all times regardless of software state. If you are still in your 5 year warranty period, contact Corsair Support to start the RMA process. If not, you’ll need to go shopping. Unless the SATA connector delivering power is only half connected, this is going to be a terminal failure pretty soon.
  10. It’s possible the two things are connected. Corsair likely blocked the 1.8x. FW update when this issue with the brightness warning occurred. It generally tends to show as “update failed” rather than “up to date” in these circumstances. Based on the latest posts in that thread, the 2.xx FW is not yet available and I expect your issue to be resolved when it is released. If not, we’ll take another look.
  11. It's a temporary bug. There is an extensive discussion below and a FW update is incoming to correct the error state.
  12. Any kit is a collection of average parts needed for a particular application. It's never going to be exactly tailor made for your use and it is not intended to be a price discount bundle. In a 1000D you are going to need more tubing than the average person, so make sure you price check the exact pieces you need vs any pre-packaged kit. A 5900x doesn't use a lot of watts unless you have tweaked a few things and/or use it for maximum CPU loads all day long. As such, the difference in CPU temp with any of the various cooling options is going to be small -- at least in an isolated test. 100W on any cooler isn't much to deal with. However, if you are running a dual fan air box above your GPU and spend most of your time gaming, you may be putting a decent amount of hot air into the CPU cooler stream. That may reduce your cooling efficiency and lead to higher gaming CPU temps. The big advantage of a water cooling system is you can move that heat elsewhere or for you, it may be more about moving the cooling elsewhere. I think this is were you gains would come from. A 1000D is certainly made for custom water cooling, so you have the case and space.
  13. Try running a repair install of the program. Windows Settings> Apps> Corsair iCUE. Click the drop down menu and select "modify". Follow the prompts for a repair installation. This does not erase profiles or settings but is good at cleaning up weird issues between OS and CUE. There have been some rolling issues with the CPUID sub-program and that is how CUE gets that data.
  14. You can mix 8 LED series fans (AF-Elite, SP-Elite, ML-Elite) and the LL fans (16 LEDs) on the Commander Core. However, if you have the older SP-Pro they are RGB compatible but won’t be speed controlled on the PWM only Commander Core. Also be aware mixed fan types will be automatically divided into separate groups by the Commander Core. You will see an “8 led series” and a “LL fan series” group since they have different effect lists related to the ring geometry.
  15. Yes, the Commander Core is compatible with SP-Elite, ML-Elite, ML-Pro, AF-Elite/RGB, HD, QL, and LL fan types. All of these are 4 pin PWM Corsair RGB fans. The LL is a medium rake blade with 9 fins and is a bit less effective on a radiator compared to the ML-Elite that came with the AIO. However, on a 360mm radiator this really won't matter unless you are running 300W+ CPU loads all day. In that case it will make a 1-2C difference, which should be irrelevant for most people.
  16. Contact Corsair Support. The triangle (!) has multiple meanings. Sometimes it connection errors or communication errors that can be solved through power cycles or reconnects. Other times it is a genuine hardware issue. If you are flashing red, that is a deliberate warning sign.
  17. Most publicly available profiles will not contain lighting data for the relatively new CUE Link devices. Profiles must be specifically programmed for the device in order for an import to work. Obviously your own personal profiles won’t contain that data until you create it and then re-save it.
  18. Watch your combinations. One of the trickier malfunctions to reveal is when a fan has a failure on the 8th led or on the return path. It makes that fan appear functional, but kills everything after. If the controller is damaged, then #2 should never work. Make sure you methodically test port 1-2 combinations to try and puzzle out where the circuit is broken. I think I misread the original post and you have 6 fans? When you bought the three additional was it as a multipack or singles? The multipack should have another LNCore in the box. Controller failures do happen, but 99% of the time it’s one of the fans.
  19. It seems like your MB side wall and bottom fans are intake and then force exhausting all case waste heat out through the top panel where the radiator resides. This is going to lead to higher than usual coolant temps, particularly in gaming when the GPU is spitting out 300W+. You can try to alternate intake/exhaust arrangements: 1) Turn the MB side wall fans to exhaust to see if you can draw more GPU heat out through that path vs the top exhaust. 2) Move the radiator to the side wall as intake or exhaust (case/room position dependent). Keep top as free air exhaust. This should help keep more environment waste heat away from the radiator. As for the immediate set-up, +1C to coolant temp = +1C to CPU temp. The only disadvantage of 41C vs 39C coolant is it makes the CPU +2C warmer. If your CPU temps are hitting your personal limit then you'll need to get strong on the fans, but otherwise set them to run at noise tolerable levels. Int his case, I think all you really need to do is create a 50% PWM plateau in the 39-44C range. This is where you'll be most of the time and this seems to be a tolerable speed for you, just below the annoyance level. Leave the heavy fan blast at 45 and 50C. If you hit 50C, you need to know. That should be out of bounds for most everyone. As to "typical temps", most user will idle 4-7C above room temp and see gaming temps +10C above that. It's the first part where you are losing some ground. Being able to keep the coolant baseline ~7C lower will let you further relax fans speeds or lower CPU temp 7C across the board.
  20. Those should be SP-elite fans. Make sure your lighting node core controller is configured as “8 LED fan series x 3 fans”. If you set it to “SP-RGB” (an older discontinued model), it will appear as if the fans are malfunctioning. Assuming that’s not it, the LNCore and fans are a series circuit. If LED #4 on Fan 2 burns out, the lights stop there. If all fans work in #1 but #2 never lights up, it may be the controller. If you are still in your case warranty period contact Corsair so they can send you a new Lighting Node Core. If not, we need to find you a new controller and there are some other options with benefits.
  21. That sounds a bit generic to me. There's no tweaking of the LC100 in this release, so if there is a specific problem, it certainly is going to be unintentional and they should be chasing some details. Rolling back to CUE 4 is not a realistic option for many people.
  22. You'll need to follow the USB cable from the Commander Core to it's end point. That should be the bottom of the motherboard, but I suspect it's dangling. That is the communication path and based on devices alone we know they can't all be connected without some external aid.
  23. You can’t make an 8 fan circuit and you’ll need to split the fans across two devices. For most people 6+2 is the best split. You can use the MB for speed control on the last two or pick up a cheap powered PWM hub and put the three front fans on that with one control lead to the Commander Core. That will free up two slots. As for lighting, you’ll need to set separate effects on both the Com Core and Lighting Node Pro. No way to link them into one circuit.
  24. The connection to the motherboard cpu fan header is a tachometer wire only. Its main purpose is to satisfy the motherboard’s native cpu boot protection feature. There is no power or control along that line. All CUE Link devices get their power from the hub, which in turn gets its power from the 6 pin pci-e cable. Make sure the hub is properly connected to the PSU. Does the AIO pump led and fans light up? The most common new user mistake has been skipping the AIO link cable ports on the radiator. Those are not optional and you must passthrough there to deliver power. There also have been a few bad cables, so if you have a spare, try it and see.
  25. All “X” series coolers are designed to be controlled by your motherboard. There is no CUE control or connectivity and it was intended for motherboard control. However, the RGB Elite version has a weird back door into CUE. If you have rgb slots free on the Commander XT, you can use it to control fans and pump lighting at the cost of three RGB headers. You could also in theory put the two fan PWM connectors on the opposite side of the controller, however you won’t have access to coolant temp data and using cpu temp is a poor substitute. I’d leave the speed control to the unit where it can read coolant temp until there is a reason to do otherwise.
×
×
  • Create New...