Selevet Ocarina of Time Remake: Supplied Build-67 Files and Dungeon Gameplay
Recorded walkthrough · 6 November 2026
A guide to the supplied Selevet build-67 Zelda-9 package for the Ocarina of Time remake on PC, followed by permitted dungeon gameplay from Finn Benchmarks. Includes the actual package files and build identity.
Build-specific guide: use your own compatible game and console files. Keep a working backup when trying another build.
Identify the supplied archive
The community resource is this Tools & Guides post. New members can join the server here first. The supplied filename is Selevet build 67 zelda 9 downloads.rar. The inspected version note calls it a build-67 Zelda-9 diag3 variant; it is not the public performance-6 archive.
Keep the extracted files together
Download the archive from the resource post and extract it into its own new folder. The inspected folder contains selevet.exe, nx2_switches.txt and VERSION.txt. Keep these files together and separate from a working Lichii installation. Read the notes before launch: the supplied switches include frame-dump diagnostics and paths that may not suit another machine.
Use an already prepared compatible profile
You need your own compatible game and required console files. This guide identifies the package and describes the launch checkpoints; it is not a fresh-PC prerequisites test. Open the executable, select the compatible Ocarina package through the application’s game-loading interface, and allow preparation to finish. At the menu, start a new game or continue a compatible save.
Understand the gameplay evidence
Dungeon footage comes from Finn Benchmarks’ permitted Selevet demonstration. The source video’s title identifies RTX 5080 + 9800X3D hardware, and its application title identifies a Selevet performance variant. Its configuration is distinct from the supplied diag3 archive and the locally recorded Lichii build 75. The video shows traversal, combat and equipment use; it does not prove that every package/configuration reproduces those results.
Compare useful checkpoints
Look for a visible world, responsive movement, working camera controls and progress through a familiar area. Keep the executable’s version with screenshots when comparing results. Do not copy a shader rejection command from another renderer just because the symptom looks similar.
Resources and community
For community setup help and build comparisons, join ItsOOGWAY on Discord. Include the exact build and the symptom you see; this is a community, not official upstream support.
Comments
Post a Comment