Troubleshooting Guide
This guide provides solutions to common issues and problems encountered when using mGBA. If you encounter a problem not covered here, please check the FAQ section or report the issue on GitHub.
Common Issues and Solutions
Game Won't Load or ROM Not Loading
Problem:
Game ROM file won't load or mGBA doesn't recognize the file.
Solutions:
- Verify the ROM file is a valid Game Boy Advance ROM (.gba format)
- Check if the file is corrupted - try re-downloading if possible
- If the ROM is in a ZIP archive, extract it first
- Ensure the ROM file isn't damaged or incomplete
- Try loading a different ROM to verify mGBA is working
- Check file permissions (ensure mGBA can read the file)
Low FPS or Performance Issues
Problem:
Game runs slowly or frames are skipping.
Solutions:
- Enable hardware acceleration (OpenGL, Vulkan, Direct3D 11, or Metal)
- Reduce resolution scaling (try 1x or 2x instead of higher scaling)
- Enable automatic frame skipping
- Close other resource-intensive applications
- Update graphics drivers to latest version
- Check if your hardware meets minimum requirements
- Try different rendering backends (software if hardware fails)
Audio Stuttering or Cracking
Problem:
Audio is stuttering, crackling, or skipping during gameplay.
Solutions:
- Increase audio buffer size in Settings β Audio
- Reduce sample rate (try 32 kHz if 44.1 kHz causes issues)
- Disable frame skipping if enabled
- Close other audio applications
- Check audio drivers are up to date
- Try different audio backends
- Reduce CPU usage from other applications
Save Files Not Working
Problem:
Game saves are not persisting or save files are not being created.
Solutions:
- Ensure mGBA has write permissions in its directory
- Run mGBA with administrator privileges if needed (Windows)
- Verify ROM and save file names match exactly
- Check save directory is not read-only
- Check available disk space (low disk space may prevent saving)
- Verify save type detection is correct (EEPROM, Flash, SRAM)
- Manually set save type if auto-detection fails
Graphics Glitches or Visual Artifacts
Problem:
Graphics are corrupted, glitchy, or displaying incorrectly.
Solutions:
- Switch between different rendering backends (OpenGL, Vulkan, Direct3D, Metal)
- Disable VSync if it causes issues
- Update graphics drivers to latest version
- Try software rendering if hardware acceleration causes problems
- Disable custom shaders or filters
- Reset video settings to defaults
- Check if specific game has known compatibility issues
Gamepad or Controller Not Working
Problem:
Gamepad or controller is not detected or controls don't work.
Solutions:
- Connect gamepad before launching mGBA
- Go to Settings β Input β Gamepad to configure
- Click each button to remap controls
- Restart mGBA with controller connected
- Check if gamepad is recognized by your operating system
- Try different USB ports (for USB controllers)
- Update gamepad drivers
- Test gamepad with other applications to verify it works
Link Cable Emulation Not Working
Problem:
Multiplayer or link cable emulation is not connecting.
Solutions:
- Enable link cable emulation in Tools β Link Cable before loading games
- Ensure both instances have the same game loaded
- Check firewall settings if using network mode
- Verify both instances are on the same network (local network mode)
- Check IP address configuration for network connections
- Try restarting both mGBA instances
- Ensure the game supports link cable multiplayer
Cheat Codes Not Working
Problem:
Cheat codes are not taking effect or causing crashes.
Solutions:
- Verify cheat code format matches the game version
- Check if cheat codes are for the correct game and region
- Ensure cheat codes are enabled (check checkbox)
- Try loading cheat codes before starting the game
- Verify cheat code format (GameShark, Action Replay, CodeBreaker)
- Some cheats may require specific game states to work
mGBA Crashes or Freezes
Problem:
mGBA crashes, freezes, or becomes unresponsive.
Solutions:
- Update to latest version of mGBA
- Update graphics drivers
- Check system logs for error messages
- Disable custom shaders or filters
- Reset configuration to defaults
- Check available memory (low RAM may cause crashes)
- Verify ROM file is not corrupted
- Report crash with error details on GitHub Issues
Platform-Specific Issues
Windows
- Visual C++ Runtime Error: Install Visual C++ Redistributable
- DirectX Errors: Update DirectX runtime libraries
- Permission Errors: Run as administrator or adjust folder permissions
- Antivirus Blocking: Add mGBA to antivirus whitelist
macOS
- "App is Damaged" Error: Remove quarantine attribute:
xattr -d com.apple.quarantine mGBA.app - Gatekeeper Warning: Allow app in System Preferences β Security
- Metal Errors: Update to latest macOS version
Linux
- Missing Libraries: Install required dependencies (SDL2, Qt5, etc.)
- Permission Errors: Check file permissions and ownership
- Graphics Issues: Update Mesa drivers or proprietary GPU drivers
Getting Help
If you cannot resolve your issue:
- Check the FAQ section on the main website
- Search existing GitHub Issues for similar problems
- Create a new GitHub Issue with:
- Detailed description of the problem
- Steps to reproduce the issue
- Your system specifications (OS, CPU, GPU)
- mGBA version
- Error messages or logs if available
Related Articles
For more information about mGBA configuration and usage:
- Getting Started Guide - Installation and basic setup instructions
- Performance Tuning Guide - Solutions to performance issues and optimization strategies
- Advanced Configuration Guide - Advanced settings that may help resolve issues
- Configuration API Reference - Configuration options and settings management