Using Nexus Alongside Other RGB & Fan Software

Nexus coexists fine with other software as programs. The friction is at the device level: two apps writing to the same fan controller or LED strip at the same time will fight, and the loser is you - flickering lighting, colors snapping back, fan speeds that will not stick. None of that is a malfunction in either app; it is two controllers issuing commands to one device.

The practical rule: let one app own each device. If you want Nexus to drive a device, close the other software or disable its control of that device. The reverse works too - Nexus does not need to own everything.

Nexus warns you about conflicts

Nexus watches for known conflicting software while it runs. When it spots one, an "App conflict" badge appears in the top bar. Clicking it opens the "Conflicting apps detected" list, which the app introduces plainly: "These apps drive the same lighting, fans, or peripherals as Nexus. Choose which ones Nexus terminates. Change this later in Settings."

Each app gets a card with its process name and PID. Click a card to switch it between "Will terminate" and "Keeps running"; where Nexus can tell which devices the app competes for, the card also lets you choose who controls them ("Nexus controls these" or "OpenRGB controls these"). "Save" applies your choices (it reads "Terminate 1 app" or "Terminate 2 apps" when any are set to terminate), and "Keep all running" leaves every app alone. If you are running the other tool on purpose, you can also turn off "Show conflict warnings" in Settings under "General"; the warnings are advisory, not a requirement.

Letting the other tool keep a device

You can split ownership per device instead of per app:

  • In Lighting, a device Nexus controls is marked "Controlled"; switch it to "Ignored - not controlled" and Nexus leaves its LEDs entirely alone, while still driving everything else.
  • Some device pages gate Nexus's control behind an explicit switch, and will tell you when another program currently holds the device so you can close it first.

This is the clean way to, say, let your motherboard vendor's utility keep the motherboard while Nexus runs your fans, hub, and everything else.

If devices or sensors detect unreliably at startup

When Nexus and another hardware tool start at the same time during boot, they can race for the same buses, and a device or sensor occasionally comes up missing or unreliable. On Windows, Settings under "General" has an "Autostart delay" slider (0 to 60 seconds). The app's own guidance: "If other RGB or monitoring software is causing inconsistent device or sensor detection, or unreliable cooling or lighting control, Nexus can wait before detecting your hardware at startup. Gradually increase the value until detection is reliable."

Tip

If a device is missing entirely rather than misbehaving, work through Device Not Detected first - a conflict shows up as flicker and snap-backs, not usually as a device that never appears.

The short version

  1. One owner per device. Pick Nexus or the other tool for each piece of hardware, not both.
  2. Let the "App conflict" warning do the finding; set what you do not need to "Will terminate".
  3. Keep the other tool where you prefer it, and mark those devices "Ignored - not controlled" in Nexus.
  4. Boot-time detection problems: raise "Autostart delay" a little at a time.