A technical exploration: can a Nintendo Switch game's NVN graphics be ported to Metal?
Tested with your own copies of Tears of the Kingdom and Breath of the Wild on Mac, iPhone and iPad. Not an emulator: the game's own ARM64 code runs directly on Apple chips.

English | 中文

You must own the game. Use this project only with games that you bought, and with keys and system files dumped from your own Nintendo Switch. This is an independent, non-commercial project. It is not affiliated with, endorsed by, or sponsored by Nintendo. The Legend of Zelda and Nintendo Switch are trademarks of Nintendo.

The repository contains no game content and distributes none: no game program, art, text, audio, shaders or keys. Everything the game needs is made on your own computer from your own files when you build the app. The app you build contains the game, so it is for your own use only; do not share it. What the repository does hold is the information needed to make the port work: the patch code, the addresses and hashes used to check your files, and the shared shader list, which names shaders and bind states but contains no shader code.

Apple, Mac, iPhone, iPad, Apple Vision Pro and Metal are trademarks of Apple Inc.; this project is not affiliated with Apple. Other game titles and trademarks named here belong to their respective owners.

Whether dumping games, keys and system files is legal depends on where you live; check and follow your local laws.

Issues and pull requests that contain or ask for game files, keys or firmware will be deleted.

This project is a technical exploration, mainly feasibility experiments and analysis. The Nintendo Switch is an ARM system (an ARM64 CPU in NVIDIA's Tegra X1), and Apple chips are ARM64 as well, so we want to test whether its games can, technically, be ported to Apple chips. It started from one question: can the NVN graphics a Switch game was written for be rebuilt faithfully on Apple's Metal, and can the game's own ARM64 code run directly on Apple chips without an emulator? Tears of the Kingdom and Breath of the Wild are the test cases, because they push the graphics API hard. The repository records the experiments, measurements and findings along the way; it is a study of the technique, not a game distribution. It does not encourage piracy: use only your own game data, dumped from a game you bought and from your own Switch, never game files, keys or firmware downloaded from the internet or obtained from anyone else.

How it works: bring your game file (XCI or NSP) and your prod.keys; one script builds a Mac app or an unsigned iPhone/iPad IPA. The game's own ARM64 code runs directly on Apple chips (rewritten where the operating system requires it), the Switch system services are answered by a small host, and the game's NVN graphics are rebuilt on Metal. The iOS build requires iOS/iPadOS 26 and iPhone 14 or newer; version 1.4.3 has been played on an iPhone 14 and an iPad, see iPhone and iPad. Details are in How it works.

Community ports keep their own runtime, graphics layer and scripts in their folder and are built with the steps there.

Recommended: let an AI assistant install and test it for you. Open this repository in Claude Code, Codex, or any other AI assistant you like, tell it where your own game file and prod.keys are, and ask it to build and install the app and to sort out whatever comes up on your Mac. It follows the install skill, runs every step and checks the result; you just wait with a coffee. Installing and testing by hand is not recommended: there are many steps, and every Mac, game version and dump is a little different. That's why I haven't provided a one-click build option: an AI assistant is my one-click build option.

The install skill (.claude/skills/install-zelda/SKILL.md) is a short guide written for the assistant: which of your files goes where, the command for your case, how long each step takes (a build is 20–40 minutes; it must not be stopped), and the fix for each common error. Claude Code finds it by itself (or type /install-zelda). With any other assistant, start with: "Read .claude/skills/install-zelda/SKILL.md and follow it to install Tears of the Kingdom for me."

The shared shader list now holds 13,422 shader variants (11,996 shaders) from the Mac, iPhone and iPad: only states a build does not make by itself, since every build makes each shader's default variant. Every build makes them from the player's own game files, so the list holds identifiers only, never game data. Helping takes no setup:

1. Play. Every build carries each shader of the game for its default bind state. When your game meets a shader in a state that variant does not serve, or builds a render pipeline the app's list lacks, it notes it in shader-list-contribution.txt; default variants are never noted.
2. On a Mac, every 100 new rows (shaders and pipelines together) it asks you once, before the game starts. Click "Send": the GitHub form opens and the file is shown, ready to drag in. If the GitHub CLI (gh) is installed and signed in, the dialog offers "Submit automatically" instead, which sends this batch for you (a private gist and an issue) without opening the browser. An iPhone or iPad never asks during play: while it is connected to the Mac that built its app (cable or the same Wi-Fi), the Mac asks instead. "Don't remind me again" stops the reminders.
3. Everyone's next build carries them. Nobody stutters there again.

Send your shaders → · The game never uploads anything by itself.

Stuttering when you first start playing or enter a new scene is expected while new shaders compile—don't be surprised. Performance typically improves as the cache warms up, and every shader the shared list gains is one nobody stutters on again.

Everything from building the app to playing is in docs/install.md. The recommended way is to hand it to an AI assistant with the install skill (see the top of this page) rather than run the steps yourself:

• What you need · Build the app · Breath of the Wild · iPhone and iPad · Apple Vision Pro
• Controls · Where things are · Known issues
• Test records

See docs/how-it-works.md.

Recorded performance experiments, remaining work and comparison methods: Mac performance follow-ups.

• d2r-mobile (MIT) developed this way of running Switch games natively (for Diablo II: Resurrected): the NSO rewriter, the Horizon host and the NVN-on-Metal layer here started as its generic parts.
• nxnative: the one-script packaging and NSP common-ticket import follow its approach.
• Ryujinx (MIT): its shader translator (vendor/ryujinx) turns the game's Maxwell shaders into SPIR-V, and its system-service code is a reference. With this project's patches and service it is compiled ahead of time (.NET NativeAOT) into games/totk/prebuilt/macos-arm64/totk_xlate; games/totk/tools/totk_xlate/publish_native.sh rebuilds it (needs the .NET 10 SDK, only for developers).
• SPIRV-Cross (Apache-2.0) turns SPIR-V into Metal Shading Language; it is fetched at a pinned commit and compiled with clang during the build.
• deko3d (zlib): texture layout sizes. bcdec: BC texture decoding. libopus and libvpx (BSD) from Homebrew: audio and the pre-rendered movies.

MIT (see LICENSE). Third-party code keeps its own license: THIRD_PARTY_NOTICES.md.

你必须拥有正版游戏。 请只配合你自己购买的游戏，以及从你自己的 Nintendo Switch 导出的密钥和系统文件使用本项目。这是一个独立的非商业项目，与任天堂没有关联，也未获其认可或赞助。The Legend of Zelda（塞尔达传说）和 Nintendo Switch 是任天堂的商标。

本仓库不含、也不分发任何游戏内容：没有游戏程序、美术、文字、音频、着色器或密钥。游戏需要的一切，都是打包时在你自己的电脑上、用你自己的文件生成的。打包出的 App 里含有游戏，只供你自己使用，请不要分享。仓库里有的是让移植能运行的信息：补丁代码、用来核对你的文件的地址和哈希，以及公共着色器清单（只记着色器和绑定状态的标识，不含着色器代码）。

Apple、Mac、iPhone、iPad、Apple Vision Pro 和 Metal 是 Apple Inc. 的商标，本项目与苹果没有关联。这里提到的其他游戏名称和商标归各自的权利人所有。

导出游戏、密钥和系统文件是否合法，取决于你所在地区的法律，请自行确认并遵守。

附带或索要游戏文件、密钥、固件的 issue 和 PR 会被删除。

这是一个技术探索项目，主要做可行性实验和分析。 Switch 是 ARM 系统（NVIDIA Tegra X1 里的 ARM64 处理器），苹果芯片同样是 ARM64，所以我们想测试：技术上能不能把它的游戏移植到苹果芯片上。它起源于一个问题：Switch 游戏所用的 NVN 图形接口，能不能在苹果的 Metal 上忠实地重建出来？游戏自己的 ARM64 代码，能不能不经模拟器、直接在苹果芯片上运行？《王国之泪》和《旷野之息》对图形接口的要求很高，所以用它们来检验。仓库记录的是这一路的实验、测量和结论；它研究的是技术，不是分发游戏。**本项目不鼓励盗版：**请只使用你自己的游戏数据，也就是从你自己购买的游戏和你自己的 Switch 导出的数据，不要使用从网上下载或从他人处得到的游戏文件、密钥或固件。

做法：准备好游戏文件（XCI 或 NSP）和你的 prod.keys，一个脚本即可构建 Mac App 或未签名的 iPhone / iPad IPA。游戏自己的 ARM64 代码直接运行在苹果芯片上（按操作系统要求改写），Switch 的系统服务由一个小宿主应答，游戏的 NVN 图形在 Metal 上重建。iOS 构建需要 iOS / iPadOS 26，最低支持 iPhone 14；1.4.3 已在 iPhone 14 和 iPad 上实际游玩，见 iPhone 和 iPad。详细见工作原理。

社区移植的游戏各自在自己的目录里带一份运行时、图形层和脚本，按那里的步骤构建。

推荐的安装测试方式：交给 AI 助理。 用 Claude Code、Codex 或其他你喜欢的 AI 助理打开这个仓库，告诉它你自己的游戏文件和 prod.keys 在哪，让它帮你打包、安装 App，遇到这台 Mac 上的问题也让它处理。它会按安装 skill 一步步跑完并检查结果，你只需要喝杯咖啡等着。不推荐自己手动安装测试：步骤多，每台 Mac、每个游戏版本、每份导出的游戏文件都有些差别。这也是我没有提供一键打包的原因：AI 助理就是我的一键打包。

安装 skill（.claude/skills/install-zelda/SKILL.md）是写给 AI 助理的简短指南：你的哪个文件放在哪个参数、你这种情况用哪条命令、每一步要多久（一次打包 20–40 分钟，中途不能停），以及常见报错各怎么解决。Claude Code 会自己找到它（也可以输入 /install-zelda）。用其他 AI 助理时，第一句这样说：“读 .claude/skills/install-zelda/SKILL.md，按它帮我安装王国之泪。”

公共着色器清单现在有 13,422 个着色器变体（11,996 个着色器），来自 Mac、iPhone 和 iPad：只收打包自己做不出的状态，因为每次打包都会给每个着色器做好默认变体。每次打包都用玩家自己的游戏文件生成，所以清单里只有标识，不含任何游戏数据。参与不需要任何设置：

1. 照常玩。 每次打包都会把游戏里每个着色器按默认绑定状态各备一份。游戏遇到默认那份用不了的状态，或者建了 App 清单里没有的渲染管线，才会记进 shader-list-contribution.txt；默认变体不记。
2. 在 Mac 上，着色器和管线合计每攒够 100 条，它会在游戏启动前问你一次。 点“发送”，GitHub 提交页面会打开，文件也会显示出来，拖进去就行。装了 GitHub 命令行工具（gh）并已登录时，对话框里会多一个“自动提交”，点了就直接替你把这一批发出去（私密 gist 加一个 issue），不用打开浏览器。iPhone 和 iPad 玩的时候从不提醒：设备连着打包它的那台 Mac（线连或同一 Wi‑Fi）时，由 Mac 来问。点“不要提醒了”以后就不再问。
3. 下次大家打包的 App 都会带上。 谁到那里都不会再卡顿。

发送你的着色器 → · 游戏不会自己上传任何东西。

第一次进入游戏或新场景时，新着色器的编译可能造成卡顿，这是预期现象，不必惊讶。 随着着色器缓存逐步预热，表现通常会改善；公共清单每多一个着色器，就少一处卡顿。

从打包 App 到开始游玩的全部步骤见 docs/install.zh-CN.md。推荐交给 AI 助理按安装 skill 去跑（见本页开头），不推荐自己一步步手动操作：

• 需要准备 · 打包 App · 旷野之息 · iPhone 和 iPad · Apple Vision Pro
• 操作 · 文件位置 · 已知问题
• 测试记录

见 docs/how-it-works.md。

已做的性能实验、待办与对比方法见 Mac 性能待做。

• d2r-mobile（MIT）为《暗黑破坏神 II：狱火重生》开发了这套原生运行 Switch 游戏的方法：这里的 NSO 改写器、Horizon 宿主和 Metal 上的 NVN 层都从它的通用部分起步。
• nxnative：“用户自己的游戏文件 + 一个脚本出包”和 NSP 通用票据读取的做法借鉴自它；本项目只构建 Mac App。
• Ryujinx（MIT）：它的着色器翻译器（vendor/ryujinx）把游戏的 Maxwell 着色器转成 SPIR-V，它的系统服务代码也是参考。加上本项目的补丁和着色器服务，用 .NET NativeAOT 预先编成原生程序 games/totk/prebuilt/macos-arm64/totk_xlate；改了翻译器用 games/totk/tools/totk_xlate/publish_native.sh 重编（要 .NET 10 SDK，只有开发者需要）。
• SPIRV-Cross（Apache-2.0）把 SPIR-V 转成 Metal 着色语言；打包时按固定提交取得，用 clang 编。
• deko3d（zlib）：贴图布局尺寸。bcdec：BC 贴图解码。libopus、libvpx（BSD，来自 Homebrew）：音频和预渲染影片。

MIT（见 LICENSE）。第三方代码保留各自的许可证：THIRD_PARTY_NOTICES.md。