New graphics options in the launcher, all off by default except supersampling (which only kicks in when the console mode is bigger than the screen).
What's in it
- 120 fps (
NX_METALFX=1): after every frame, the image and the 3D scene's depth go to MetalFX'sMTLFXFrameInterpolator, and the in-between image is shown half a frame before the real one (gfx::presentschedules both withpresentDrawable:atTime:). MK8D has no motion vectors, so they stay zero and MetalFX estimates the movement itself. Offline against real consecutive race frames, its midpoint is much closer to the real in-between frame than a blend (mean error ~9 vs ~15, repeating a frame is ~17). Menus aren't interpolated (no 3D depth buffer). Cmd+I toggles it while playing. Needs macOS / iOS 26. - Docked (1440p) console mode: like 4K, it patches the output size and memory budgets (values between 1080p and 4K).
- Supersampling: an image taller than the screen (4K on a 1440p display) is filtered down to the screen in linear light (box filter over each pixel's footprint) before interpolation and presenting, instead of a single bilinear tap in the present pass.
NX_SUPERSAMPLE=0turns it off. - Full resolution 3D (
NX_FULL_RES=1): gsys sizes its 3D render buffers as the output × 0.75 (main+0x6f7f2c). A load-time patch makes it 1.0, so the scene renders at the full output resolution. - High quality shadows (
NX_HQ_SHADOWS=1): the shadow map size comes fromdepth_shadow_tex_width/height(1024 / 1536), capped there (main+0x6d7834). The patch doubles the cap, giving 2048 / 3072 maps. - Performance HUD toggle (
MTL_HUD_ENABLED=1). - "60 fps split screen" is renamed "Full frame rate split screen" in the launcher, since with 120 fps on it gives 120.
- iOS launcher: a 120 fps toggle. The app asks ProMotion for 120 Hz (
CADisplayLinkwith a preferred frame rate range, plusCADisableMinimumFrameDurationOnPhone), because on its own the Metal layer stays at 60 Hz, and two presents per frame at 60 Hz halved the game speed. Interpolation also turns itself off when the screen can't do at least 100 Hz or Low Power Mode is on, on macOS too. Both launchers only show the 120 fps toggle when MetalFX can interpolate on the GPU (and, on iOS, the screen is ProMotion). On a Mac, a display running at 60 or 144 Hz (where 120 images a second can't be spaced evenly; measured on 144 Hz, every 5th image stayed twice as long) switches to its 120 Hz mode at the same resolution while the game runs, withkCGConfigureForAppOnly, so macOS restores it when Mush8 quits.
The two code patches live in loader.rs (QUALITY_PATCHES). Each one checks the words it replaces first, so another game version is left untouched. They write the game's code at load time, so they are macOS only (iOS can't change its signed, linked-in modules).
Tested
On an M2 Max, macOS 27, external 1440p monitor at 120 Hz:
tools/race-bench.shwith each option and with everything on at once (4K + full res 3D + HQ shadows + supersampling to 1440p + 120 fps): the game holds 60 fps.- With everything on, GPU time is about 4 ms for the game plus 6 ms for MetalFX per frame.
- A screen capture at 120 Hz shows 120 distinct images per second with interpolation on, and about 60 without.
- 4-player split screen works with full res 3D, full frame rate split screen and 120 fps.
- Default settings are unchanged.
- iPhone 17 Pro Max: 120 fps on, the game holds 60 fps with interpolation running.
Caveats
- Interpolation artifacts: transparent effects (boost flames, sparks) can't be interpolated cleanly, so they look like 60 fps.
- One unexplained stall: one run with everything on had a single 1 s hitch mid-race. It didn't come back in the next runs.
🤖 Generated with Claude Code
Activity
9thanks! done:
- rebased on main.
gfx::presentnow takes a slice of images: empty is a held frame from #30 (paced, nothing shown), one is a normal frame, two is the in-between image plus the real one. Held frames don't go to the interpolator. QUALITY_PATCHES/quality_patchesare behindcfg(target_os = "macos"), soNX_FULL_RES/NX_HQ_SHADOWSin env.txt do nothing on iOS. The iOS launcher never showed those two options, only the 120 fps toggle.- comments removed with
tools/strip-comments.py(only the 2 line header is left, also in the newfi.rs/downscale.rs).
macOS build, iOS cargo check, cargo test --workspace and both launchers' Swift typecheck are clean.
hey thanks for the update ! quick question before i look at it again : whats the point of the 120 fps part ? the game still runs at 60, metalfx just fills in a guessed image between two real ones. so the real frame shows up half a frame later (more input lag in a racing game), and boost flames / sparks come out wrong. it doesnt really feel like 120 to me, just smoother looking. is there something im missing ?
You understood it correctly, yes. The frame lag is milliseconds so not much. But yes you are right, it's a bit smother, not more. I personally like it
hey this is really cool, thanks ! one blocker before i merge : quality_patches in loader.rs writes the game code at runtime (mem::protect RW then RX). thats fine on macos but iOS cant do it (no jit, the modules are linked in and signed), so NX_FULL_RES / NX_HQ_SHADOWS would crash there if someone sets them in env.txt. can you limit them to macos (cfg(target_os = "macos")) and hide those options on iOS ? or move them to GAME_PATCHES in nxpatch if you want them on iOS too. also it needs a rebase on main now (#30 changed present() too), and no comments in the code pls, the project is comment free (only the 2 line header). thanks !