Skip to content
everything-imu

Troubleshooting

The status bar never reads “Live”

Section titled “The status bar never reads “Live””

everything-imu handshakes with SlimeVR-Server over UDP 6969. Make sure SlimeVR-Server is running before you expect Live, and that no firewall is blocking loopback UDP on that port.

A controller doesn’t appear on the Devices tab

Section titled “A controller doesn’t appear on the Devices tab”
  • USB on Linux: raw HID access is required. Apply the udev installer from the app settings, then replug the controller.
  • Bluetooth controllers (Joy-Con 1, Pro, DualSense, DualShock 4, PS Move): pair them through your OS Bluetooth settings first, then they show up here.
  • Joy-Con 2 / Pro Controller 2: these connect over BLE directly - no OS pairing dialog. If the peripheral vanishes from the scan after pairing, restart the Bluetooth adapter and wait up to 30 seconds.
  • Steam is running: Steam Input can grab a DualSense exclusively. Close Steam or disable Steam Input / PlayStation controller support for that pad.

The tracker shows up but doesn’t move

Section titled “The tracker shows up but doesn’t move”
  • Confirm the IMU is actually streaming on the device’s card (rate should be non-zero).
  • For a controller that went to sleep after pairing, the first input can take a second or two - the driver re-enables the IMU on the first timeout.

Yaw drifts as I turn

Section titled “Yaw drifts as I turn”

Controllers without a magnetometer have no absolute heading reference, so yaw drifts. Re-yaw facing forward (R), or use Reset Mounting right after strapping the tracker on. Devices with a magnetometer (Joy-Con 2, PS Move ZCM1) drift far less once calibrated.

Linux

Section titled “Linux”
  • No tray icon: harmless. On distros without libayatana-appindicator3 the tray is skipped rather than crashing the app.
  • AppImage won’t start: it needs FUSE 2. Run it with --appimage-extract-and-run on FUSE 3-only or immutable distros.
  • NVIDIA + Wayland rendering glitches: the WebView switches to a compatible path automatically; to force the default, export WEBKIT_DISABLE_DMABUF_RENDERER=0 before launching.

Android: phone doesn’t vibrate for haptics

Section titled “Android: phone doesn’t vibrate for haptics”

Some vendor skins (notably MIUI) ship “touch vibration” disabled, which silences app rumble even when the vibrate permission is granted. Enable touch/haptic feedback in the phone’s sound-and-vibration settings. The app routes rumble through a media/game vibration channel to work around this where possible.

Still stuck?

Section titled “Still stuck?”

File an issue with reproduction steps and the logs from the Logs tab: github.com/matiaspalmac/everything-imu/issues.