Enkeisha Emulator guides
DuckStation setup guide
Play original PlayStation games and move your memory cards
Start with one disc and confirm it boots. For games spread over several discs, use an M3U playlist and verify that the same memory card is available across discs.
Install DuckStation
Choose your OS on the official website or open the Latest PC release. Release builds roll forward, so record your build from the app’s About screen.
| Platform | First steps |
|---|---|
| Windows | Use Windows 10/11 and the correct x64 or ARM64 package. Install the runtime listed by the developer if required. Extract the ZIP in full and run DuckStation. For a test setup, create portable.txt beside the executable before launching it. |
| macOS | Use the Universal release for macOS 13.3 or later and move the app to Applications. |
| Linux | Make the AppImage for your CPU executable. Mount external drives before adding games from them. |
| Android | Use the developer’s Google Play listing. Choose your BIOS and a dedicated game folder the system picker can access. Menus and features differ from the desktop build. |
Extract the Windows x64 ZIP into its own folder and run duckstation-qt-x64-ReleaseLTCG.exe. The ZIP has no outer folder, so extracting it directly into Downloads scatters its files there. Official Windows instructions
Boot one game, then set up disc swapping
- Point DuckStation to a compatible BIOS dumped from your PlayStation or PS2. Start with a BIOS matching the game’s region for easier troubleshooting.
- For a BIN/CUE dump, launch the
.cuefile. Keep each track file alongside it under the filename listed in the CUE. A CHD is a single-file alternative. - Add the game folder in setup or the game list settings. To troubleshoot an empty list, open the CUE or CHD directly.
When the game requests the next disc, use the in-game disc change command. For a multi-disc title, create an .m3u file beside the discs, list one CUE or CHD filename per line and launch the M3U.
My Game (Disc 1).cue
My Game (Disc 2).cueBefore switching an ongoing game to M3U, back up its card and check the card mode. A title- or disc-specific card can change which progress is visible.
Import the BIOS in the first-run wizard
On the BIOS page, choose Install BIOS and select your BIOS file. This build displayed the recognized BIOS description and changed its detection status to green. If simply placing a file in the folder does not refresh the list, use the import function to check recognition. Booting a PS1 game still requires a compatible disc image.
Configure keyboard, controller or touch input
On desktop, open Settings → Controllers and configure Port 1. Start with Automatic Mapping for a controller or select each button to assign a keyboard key. Test the directional pad, confirm button, Start and both analog sticks.
Some early titles expect a digital controller. Choose the digital controller type if a DualShock appears unresponsive. On Android, check the touch overlay first, then pair your controller in Android and map it to Port 1.
The tested author-distributed Nortis expects a digital controller. We selected Digital Controller for Port 1 before booting it. Do not assume the wizard’s analog default, or a profile for another game, suits every title. Author’s input implementation
Raise the resolution and try PGXP
| Goal | Starting point |
|---|---|
| Compatibility and speed | Default renderer, 1× internal resolution and PGXP off. |
| Sharper 3D | Choose a hardware renderer and try 2×, then 3× if performance holds. |
| Less geometry wobble | Keep resolution fixed and try only PGXP geometry correction. Watch for shifting or missing geometry in a moving 3D scene. |
Start at 4:3. If widescreen or an advanced PGXP option introduces a glitch, revert the last change and test the same scene. Use a per-game setting for a title-specific fix. Developer’s feature list
Move memory cards to a new device
An in-game save is written to a virtual memory card. A save state captures a running session. Back up cards first, especially when changing versions.
| Platform | Where to look |
|---|---|
| Windows | %LOCALAPPDATA%\DuckStation for many new installs. Older setups may use Documents. |
| macOS | ~/Library/Application Support/DuckStation |
| Linux | $XDG_DATA_HOME/duckstation or usually ~/.local/share/duckstation |
| Android | Check the app’s available storage or export method before uninstalling. |
- In the desktop app, check Settings → Memory Cards. Tools → Open Data Directory also helps locate the standard
memcardsfolder. Save and quit before copying. - Use the same shared or per-game card mode on the new device. Preserve both the original card and any existing card on the destination.
- Boot the same game normally and load from its in-game menu. If you only have an old state, try opening it on the old build and saving to a card.
Developer’s data directory guide
Keep states separate from memory-card saves
We saved the Nortis title with System → Save State → Game Save 1. After restarting the game, we loaded the matching number under System → Load State and confirmed title rendering. “Game Save” in this menu names an emulator state slot, not a save written by the game to a memory card.
Troubleshooting and FAQ
If a multi-track disc has no music, check every track named in its CUE. For a single game that hangs, restore its per-game defaults and check the image and region. Some PAL titles also need subchannel information.
Frequently asked questions
Can DuckStation run PS2 games?
It is for the original PlayStation. Use the PCSX2 guide for PS2 games.
Can I keep BIOS and game files in separate folders?
Yes. Select the BIOS location and the game folder separately.
Do I need cover art before a game will start?
Cover art is for the library display. Check the disc image and BIOS first.