Mario Kart World on Eglantine

The project readme says Mario Kart World can run at decent or full speed depending on the PC and the settings. It does not publish a frame-rate table. Which Forks compiled 57 reports: 45 of them include a number, and the median of those numbers is 30 FPS. The mix they counted is 42 NVIDIA, 13 AMD, 1 Steam Deck and 1 unlabeled. I treat that median as a summary of those reports, not as a speed you will get.

The same compilation shows 60 FPS on high-end machines in the 9800X3D and RTX 5080 class, and on SmileyTatsu build 12 when docked on AMD. An RTX 3060 Ti note sits at 5–15 FPS with the resolution scale at 0.5x. A Steam Deck APU note for build 212 PGO calls the game unplayable. Handheld versus docked also changes an iGPU example: 60 handheld and 40 docked on a 780M. I am leaving those as separate machines.

Issue 341 is an AMDGPU kernel crash on RDNA3. Issue 370 is a MoltenVK crash on an Apple M4 while a pipeline is created, seen on builds 158 and 168. Issue 596 is a crash after loading on an RTX 50-series card with v0.1.0-rc1, the release whose title says DONT USE. Issue 558 is an infinite load when creating a Wireless Play lobby. A 0 FPS thread is also described in early crash reports: the game runs, drops to 0, returns to 60, then the emulator closes.

Builds named in the fix column are not magic versions. Build 77 is the VRAM note for cards that ran out of memory. Build 129 is tied to ASTC thread stalls. Build 135 is the note that trees stay drawn while the frame rate lost to the earlier tree fix is recovered. Build 158 is tied to present stalls and stale command lists. Build 212 is tied to NUP platform detection and Intel ANV banding. For a crash the moment a race starts, the older builds 73 and 64 suggested EDEN_NX2_SPARSE_LAZY=0. Frame generation and a 30 FPS cap show up because game speed follows the frame rate in these reports. I do not have a single “best settings” list from the project.