Troubleshooting (Linux)
This guide covers common issues you might encounter with LookPilot and how to resolve them.
Find your issue
Camera Issues
Camera Not Detected
Symptoms: Camera doesn't appear in the dropdown list or shows "No camera"
Solutions:
- Refresh camera list: Click the reload button (⟲) next to the camera dropdown
- Check camera connection: Ensure your camera is properly connected via USB
- Close other applications: Make sure no other software is using the camera (browsers, video chat apps, etc.)
- Try different USB ports: Switch to a different USB port, preferably USB 3.0
- Restart LookPilot: Close and reopen the application
- Check camera permissions: Ensure your user has access to
/dev/video* devices
- Install v4l-utils:
sudo apt install v4l-utils then check cameras with v4l2-ctl --list-devices
- Use .deb Steam version: Make sure to use .deb version of Steam (Flatpak, Snap or any other containerized installations aren't supported) - https://store.steampowered.com/about/
Tracking Issues
Head Tracking Not Responsive
Symptoms: Moving your head doesn't affect the 3D visualization or game camera
Solutions:
- Check tracking status: Ensure "Start tracking" button shows "Stop tracking" (tracking is active)
- Verify camera selection: Make sure a camera is selected in Settings > Camera
- Check lighting: Ensure your face is well-lit with even lighting
- Verify head position: Sit in the camera's field of view with your face clearly visible
- Adjust deadzone: Lower the deadzone value in head tracking settings
- Reset tracking: Press the "Center" button to reset the neutral position
- Check enabled axes: Verify the desired axes (Yaw, Pitch, etc.) are enabled
Tracking is Jittery
Symptoms: Camera movement is shaky or jumps around erratically
Solutions:
- Increase smoothness: Raise smoothness values in head/eye tracking settings
- Increase deadzone: Deadzone prevents tiny movements (sometimes noise) from affecting the tracking.
- Increase confidence threshold: Can be also found in tracking settings. Increasing will cause less certain tracking predictions to be ignored.
- Improve lighting: Add stable, consistent lighting to your face
- Reduce background movement: Minimize movement behind you in the camera view
- Lower FPS: Reduce tracking FPS in Settings > Performance if your system can't keep up
- Check camera mounting: Ensure camera is mounted stably and not vibrating
- Close other applications: Free up system resources by closing unnecessary programs
Game Communication Issues
Game Not Responding to Head Tracking
Symptoms: Tracking works in LookPilot but doesn't affect the game camera
Solutions:
- Look for a game guide: Most popular games have a corresponding guide here: game setup guides.
- Verify TrackIR support If trying the freetrack protocol, verify that given game support TrackIR tracking online or in the game documentation.
- Check protocol selection: Ensure the correct protocol is selected for your game
- Enable in game: Look for head tracking options in the game's settings menu
- Restart game: Close and reopen the game after starting LookPilot tracking
- Try different protocol: If available, test with a different communication protocol
- Check Proton setup: For Proton games, verify Steam installation and game selection are correct
- Verify game launched: Ensure the target game has been launched at least once through Steam
- Check Steam running: Make sure Steam is running and logged in
UDP Protocol Issues
Symptoms: UDP communication fails to connect
Solutions:
- Verify IP and port: Double-check the IP address and port number configuration
- Check target application: Ensure the receiving application is running and listening
- Test with localhost: Try using 127.0.0.1 for local testing
- Check firewall: Verify firewall isn't blocking UDP traffic on the specified port
- Try different port: Test with a different port number if the current one is in use
Proton Issues
Symptoms: Proton protocols fail to start or games don't detect tracking
Solutions:
- Launch game first: Start the target game through Steam at least once to create Proton prefix
- Check Steam path: Verify LookPilot has detected the correct Steam installation path
- Select correct game: Ensure you've selected the right game from the dropdown
- Steam running: Make sure Steam is running and you're logged in
- Verify game in library: Confirm the game is actually in your Steam library
- Browse for Steam: Manually browse to your Steam installation if auto-detection fails
- Force a mainline Proton version: If
auto / freetrack (Wine) never connect, force a specific official Proton version on the game (Steam -> Properties -> Compatibility). Proton 10 is the most commonly confirmed by users; Proton-GE has also fixed connection failures where Proton Experimental or distro-specific builds (e.g. CachyOS Proton) failed
- Native Linux game builds: most native builds have no head-tracking interface at all (X4: Foundations is a notable exception, via UDP). If a game ships both native and Windows builds, force Proton on the game and follow the Wine/Proton setup
Keybind Issues
Keybinds Not Working
Symptoms: Preset keybinds or system keybinds don't respond when pressed
Solutions:
- Wayland: Update LookPilot first - recent versions support global hotkeys on Wayland. The robust route on any Wayland compositor is the local control API: bind your compositor's own shortcuts to
lookpilotctl center / toggle / pause (see the Control API guide)
- Check other applications: Verify another application isn't capturing the key combination
- Try different keys: Use a different key combination
- Restart LookPilot: Close and reopen the application to re-register keybinds
- Verify keybind is set: Check that the keybind is actually configured in the preset options
Performance Issues
High CPU Usage
Symptoms: LookPilot uses excessive CPU resources
Solutions:
- Lower FPS limit: Reduce tracking FPS in Settings > Performance
- Reduce camera resolution: Use lower resolution in Settings > Camera
- Close other applications: Free up CPU resources
- Check camera drivers: Update to latest camera drivers
App Startup Issues
LookPilot won't launch
Solutions:
- Run it natively: Never force Proton/Wine on LookPilot itself - it is a native Linux app
- Force the sniper runtime: If the default launch fails, set the Steam compatibility tool for LookPilot to "Steam Linux Runtime 3.0 (sniper)" and let it update
- Check the logs: They live in
~/.local/share/LookPilot/logs - zip and send them to support@lookpilot.app
- Clean reset (last resort): Delete the installed files (Steam -> Browse local files) plus
~/.local/share/LookPilot, then reinstall. This resets local presets and settings
- Standalone fallback: The standalone build from lookpilot.app/downloads works without the Steam runtime
- AppImage needs FUSE2: The standalone AppImage currently requires FUSE2, which some distros (Fedora Atomic, CachyOS) no longer ship - install libfuse2 manually or use the Steam build
Offline Use
LookPilot currently needs an internet connection at startup (known issue). Workarounds:
- Start online, then disconnect: Start LookPilot while online and load your preset - tracking keeps working after you go offline
- Launch the binary directly:
.../steamapps/common/LookPilot/main.dist/LookPilot starts without Steam and offers a guest login (presets cannot be loaded that way)
- ISP blocking: If community presets or bug reports never load even though your connection works, your ISP may be blocking our servers - testing over a VPN confirms this
Switching to an Older Version
If something broke right after an update, rolling back is a quick way to confirm it and keep playing:
- Steam: right-click LookPilot > Properties > Betas, and pick an older version from the dropdown
- Standalone: all releases are available at github.com/Reblexis/lookpilot-downloads/releases
If an older version fixes your problem, please report the bug (in-app Feedback tab) so it gets fixed in the current version.
Known Issues
- Game stays "running" in Steam after you exit it: press Stop tracking in LookPilot and the game process will finish closing. You do not need to quit LookPilot
- DCS hangs on exit while tracking runs: stop tracking before quitting DCS (see the DCS World guide)
If your issue isn't listed here, please contact support@lookpilot.app