ePSXe’s plugin system gives you two very different graphics paths: maximum compatibility at native resolution, or upscaled HD output that can look strikingly clean on 3D games. These settings target the second path on a typical modern PC, with fallbacks noted where a game disagrees.
Choose the right video plugin first
Open Config > Video. For HD output, choose Pete’s OpenGL2 core plugin (settings in depth in our OpenGL2 guide). For a problem game, drop to the internal GPU core at native resolution — if the glitch disappears, the plugin settings were the cause. The official recommended spec (fast dual-core CPU, 512 MB RAM, OpenGL 2.0 + GLSL card) covers native resolution comfortably; upscaling is what asks more of the GPU.
The settings that matter
- Internal resolution: 2x–3x on a mid-range GPU is the sweet spot. Higher values mostly sharpen menus, not models, and can introduce slowdowns in framebuffer-heavy games.
- Texture filtering: use an extended/filtered setting for 3D textures, but expect occasional seams in 2D-heavy games. If sprites develop black outlines, reduce filtering first.
- GTE accuracy: enabling the accuracy options reduces the classic PS1 polygon wobble. Be clear about what this is not: ePSXe has no native PGXP like DuckStation’s — see the honest note in ePSXe vs DuckStation.
- Framebuffer effects: keep them enabled (or on a middle setting) for games with screen transitions and effects; disabling them is a common cause of missing effects and some black screens.
- Use FPS limit: on, with the limit set to auto/60 (NTSC) — this also prevents the games running too fast problem.
2D games: a different recipe
For sprite-based games, native resolution with a CRT-style shader usually looks better than aggressive upscaling. On Android v2.0.19, the fixed CRT shaders and the new CAS and MMPX shaders are designed exactly for this case.
Per-game profiles beat one global setup
PS1 emulation rewards per-game tweaks: one title wants framebuffer effects maxed, the next breaks with the same setting. Change one thing at a time, note what fixed the game, and keep the global profile conservative. If a game still misbehaves after a plugin reset, check the troubleshooting hub before assuming the rip is bad.