Jump to content
Corsair Community

Corsair Calico Jack

Corsair Employees
  • Posts

    684
  • Joined

Reputation

10 Good

Recent Profile Visitors

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

  1. It renders an overlay over the sides, so the output you're using shouldn't matter.
  2. The QL fans include a Lighting Node CORE. A Lighting Node Core is essentially a Lighting Node Pro and Hub combined into a single product. The "two piece" you're referring to is a Lighting Node Pro. The 6 channel item is an RGB hub. So,if you have 2 USB headers on the board, you can plug your Lighting Node Pro (LNP) and Lighting Node Core (LNC) into the board separately. If you do not, then you would need to purchase another RGB Hub, plug the LL fans into one hub and the QL fans into the other, and plug both into the Lighting Node Pro. Alternatively, you can buy a Commander Pro, and plug the Lighting Node Core into the USB header into USB hub in the back of that product.
  3. Ok, so I'm reading through this and I feel some clarification is needed. You can't use more than 6 strips on one channel because of the LED limitation. Each channel can't power more than 4 long and 2 short strips. Each channel is essentially a different lighting controller, so you cant just run the extra strips on the other channel. The max number of LEDs is listed in your manual. The strips need to be plugged in in this specific order: Short, Long, Long, Short, Long, Long. The controller is expected to be in the bottom right corner of the monitor. Here is a video outlining the installation: There's a lot of feedback here, and I'm happy to forward it, but please remember that the video playback and how it operates is limited in numerous ways in order to achieve that immediate ambient color change. I can't promise anything, but I can certainly make sure that our teams are aware of the discussion around Ultrawide. I'm not going to be able to offer any specific changes, but if you have feedback regarding how it operates, you are certainly free to share and discuss on this thread.
  4. You would need either 2 hubs and a lighting Node Pro, or you can use what you have but would need another USB header on the board. Alternatively, you can just buy a Commander Pro and plug into the USB headers in the back of it.
  5. Devbiker is probably right here. Most likely the fan is faulty. Try his suggestion above, and then create a ticket on help.corsair.com if you can't just have the fan replaced at the store. We'll get you set up.
  6. I'd suggest creating a ticket on help.corsair.com Either the firmware needs to be flashed, or some of these LED's have failed. Both issues will need to be fixed through a ticket, so I'd suggest just going ahead with it.
  7. Just to correct Zotty above, you cannot mix any fans on the hub. Every fan on the RGB hub must be the same kind of fan. Also, please note that you need a Commander Pro, Lighting Node Pro, or Lighting Node Core in order to control your fans in iCUE.
  8. It's not exactly specific to iCUE. This is an issue AMD's been dealing with:
  9. Have you guys seen QL fans? https://www.corsair.com/us/en/Categories/Products/Fans/RGB-%26-LED-Fans/iCUE-QL-RGB-PWM-Fan/p/CO-9050098-WW
  10. Stated by AMD, this isn't specific to iCUE. This is a problem related to monitoring software and the 3000/2000 series CPU's. You can try the solution I offered above, which will turn off the Hardware related iCUE functions, or wait for further BIOS updates.
  11. Go to Services.msc, locate the Corsair Service, right click it and select Properties, change Startup Type to Disabled, and then Select Service Status Stop. That should turn it off and keep it off until u start the service again in services msc.
  12. It's because your in a Hardware profile. You need to use a Software Profile in order to use the Advanced Settings you are attempting to use.
  13. Why do a macro? Reassign the Aim with Knife button in the game to RCTRL. Then create a Keystroke Remap in iCUE that presses RCTRL and Attack and assign it to the mouse. Much easier than creating the macro and worrying about delays and timing.
  14. Hi, Same thing. They all use the same CPUID SDK. They can't all grab from the sensors at the same time, so they'll conflict.
×
×
  • Create New...