iOS 16.1/17 compatibility fork

Requirements

• Use ios16-ios17-compat, the renamed and maintained compatibility branch; main remains the upstream baseline and old branch names or tags are archives.
• Legacy builds target iOS / iPadOS 16.1+, with separate a10x and m2 GPU targets. Metal 4 builds require iOS 26 and are experimental; one IPA does not cover both paths.

Get started

1. Open the branch and read docs/fork-status.md for the current game and device validation matrix.
2. Select the legacy or Metal 4 renderer and the matching device target. The documented selectors are DM_IOS_RENDERER and DM_LEGACY_TARGET.
3. Follow that branch’s build documentation with your own files and keys. Freeze the source revision and rebuild matching shader resources for each game.
4. Package for the selected target and test on that device. Record gameplay and picture results separately from build or installation success.

Usage & troubleshooting

• As of 2026-11-01, users report playable Animal Crossing on M2 and Witcher 3 on an M2 iPad with iPadOS 16.1 at about 30 fps, though picture anomalies remain possible. Need for Speed is also user-confirmed on M2, with intermittent scenery artifacts and audio stalls still open.
• Pokken’s picture is restored on M2 but long-run and A10X results are not certified. Arceus has a restored third-person picture on one Air system, while a reproducible task-end crash and the A10X layered-resource audit remain open.
• Pokémon Z-A packages have been installed, but that does not establish every scene or device. There is no verified Switch 2 iOS target. A10X has unresolved layered-rendering and sampler paths in several games.
• Modern frame interpolation is experimental. The project does not claim stable 120 fps or universal older-device compatibility; build and packaging success is not a playability result.