Troubleshooting

Controller not working with console or GameCube adapter

This is one of the most common issues and usually relates to polling rate optimization or adapter compatibility.

Arduino-based controllers with official adapters

If you are using an official adapter with an Arduino-based controller, you will likely need to disable the polling latency optimization:

Hold A on plugin - This disables the polling latency optimization by passing in a polling rate of 0 to the GamecubeBackend constructor

This issue occurs because the official adapter may not be compatible with the default polling rate optimization that HayBox uses.

Power requirements

Different microcontrollers have different power requirements:Arduino-based controllers (without boost circuit):

Require 5V power
For Mayflash adapter: both USB cables must be plugged in
For console: the rumble line needs to be intact

Pico/RP2040-based controllers:

Work natively with 3.3V power
No special power requirements

If your Arduino-based controller is not responding, check that it’s receiving adequate 5V power. The rumble line on GameCube cables is often used for power delivery.

Arduino-based controller not responding

Arduino-based controllers (like B0XX R1-3, LBX) have specific power requirements that differ from Pico-based controllers.

Check power supply

Arduino controllers without a boost circuit require 5V power:

On Mayflash adapter: Ensure both USB cables are plugged in
On console: Verify the rumble line in your GameCube cable is intact
On official adapter: Hold A on plugin to disable polling optimization

Polling rate issues

If the controller works but feels laggy or inconsistent:

Hold RT1 (A) on plugin to enable GameCube backend with polling rate fix disabled
This is specifically designed for use with GCC adapters

Using 1000Hz polling rate on console will work but results in more input lag. The polling rate setting is meant to sync with your adapter, not overclock the console.

Pico/RP2040 controller issues

While Pico-based controllers generally have better compatibility, there are still some things to check.

Power advantages

Pico controllers work natively with 3.3V power, making them more compatible:

No boost circuit required
More flexible power options
Better adapter compatibility

Entering bootsel mode

To flash new firmware or troubleshoot:

Hold RT2 (C-Down) on plugin to enter bootsel mode
The Pico will appear as a USB drive (RPI-RP2)
Drag and drop .uf2 firmware files

Polling rate

Unlike Arduino, Pico doesn’t require polling rate configuration:

Pico has enough processing power to read inputs after receiving the console poll
No need to predict poll timing
Automatic optimization for both console and PC use

Mayflash adapter setup

The Mayflash GameCube adapter requires specific setup depending on your controller type.

Arduino-based controllers

Plug in both USB cables - Arduino controllers need 5V power
The first cable (data + power) connects to your PC
The second cable (power only) provides additional power

Without both cables, Arduino controllers without boost circuits will not receive adequate power.

Pico-based controllers

Only one USB cable needed
Native 3.3V operation
Plug and play compatibility

If you’re experiencing issues with a Mayflash adapter, first verify you have both USB cables connected for Arduino controllers.

Official adapter compatibility

The official Nintendo GameCube adapter has specific compatibility requirements with HayBox.

Arduino controllers

Required action: Hold A on pluginThis disables the polling latency optimization that is incompatible with official adapters. Specifically:

Passes a polling rate of 0 to the GamecubeBackend constructor
Disables predictive polling timing
Ensures compatibility with official adapter firmware

Why this is necessary

By default, HayBox optimizes polling for reduced latency by predicting when the next poll will arrive. The official adapter’s timing doesn’t work well with this optimization, requiring it to be disabled.

Alternative button holds

RT1 (A) on plugin - GameCube backend with polling rate fix disabled (for GCC adapters)
RT3 (C-Left) on plugin - Nintendo 64 backend (60Hz polling rate)

Boost circuit requirements

Some Arduino-based controllers require a boost circuit to function properly without external power.

What is a boost circuit?

A boost circuit steps up voltage from 3.3V to 5V, allowing Arduino controllers to:

Operate with single USB cable on adapters
Work without rumble line on console
Function independently of external 5V power

Controllers without boost circuits

If your Arduino controller lacks a boost circuit:On Mayflash adapter:

Requires both USB cables plugged in
Cannot operate on single cable power

On console:

Requires intact rumble line for power
May not work with damaged GameCube cables

Pico alternative

Pico/RP2040 controllers don’t need boost circuits because:

Native 3.3V operation
Lower power requirements
Better power efficiency

If you’re building a new controller, consider using a Pico/RP2040 to avoid boost circuit requirements entirely.

Console detection issues

HayBox automatically detects whether you’re plugged into a console or USB, but sometimes this needs manual override.

Pico/RP2040 auto-detection

Automatically detects:

USB vs GameCube vs Nintendo 64
Default is XInput for USB (PC gaming)

Manual backend selection (hold on plugin):

RF2 (X) - Nintendo Switch USB mode (also sets Ultimate mode)
RF3 (Z) - DInput mode (for games without XInput support)

Arduino/AVR detection

USB detected → DInput backend
No USB → GameCube backend by default

Manual backend selection (hold on plugin):

RT1 (A) - GameCube backend with polling rate fix disabled (for GCC adapters)
RT3 (C-Left) - Nintendo 64 backend (60Hz polling rate)

Dolphin/Slippi not detecting inputs

If your controller is recognized but inputs aren’t working in Dolphin or Slippi, you likely need the correct controller profile.

Profile files

HayBox uses different mappings than official B0XX firmware. Profiles are located in the dolphin folder:Windows:

HayBox_XInput.ini - For Pico/RP2040 (e.g., B0XX R4)
HayBox_DInput.ini - For Arduino/AVR (e.g., B0XX R1-3, LBX)

Linux:

HayBox_XInput_Linux.ini - For Pico/RP2040
HayBox_DInput_Linux.ini - For Arduino/AVR

macOS:

HayBox_DInput_macOS.ini - DInput only (limited support)

Installation locations

Slippi Launcher:

Windows: %appdata%\Slippi Launcher\netplay\User\Config\Profiles\GCPad\
Linux: ~/.config/SlippiOnline/Config/Profiles/GCPad/
macOS: /Users/<USER>/Library/Application Support/Slippi Launcher/netplay/Slippi Dolphin.app/Contents/Resources/Sys/Config/Profiles/GCPad

Vanilla Dolphin:

Windows: %userprofile%\Documents\Dolphin Emulator\Config\Profiles\GCPad\
Linux: ~/.config/dolphin-emu/Profiles/GCPad/

Setup steps

Copy the appropriate .ini file to the correct folder
In Dolphin, configure a “Standard Controller”
Click Refresh next to the Device dropdown
Select the HayBox profile and click Load (not Save)
Ensure correct device is selected in dropdown

macOS only supports DInput and compatibility is poor. Pico/RP2040 controllers must force DInput mode by holding Z on plugin. This is unsupported due to Apple’s limited controller support.

Mode switching not working

HayBox allows mode switching on-the-fly, but requires specific button combinations.

Default controller modes

Hold Start + Mod X + one of:

L - Melee mode (default)
Left - Project M/Project+ mode
Down - Ultimate mode
B - Rivals of Aether mode
R - Rivals of Aether 2 mode
Right - FGC mode (Hitbox style)

Default keyboard modes

Only available with DInput backend (not XInput):

Start + Mod Y + L - Default keyboard mode