Setup

Walkthrough.

This checklist mirrors how experienced users walk newcomers through first boot: install a clean build, add BIOS you dumped yourself, point the game list at your library, then tune graphics and pads. Deviating is fine—just change one thing at a time so you know what fixed (or broke) a title.

Sections below expand the same checklist support volunteers use—skim headings first, then drill into the steps you skipped.

  1. Install

    Use the Download hub to fetch a Windows installer, portable zip, or Linux AppImage from GitHub releases only. Note the exact version string—you’ll need it if you ask for help later.

    On Windows, install the VC++ runtime if the app fails to start; see Support.

  2. BIOS

    Place dumps you created from hardware you own into the BIOS directory the emulator expects (check the current UI label—paths move slightly between versions). Match region family to your game rips: NTSC-U, NTSC-J, PAL, etc.

    If the BIOS list is empty, you pointed at the wrong folder or the files are incomplete. Never download BIOS from random sites—see FAQ.

  3. Game list

    Open Config → Game List (or the equivalent in your build) and add folders that contain ISO, BIN/CUE, or CSO files—not shortcuts to random archives.

    Let the scanner finish; if a title is missing, confirm the extension is supported and the rip is not split across folders without a proper CUE sheet.

  4. Controllers

    Config → Controllers — map DualShock-style buttons to keyboard, Xbox, or PlayStation pads. Enable pressure-sensitive buttons if your hardware supports them; rumble is optional per device.

    Test in the small preview window before launching a game so you don’t discover a wrong axis mid-cutscene.

  5. Graphics (first sane defaults)

    Open Settings → Graphics. Pick Vulkan or D3D12 on Windows when available; on macOS use the recommended Metal path for your build.

    Start at native or modest internal resolution, confirm full speed, then raise upscale in small steps. Enable widescreen or no-interlace patches only if the wiki suggests them for that game.

  6. Audio & first launch

    Under audio settings, leave defaults unless you hear crackle—then stabilize FPS first, and only then tighten latency options.

    Boot your game from the game list; if you get a black screen, try software renderer once to isolate a GPU issue, then consult Support and the wiki for that title.

Optional polish

  • Turn on frame pacing or limiters if your display shows tearing or inconsistent pacing.
  • Create per-game configs for heavy hitters once you read their wiki pages.
  • Back up memcards before experimenting with cheats or aggressive patches.

Hotkeys & quality of life

Learn where fullscreen, frame limiter toggle, and save-state slots live in your build’s input settings. Binding them to something you can reach without alt-tabbing saves hours.

Enable on-screen FPS only while tuning; permanent overlays add noise when reading forums or comparing videos.

When something breaks: logs

Before you post “black screen help,” grab a fresh emulog from a single boot through the failure, with no unrelated games mixed in. Redact paths if you care about privacy, but keep renderer lines intact.

Forum helpers and GitHub triagers ask for the same bundle every time—see Support for the checklist.

Folder hygiene (recommended)

Keep games, BIOS, and memory cards in predictable locations. Avoid storing memcards inside cloud-sync folders while a game is running—sync conflicts corrupt saves.