Which build should you choose?
Start with the PGO package recommended in the release notes for your platform, if your CPU supports it. PGO means profile-guided optimization: the compiler uses a recorded workload to optimize the program. It does not add games, keys or firmware, and it does not make a game universally compatible.
The build 125 release notes explain that Windows PGO is trained on Ocarina of Time. Other games may benefit less. Linux uses an Eglantine profile. The macOS package in this release does not have a separate PGO option.
| Package | What the release notes say | Your next step |
|---|---|---|
| Windows x86-64 PGO | clang-cl, ThinLTO and an Ocarina of Time training profile | Try the recommended PGO ZIP, then compare standard if needed |
| Windows x86-64 standard | Same program without the PGO profile | Useful when the PGO build does not work for your setup |
| Linux PGO | Uses an Eglantine profile | Match both your CPU architecture and package format |
| macOS ARM64 | Apple Silicon package, no separate PGO listed | Follow the macOS requirements, not a Windows recommendation |
How do you compare them fairly?
- Read the release notes and record the build number. Compare PGO and standard from the same release before comparing unrelated builds.
- Follow the update and backup guide. Separate program directories do not necessarily mean separate saves or settings.
- Keep the game version, save, location, graphics options and driver unchanged.
- Record whether the problem is startup, shader compilation, gameplay frame rate or a crash. A first run with an empty cache can differ from a later run.
- If one build fails, keep its log before starting the other. Do not conclude that a profile improves every game from one successful title-screen test.
A useful comparison says, for example, “same build and settings, same save and scene, but this package crashes at the intro.” It does not need a broad claim such as “PGO is always faster.”
What if the recommended build does not launch?
Recheck the operating system and CPU architecture first. A Linux ARM64 build is not a Windows build, and the macOS ARM64 package does not establish Intel Mac support. Make sure the entire archive was extracted.
Then compare the standard package for the same release if available. Keep both program folders named clearly, and avoid changing graphics settings at the same time. If both fail, use the platform setup instructions to separate a launch problem from a game problem.
Where should you get the files?
Use the official download selector or go directly to the official GitHub releases. This page explains a release snapshot checked on 9 November 2026. Newer release notes take priority over this snapshot.