Pokémon Pokopia on Eglantine

Which Forks lists 15 Pokopia reports. Fourteen include a frame-rate number, and the median is 60 FPS. The GPU mix is small: 4 AMD, 3 NVIDIA, 3 Steam Deck, 5 unlabeled. An RX 6700 XT note sits at 50–60. A GTX 1080 note hits 60 with stutter. Steam Deck notes sit at 40–50 and dip to 30. A notsapinho note claims 80 or more with a 120 FPS mod, and the same notes say 120 is not a stable target. I am not promoting that mod to a recommended setting.

The fork name that comes up for this game is PokeDinner, with 2.5.0 named as a usable point, or notsapinho. PokeDinner 2.0.0 is tied to invisible items. ZendNevs v2.0.4 is tied to a startup freeze. Mainline build 74 fixes the emulator incorrectly rejecting SetHeapSize requests of 8 GiB or more: Pokopia requests 9.5 GiB. The release follows the 12 GiB memory layout and expands the heap region from 8 to 16 GiB, alongside audio and startup-service fixes. This describes emulated address-space handling, not a physical RAM minimum. Resetting the memory layout is the setting people repeat. Fast and accurate are both reported at 60 on different builds, so I will not crown one accuracy mode.

Issue 414 is “no file system interface” when the game boots from base/exefs/main. The workaround written there is to boot from the update’s exefs instead. Issue 491 is stuck on Launching on build 189. Issue 661 says Pokopia no longer runs on Steam Deck on the latest build that reporter had. Issue 545 is texture flicker. A separate note is a 0 FPS black screen after loading. Black sky and missing audio are still in the status line because those reports were not closed by a single build number I can point at.

Sixteen gigabytes of system RAM is the practical floor in the same community notes. PokeDinner’s own checklist is harsher: 12 GB of DRAM plus a 32 GB page file. If you are choosing between mainline and PokeDinner, read the PokeDinner page before you grab 2.7.7, because that version’s notes warn AMD users away.