Summary:
The Legend of Zelda: Ocarina of Time remake for Nintendo Switch 2 lists AMD’s FidelityFX Super Resolution 1.0 (FSR 1.0) and SMAA in its licence notices, while Nvidia’s DLSS does not appear. That single detail matters because it tells us which upscaling and anti-aliasing tools ship with the game code, and it helps explain some of the visual traits players have noticed in trailers and hands-on footage. Digital Foundry’s technical read of the gameplay footage also measured a 1080p gameplay target at 60 frames per second and observed image sharpening and shimmering foliage. In practical terms, the FSR 1.0 choice points toward a spatial, low-overhead upscaler that is cheaper to run than modern temporal solutions but recovers less fine detail. For Switch 2 owners and Zelda fans, that trade-off will shape perceived clarity, foliage shimmer, and how stable the frame rate feels during demanding scenes. Read on for a clear breakdown of what FSR 1.0 and SMAA mean for this remake, why Nintendo might skip DLSS, and what players should expect at launch.
What the licence notice of The Legend of Zelda: Ocarina of Time actually shows
The licence screen that has circulated online for the Switch 2 version lists “FidelityFX Super Resolution 1.0 (FSR)” along with a mobile-optimised Edge Adaptive Spatial Upsampling (EASU) implementation and SMAA for anti-aliasing. Seeing those names in the copyright and licence list indicates that the game ships with AMD’s spatial upscaling code and SMAA libraries embedded. A licence notice does not map one-to-one to how or when the tech is used in-game, but it’s reliable for confirming what third-party components the build includes. Because the Switch 2 is capable of supporting Nvidia’s DLSS on a hardware level, the absence of a DLSS entry in the same list is notable and offers a concrete starting point for understanding Nintendo’s implementation choices for the remake.
Why the specific names matter to players
Names like FSR 1.0 and SMAA are not just technical labels – they hint at performance and image characteristics you will actually notice while playing. FSR 1.0 is a frame-by-frame spatial upscaler that expands a lower-resolution render into the display resolution without referencing prior frames. That makes it computationally cheap and easy to integrate into engines that do not expose motion vectors. SMAA is a post-process anti-aliasing method designed to clean up jagged edges with low performance cost. Together, they usually mean a game aims for stable frame pacing while relying on sharpening and edge processing to preserve perceived clarity. The trade-off is that thin geometry, like grass and leaves, can look less detailed or shimmer more than when temporal methods are used.
How FSR 1.0 differs from DLSS and FSR 2.x in practice
FSR 1.0 is a spatial algorithm that treats each frame independently, while DLSS and FSR 2.x use temporal data – information from previous frames – to reconstruct finer detail and reduce noise. Temporal upscalers generally require motion vectors and extra engine support, but they can recover more detail and smooth out flicker on thin geometry. DLSS specifically uses neural reconstruction on Nvidia hardware and can produce high-quality results, but it relies on vendor-provided libraries and models. FSR 1.0 is more engine-agnostic and easier to retrofit into titles that weren’t built with temporal upscaling in mind. In short, spatial upscaling is lighter and simpler; temporal upscaling is heavier but usually better at keeping small, moving details consistent across frames.
What that means visually
On a visual level, expect the FSR 1.0 route to deliver a crisp look in big, static objects and UI elements while struggling more with fine, moving details. Things like grass, thin branches, and distant foliage are where spatial upscalers can reveal their limits. Players may see extra sharpening applied to counteract softness, which can create a slightly “over-processed” look in screenshots or footage. SMAA helps with edge aliasing but does not address temporal instability, so moving scenes can still exhibit flicker or shimmer. For many players, the trade-off is acceptable if it keeps the frame rate stable at 60 frames per second, but those who watch for pixel-level fidelity may be disappointed compared to what DLSS or FSR 2.x can achieve.
What Digital Foundry’s analysis adds
Digital Foundry studied the gameplay footage shown by Nintendo and reported a 1080p gameplay rendering target at 60 frames per second, with menu screens sometimes reaching higher internal resolutions. Their technical read did not find evidence of DLSS being used in the footage, and they noted sharpening artifacts and vegetation shimmer in places. That observation lines up with a build that uses a spatial upscaler and simple anti-aliasing, exactly what the licence listing suggests. While footage analysis is not the same as testing the final retail build, it provides valuable clues about render targets, frame pacing choices, and likely visual compromises the team made to balance fidelity and performance on the Nintendo Switch 2.
Possible technical reasons Nintendo might avoid DLSS
There are several plausible reasons Nintendo could ship a first-party title without DLSS. One common reason is engine compatibility – temporal upscalers typically require motion vector support and other rendering hooks that older or heavily modified engines might not provide without significant rework. If the remake is built on an internal engine or an older codebase adapted for modern hardware, adding temporal upscaling could mean weeks of engineering work and potential frame-pacing regressions. Another factor is control – first-party teams often prefer to use open or in-house tools so they can tune algorithms precisely for the target hardware. Finally, development schedules and priorities can favour stable 60 fps performance over squeezing extra resolution out of temporal methods – a choice many Nintendo teams have historically made to keep gameplay smooth.
How engine history shapes implementation choices
Many recent first-party projects that started life on earlier hardware or reused legacy systems have similar constraints. Bringing motion vectors, updated lighting passes, and temporal framework support into a codebase can be non-trivial, especially when the primary goal is to recreate a classic experience faithfully while improving visuals. If the development team prioritised reach and polish across the game over adopting a newer upscaler, FSR 1.0 offers a lower-risk way to get good-looking frames with predictable performance. That pragmatic approach lines up with what we’ve seen in other Nintendo-built Switch 2 releases, and it explains why the licence list names FSR 1.0 and SMAA rather than DLSS.
How this choice echoes in other Nintendo titles
Nintendo has several Switch 2 titles that opted for FSR 1.0 and SMAA or other non-DLSS solutions. Those choices have set expectations for visuals and performance on first-party releases, and players familiar with recent Nintendo launches may recognise similar sharpening and foliage behavior across multiple games. That pattern helps explain why fans and technical analysts immediately picked up on the licence listing: it matches a trend rather than being an isolated decision. For readers who want broader context about Nintendo’s Switch 2 firmware, updates, and first-party coverage, we link to our ongoing Switch 2 coverage page for background and related discussions at Nintendo Reporters News.
What players should expect at launch
Expect solid 60 fps gameplay in most situations, combined with occasional visual trade-offs where spatial upscaling meets dense foliage or fast camera motion. The overall presentation will likely impress for its faithful art direction and lighting, but pixel-fidelity purists may notice shimmering leaves and slightly over-sharpened textures in motion. For many players, the playable feel – input responsiveness, consistent framerate, and animation quality – matters more than micro-details in foliage. Nintendo tends to prioritise the play experience, so if FSR 1.0 helps the team guarantee a stable frame rate across the game, that will likely have been a deliberate design decision aimed at preserving the remake’s nostalgia while upgrading visuals.
Tips for players who care about image quality
If you’re sensitive to shimmer or want the cleanest image possible, consider experimenting with TV or monitor settings such as motion smoothing, sharpening, or other postprocessing options. The system output mode – docked 4K downscaled versus native docked 1080p, or handheld mode – can change how scaling artifacts appear. Keep an eye out for post-launch patches too; Nintendo and partner studios sometimes tweak anti-aliasing and upscaling parameters after release. Finally, discussions in the community and technical analyses from groups like Digital Foundry often reveal hidden options or performance modes that surface only after players and experts spend time with the retail build.
Conclusion
Nintendo’s licence listing for The Legend of Zelda: Ocarina of Time remake naming AMD FSR 1.0 and SMAA gives us a practical insight into the game’s rendering approach. That combination points to a spatial, low-cost upscaling pipeline favouring predictable performance over the extra detail that temporal methods can recover. Digital Foundry’s footage analysis aligns with those findings, showing 1080p gameplay at a locked 60 fps with some sharpening and foliage shimmer. For fans, the most important takeaway is that Nintendo appears to have chosen a familiar, pragmatic route that prioritises consistent playability on the Switch 2 while accepting some visual compromises. If you care about tiny details, watch the technical breakdowns after launch – those will show exactly how the game balances resolution, upscaling, and anti-aliasing in real play conditions.
FAQs
- Does the licence notice prove the game uses FSR 1.0 in every mode?
- No – a licence proves the code ships with the build, but it does not prove how or when the upscaler runs. Footage analysis and retail testing are needed to confirm runtime behaviour.
- Why not just add DLSS later if Nintendo wants it?
- DLSS requires engine support for temporal reconstruction and may need motion vectors and other hooks. Retrofitting those systems can be time-consuming and risk regressions, so teams weigh the cost against the benefits.
- Will FSR 1.0 cause big frame drops?
- FSR 1.0 is lightweight and chosen because it avoids heavy performance costs. It’s more likely to help maintain stable frame rates than cause drops, though other factors in scenes can still impact performance.
- Can post-launch patches change the upscaler or AA?
- Yes, developers can patch rendering pipelines post-launch. Nintendo and partners have updated graphics settings in prior releases, so future tweaks are possible if needed.
- Where can I read more technical analysis about this remake?
- Technical outlets like Digital Foundry publish breakdowns, and wider coverage of Switch 2 tech can be found through our dedicated Switch 2 hub and our news section.
Sources
- Zelda: Ocarina of Time on Switch 2 appears to skip DLSS for AMD’s 2021 upscaler, Notebookcheck, November 2, 2026
- Zelda auf Switch 2: Lizenzhinweise nennen ausgerechnet FSR 1.0, PCGamesHardware, November 2, 2026
- Digital Foundry: What have we learned about the Ocarina of Time Remake?, Digital Foundry, June 15, 2026