Ocarina of Time Remake Graphics Setup: DLSS 5 Manager, ReShade Checks and Frame Generation
Recorded PC walkthrough · November 2026
Ocarina of Time Remake Graphics Setup: DLSS 5 Manager, ReShade Checks and Frame Generation
Start from a working base game, add one graphics tool at a time, and verify the relevant status before comparing the result. This companion guide separates the recorded Build 88 graphics session from the later Superbuild v12 frame-generation selection on the RTX 4070 SUPER system.
Builds, tools and community help
Use your own dump. If validation fails, share the exact error, file format and game version in our Discord. We can help you check the extraction. Back up existing saves before changing a working setup.
Keep a working base setup first
Use your own game dump. If validation fails, share its format, version and exact message in our community Discord for help checking the extraction. Back up your saves before changing builds. Check normal movement and camera control before adding an image effect or generated frames.
Record a repeatable baseline
Move Link and turn the camera with add-ons off. Note the application build, game mode and settings. Use the same route and camera movement for another pass. The video uses labelled recordings from different sessions; it is not a matched benchmark proving a numerical gain.
Install the recorded Manager option
Close the game, add the Lichii executable in DLSS 5 Manager, select Vulkan and install its Deep Fried Chicken option. The Build 88 footage shows that selection and the relaunch. Keep the names of the third-party tools attached to the setup rather than assuming a toggle alone proves the effect is processing.
Check ReShade and the Feed path
Open ReShade and inspect the Kernel and Feed configuration. The saved same-session log records successful neural callbacks, but it also records a motion-vector provider mismatch. For the Lumenite path, the Feeder documentation recommends provider 3. Check the current documentation, effect order and processed-frame status for the version you use.
If an effect makes the game close
The later Superbuild v12 session closes while effects are being changed. Reopening reaches the forest again. If the failure keeps returning only with an add-on, remove it and retest the working base game. Change one component at a time so you can identify which step introduced the problem.
Choose frame generation and verify activation
In Live Flow, enable multi-frame generation and select a multiplier supported by your setup. The v12 capture shows x2 selected while the status reads Starting. A selected multiplier is not a verified measurement of presented frames. Wait for activation and check presented output separately from the game counter.
Use the gameplay as a visual check
The walkthrough returns to the Build 88 session for camera turns, moving foliage, training movement and the route toward the sword. Use these scenes to decide what you want to inspect on your system, not as proof of a measured stable output rate. Keep the baseline settings so you can return to them.
Share a useful test report
When asking for help, include the build, GPU, Manager version, effect order, provider setting and exact status or error. Mention whether the base game works with add-ons removed. Our Discord is a place to compare those results and troubleshoot your own setup.
Video chapters
- 0:00 — Start with a playable baseline
- 0:23 — Check the game and your own files
- 1:10 — Make a short baseline pass
- 2:29 — Install the Manager for this executable
- 3:35 — Confirm that the effect processes frames
- 4:42 — If the add-on closes the game
- 5:29 — Select frame generation and verify status
- 6:35 — Judge motion along a familiar route
- 8:10 — Check the final result
Recording notes: Examples are from separate sessions with labels. Session logs show neural callbacks and a motion-vector provider warning. The v12 x2 selection shows Starting. Presented FPS was not verified. Use your own game dump. If validation fails, share the format, version and exact error in our Discord for help checking your extraction.
Background music in the video: Cybernetic Ride. Screenshots come from the creator’s recorded sessions. The software projects and their maintainers retain their own credits and licenses.
Comments
Post a Comment