Fast fixes first
Troubleshooting
Do not guess randomly. Split the problem first: route, hardware, feed, output, or launcher auth.
Use this order
Quick triage
Most common failure buckets.
1PC board not detected
Usually wrong cable, wrong USB path, or unstable board side first.
2PC feed inactive
Usually OBS / DistroAV / NDI order, wrong stream name, or LAN issue.
Test Move works, aim does not
Output path is fine. Feed path, color path, or route path is wrong.
Wrong plan / wrong route
1PC and 2PC are isolated. Wrong launcher or wrong license wastes time fast.
Board or bridge is not detected
Launcher opens, but the 1PC hardware path is not seen correctly.
Why this happens
Most 1PC failures start before software. Wrong cable, wrong host side, or unstable board power kills the route first.
Check now
- Use a real data cable, not charge-only.
- Re-seat the board on another USB port.
- Check Windows Device Manager before touching launcher settings.
- If Leonardo route, re-check Host Shield solder points.
Do this next
- Stabilize the board path first.
- Only after that, reopen the launcher and continue.
- If RP2040 route, verify mouse really enters the board first.
If still broken
Tell support exact board, exact cable path, and whether Device Manager sees it.
RP2350 shows as G203, but mouse does not light
Windows sees the board, but the real mouse connected to the RP2350 stays completely off.
Why this happens
Those are two different USB sides. Windows seeing G203 confirms the board-to-PC device side. If the mouse LEDs stay off, the mouse-side host/OTG path has no 5V/VBUS or is not the real host side.
Check now
- Use the RP2350 PIO-USB host/OTG side for the mouse, not the PC-side USB port.
- Confirm the mouse receives 5V and GND on the host side.
- Try a powered USB hub or powered OTG adapter between RP2350 and mouse.
- Only continue to firmware/HID debugging after the mouse lights up.
Do this next
- Fix host-side power first.
- Reflash the RP2350 UF2 only after the hardware side is known powered.
- If LEDs turn on but movement still fails, then send the exact board, adapter, and mouse model to support.
If still broken
Tell support whether the mouse LEDs turn on, exact RP2350 board, exact OTG/powered hub used, and whether Windows still shows G203.
Aim feels dead or detection looks wrong
Launcher is open, but behavior does not look like target color is being tracked.
Why this happens
Usually board path is fine and the real problem is color range, wrong monitor assumptions, or using the wrong workflow for the current build.
Check now
- Re-check HSV values.
- Make sure target color is really visible on the actual game image.
- Confirm this is the 1PC launcher for a 1PC license.
Do this next
- Reset to a known-good color profile.
- Lower variables only after the color path starts responding again.
- Do not debug movement before the color path is alive.
If still broken
Tell support exact game color, current HSV, and whether board path is already confirmed stable.
PC1 feed shows inactive
PC 2 panel is open, but the NDI source never becomes live.
Why this happens
Usually not a launcher problem. Real problem is OBS + DistroAV + NDI chain or LAN path on PC 1.
Check now
- Install order must be OBS -> DistroAV -> NDI runtime or extension.
- Restart OBS after installs.
- Enable Main output in DistroAV and keep stream name correct.
- Both PCs must be on the same LAN.
Do this next
- Open OBS and confirm the stream is actually active first.
- Then return to PC 2 panel and wait for the source to appear.
- If feed dies later, restart the OBS output chain before touching aim settings.
If still broken
Tell support exact stream name, whether DistroAV Main output is enabled, and whether PC 2 panel says inactive or waiting.
Test Move works but modules do nothing
MAKCU output path is alive, but aim/magnet still look dead.
Why this happens
This means output path is usually fine. Real issue is feed, color, or route selection.
Check now
- Check PC1 Feed status first.
- Confirm 2PC launcher + 2PC license are being used together.
- Confirm target color is visible inside the NDI feed, not only on PC 1 locally.
Do this next
- Fix NDI or color path first.
- Only after feed is live should you tune movement settings.
- Do not re-debug MAKCU if Test Move already works.
If still broken
Tell support whether Test Move works, whether feed FPS is live, and what the detector counters show.
MAKCU bridge feels wrong
Mouse path exists, but behavior is inconsistent or completely wrong.
Why this happens
Most of the time this is port order or cable order, not the launcher logic itself.
Check now
- Left MAKCU port -> PC 1.
- Middle MAKCU port -> PC 2.
- Right MAKCU port -> mouse.
- Re-seat all three lines after verifying the order.
Do this next
- Return the wiring to the exact documented order.
- Reconnect mouse last.
- Retest with panel hardware test only after rewiring.
If still broken
Tell support exact MAKCU port order and whether panel hardware test still works.
Download or launcher route mismatch
License works in one place but not the other, or the wrong launcher was downloaded.
Why this happens
1PC and 2PC are intentionally isolated. Wrong route creates fake auth or hardware debugging.
Check now
- 1PC license -> 1PC launcher only.
- 2PC license -> 2PC launcher only.
- Use Downloads page with the real license to unlock the correct route.
Do this next
- Download the route-specific launcher again.
- Do not mix 1PC and 2PC builds between machines.
- Keep VPN off if 1PC launcher download is blocked.
If still broken
Tell support exact license key, exact launcher route, and exact download error text.
Still stuck
What to send to support.
Best support ticket includes route, exact hardware chain, exact launcher route, exact error text, and whether panel tests already worked.