-
Notifications
You must be signed in to change notification settings - Fork 15
Troubleshooting: Reporting Problems
Read this before opening an issue. Most problems have a known solution.
- Search existing issues at github.com/nickybmon/OpenEmu-Silicon/issues — your problem may already be tracked. If it is, add useful new information in a comment rather than opening a duplicate.
- Use the latest release. Only the current release is supported. Check Releases and update first.
- Read the relevant guide — many common issues are covered in Importing Games, BIOS Files, CD-Based Games, and Troubleshooting: Input Problems.
| Supported | Not supported |
|---|---|
| Apple Silicon Macs (M1–M4) running macOS 11.0+ | Intel Macs |
| macOS 11 (Big Sur) through macOS 26 (Tahoe) | Hackintosh / patched macOS |
| Official releases from Releases | Builds you compiled yourself (unless reporting a build issue with reproduction steps) |
Input / controller not working → See Troubleshooting: Input Problems — the most common cause is a missing Input Monitoring permission.
CD-based game won't import or launch → Follow the CD-Based Games guide exactly. No additional help beyond the guide will be offered for CUE/M3U problems.
System won't start — asks for BIOS → See BIOS Files — install the correct BIOS file by dragging it onto your library window.
Cover art not loading → Go to OpenEmu → Preferences → Cover Art and enter your ScreenScraper.eu credentials.
Core not appearing / system missing → Check OpenEmu → Preferences → Cores and install the missing core.
"Cores" aren't responding after a macOS update → You may need to re-sign your installed cores. Open Terminal and run:
codesign --force --sign - ~/Library/Application\ Support/OpenEmu/Cores/*.oecorepluginUse the Bug report template and include:
- Mac model and chip (e.g. M2 MacBook Pro 14")
- macOS version (e.g. macOS 15.3 Sequoia)
- OpenEmu-Silicon version (from the title bar or About screen)
- Which system and game — ROM filename if relevant
- What happened vs. what you expected
- Console and crash logs — see Troubleshooting: Console and Crash Reports
- Steps to reproduce — exact sequence to trigger the problem
The more specific, the faster the fix. Vague reports ("it crashes sometimes") are very hard to act on.
- Do not post "+1", "me too", or "any update?" comments — these add noise without helping
- Do not link to or name ROM download sites
- Do not follow tutorials found on YouTube — they are often outdated or wrong
- Do not open an issue without searching for duplicates first