For two decades, VR forgot this Zelda
For two decades this game has been the Zelda that ages best and the one that VR forgot. The cel-shaded Great Sea still looks like a watercolor that learned to move, and the sailing still teaches patience better than most open worlds released since. Nintendo never built a VR version — not on Labo, not on Quest, not anywhere — so the headset treatment arrives the only way it ever does for a Nintendo game this old: from the community, in two completely different shapes.
Two ways in, neither of them official
The headline path is a PCVR build called ZeldaWWHDRecomp-VR. It’s an OpenXR fork of the Wind Waker HD static recompilation port — the project that translates the Wii U game’s PowerPC code to native C and runs it on Vulkan with no emulator in the loop. Because OpenXR is wired into the renderer rather than hooked over a finished frame, the stereo image is composed per-eye from the actual scene geometry. You need a Windows PC, a Vulkan runtime, and your own Wii U disc image or Cemu archive to feed it. The Meta Quest Link app is the documented runtime, and SteamVR and Virtual Desktop provide runtimes too but were untested by the author.
The VR fork ships as source only.
That last sentence is the whole setup story. There is no installer, no release zip, no pre-built binary on the fork’s page. You clone the repo, leave the WWHD_OPENXR CMake option on (it defaults to on for Windows), and compile it yourself with Visual Studio and the Vulkan SDK. If “build a game engine fork from source” sounds like your kind of Saturday, great. If it sounds like a tax form, the second path exists for you.
The second path is WakerQuest, a Quest 3 and 3S standalone port built from the GameCube original’s C++ decompilation. No PC, no Link cable — an APK and your own uncompressed GameCube ISO. I’ll get to it below, because the two builds ask completely different things of you.
You are the camera, not Link
This stays a third-person game.
The fork puts you where the game’s camera already sits — floating behind Link as he moves — and then layers your head’s actual movement on top. Look around freely, lean, stand up, and the world tilts with you while the horizon stays level. That’s a design decision, not luck: the author deliberately drops the camera’s own up-and-down tilt, because a view that pitches without your head doing so is exactly what makes people queasy in third-person VR. Recentering is a button press, and a world-scale slider sets how life-sized the sea feels around you.
What makes this fork more than a floating window is what your hands do. The right controller aims the bow, hookshot, boomerang, telescope, Picto Box, and grappling hook by tracking its own orientation — point, and the item fires where you’re pointing, not where a stick decides. The left controller carries the GamePad screen: click the stick and a tablet stands up off the controller like it’s mounted there, and the right trigger becomes a finger that taps and drags on it instead of pressing ZR. Rumble runs on both controllers. For a game whose entire inventory lived on a second screen, having that screen physically in your left hand is the single most VR-native idea in either 2026 route.
The body you don’t get matters as much as the body you do. You are not Link. There is no sword in your hand, no first-person legs, no embodied swing. You’re a particularly mobile cameraman with excellent aim and a tablet. That’s the honest ceiling of the experience, and it’s higher than it sounds — being inside the Great Sea’s light is its own reward — but don’t come expecting to duel Ganondorf with your own blade.
The performance wall is real
Now the part that’ll decide whether you actually play this: it runs slow. On the machine it was built on, Outset Island — about 5,000 draw calls a frame — landed at 27 to 29 frames per second through a Quest 2 over Link, with the game itself running at 91 to 98 percent speed whenever a frame took longer than a simulation step. That’s not a stutter you can ignore; that’s the floor on a quiet starting island, before the sea opens up and the draw count climbs.
Resolution is the lever you pull against it. At 1x internal scaling the image is soft across the roughly 100 degrees of view a headset gives you; bumping to 2x — 2,560 pixels — gets you close to what a Quest 2 panel actually shows, but it costs you frames you don’t have. So you’re choosing between soft and slower, or sharp and slower still.
Two smaller things to know. A handful of flat 2D elements — the title-screen boat, the logo, a few UI bits outside the game’s layout system — are drawn flat in each eye and don’t line up in depth, so they float wrong. And full-screen effects like heat haze, depth of field, and fade edges are computed per eye, so they can look slightly different between your left and right eye. Neither breaks the world; both remind you this is a renderer bent into VR rather than built for it.