Analogue 3D 1.5.0: N64 Upscaling, 12 Builds Deep

1.5.0: The Purist Box Learns to Upscale

Analogue built its brand on a promise of not interfering. No scaling, no filtering, no interpolation — bit-perfect FPGA recreations of dead silicon that render what the original chips rendered and nothing else. Which is why there is a specific irony in the marquee feature of the twelfth Analogue 3D firmware build, shipped on July 21, 2026: the purist box now upscales your Nintendo 64.

Firmware 1.5.0 weighs 22.3 MB, carries the MD5 hash a00db9c90a2d8f09f25ec7f2d47c1802, and adds what Analogue calls Internal Graphical Upscaling — doubling the console's horizontal resolution inside the rendering pipeline before the picture ever reaches your television. Time Extension called it "A Game Changer." Whether it is a breakthrough or a quiet climbdown depends entirely on how literally you took Analogue's decade of purity theology.

The feature Analogue spent ten years not needing

Every prior Analogue product — the Nt Mini, the Super Nt, the Mega Sg, the Pocket — sold on the idea that the original output was sacred and any post-processing was heresy. The 1.5.0 copy keeps the liturgy intact: the upscaling "enhances detail and clarity while remaining faithful to the original hardware rendering process." Faithful, but sharper. The company found a way to add pixels and still call it purity, which is a sentence that makes a marketing department very happy and a pedant very tired.

What actually shipped on July 21

The upscaling is the banner, but 1.5.0 is a fat release. Alongside the doubled horizontal resolution — driven by "extensive enhancements to the RDP and VI," in Analogue's words — the build finally lands a proper RSP rewrite, makes save-state loading instantaneous, adds a "Recent Memory" startup action that boots you straight back to your last save, cleans up Gallery navigation, and fixes the 8BitDo N64 Modkit's simultaneous C-button and USB-rumble bugs. You enable upscaling under Settings > Advanced > Horizontal Upscaling, or toggle it live from the in-game menu to A/B the difference yourself.

Why the twelfth build is the one that matters

Eleven builds preceded this one, and almost all of them were plumbing: HDMI fixes, controller-pak logic, playtime counters, cartridge colors. 1.5.0 is the first update that changes what you actually see on screen. Andreas Sebayang at Notebookcheck summarized the release accurately: the 3DOS update "introduces numerous changes, the most significant of which is likely Internal Graphical Upscaling." Everything else on July 21 is housekeeping. This is the headline.

What Internal Upscaling Actually Does

"Upscaling" is a loaded word for a company that has spent years mocking upscalers, so it is worth being precise about what 1.5.0 does and — more importantly — what it does not do. This is not a sharpening filter bolted onto the HDMI output. It is a change to how the FPGA renders the frame in the first place.

Doubling horizontally, not stretching the output

Analogue's own note is unusually specific: "Resolution is doubled horizontally for twice as many pixels onscreen without affecting 2D graphics." The system increases the amount of visual information inside the graphics pipeline — the RDP (Reality Display Processor) and VI (Video Interface) do the extra work — before Analogue's Original Display Modes and HDMI settings take over. Polygon edges get cleaner, distant geometry gets more defined, and the characteristic N64 mush softens. Crucially, 2D elements — menus, text, HUDs — are left alone, so you do not get the awkward half-processed interface you would from a dumb post-filter.

Why horizontal and not vertical

The N64 was, in practice, a horizontally starved machine. Many titles rendered around 320 pixels wide, and the console's own anti-aliasing plus the composite cables of 1997 smeared what little detail there was. Doubling horizontally targets exactly the axis where N64 output looked worst, without touching the vertical scanline structure that the CRT purists — and Analogue's Original Display Modes — are trying to preserve. It is a targeted intervention, not a blanket one, and it is optional. Turn it off and you are back to the untouched image.

The catch: no independent testing yet

Here is the deadpan caveat. As of publication, essentially every write-up of the upscaling — including the enthusiastic ones — is working from Analogue's description and community capture videos, not controlled measurement. Nobody has published frame-by-frame comparisons across a broad game set proving the "no timing or performance hit" claim holds everywhere. It probably does; Analogue's track record on this hardware is strong. But "the manufacturer says it is free" is a claim, not a benchmark, and you should file it accordingly.

Twelve Builds in Eight Months

Strip away the individual features and the more remarkable story is the cadence. Analogue shipped its launch firmware on November 18, 2025, and by July 21, 2026 had pushed the console to its twelfth documented build. That is roughly one release every two to four weeks across the back half of the run, on a $250 box, for a library that stopped growing around 2002.

The full release table

Every version below is drawn from Analogue's official 3D firmware support page, the authoritative source for version numbers, dates, and patch notes. File sizes settled at 21.8 MB for most of the run, ticking up to 22.3 MB when 1.5.0's upscaling logic went in.

The pattern: fixes first, features later

Read the table top to bottom and the arc is obvious. The 1.1.x and early 1.2.x builds are triage — HDMI handshakes, corrupted OS graphics, GameShark support, controller-pak auto-selection, a playtime counter that overflowed past 24 hours. The back half is ambition: save states in 1.3.0, screenshots and a gallery in 1.4.0, upscaling in 1.5.0. Analogue spent the first four months making the console reliable and the next four making it do things the N64 never could.

What the pace says about the hardware

FPGA consoles are reconfigurable by definition — the logic is software describing hardware, so a firmware file can genuinely rewire the "chip." That is the entire pitch, and Analogue is now demonstrating it in public at a rate no emulation-averse purist expected. The flip side, said plainly: shipping a $250 console that needed eleven updates to reach "does what the box implied" is also a statement, and not an entirely flattering one.

Memories, Screenshots, and a Grown-Up OS

Two mid-cycle builds turned the Analogue 3D from a cartridge player into something closer to a modern console with a real operating system — one Analogue now brands "3DOS." Neither feature existed at launch, and both are things emulator users have taken for granted since the 2000s.

1.3.0: save states, branded "Memories"

Released May 15, 2026, firmware 1.3.0 added save states — but Analogue, allergic to the emulator vocabulary, calls them Memories. You get up to twenty per game; the oldest auto-deletes as you exceed the cap unless you pin it. It is the single most-requested feature for any retro platform, and its arrival on a "purist" FPGA box is another small crack in the no-compromises framing. 1.5.0 later made loading a Memory instantaneous and added the "Recent Memory" startup action.

1.4.0: screenshots, a gallery, and the WiFi it lacks

On June 23, 2026, 1.4.0 added screenshots and a built-in Gallery, capturing — per Analogue — "definitive recreations of original CRT displays, now captured for the first time in bit-perfect 4K HDR." You trigger a capture with the Star button on the 8BitDo 64 pad, Capture on an NSO controller, or Z+Start+R on an original pad. The obvious limitation: no wireless. Joseph Bradford at MMORPG.com put the frustration bluntly: "I do wish that the A3D had a WiFi feature so I could simply upload the screenshots direct from the console." Instead, you pull the microSD.

The library metadata nobody noticed maturing

Underneath the flashy features, the Library quietly became competent. 1.2.0 started tracking when each game was added and total playtime per title; 1.2.1 fixed the counter that broke past 24 hours and taught the system to auto-pick a Virtual Controller Pak or Rumble Pak per game; 1.2.6 added nine cartridge colors and made long titles scroll instead of truncating. Small stuff — but it is the difference between a tech demo and a device you actually live with.

The Flash-Cart Fix Nobody Announced Loudly

The most consequential update for a specific and vocal slice of owners was not a headline feature at all. It was a single line in the 1.2.4 patch notes — "Advanced Library detection for variable game headers" — that quietly solved a problem that had annoyed flash-cart users since launch.

Why multi-ROM carts broke the Library

The Analogue 3D reads real cartridges, and it treats each cartridge as one Library entry with its own saves, playtime, and controller-pak assignment. That model breaks the moment you insert an EverDrive 64 loaded with two hundred ROMs: the console saw one "cartridge," so every game you loaded collided into the same entry, sharing — and clobbering — the same save data. For anyone using a flash cart as their primary way to play, that was close to unusable.

What 1.2.4 changed

Released March 28, 2026, firmware 1.2.4 made the console read each ROM's header individually and spin up a separate Library entry per game. Rahim Amir Noorali at Notebookcheck reported that "switching between ROMs now automatically creates new entries," giving each game its own saves, its own rumble and controller-pak state, and its own playtime. The change was significant enough that third-party outlets covered it even though Analogue's own notes were characteristically terse.

What it means if you dump your own carts

The fix rewards a specific, legal workflow: dumping cartridges you own to clean ROMs. If you have a stack of N64 carts and a dumper, you can dump each cartridge to a verified ROM yourself, drop the files on a flash cart, and the 3D will now treat your personal library as a proper, per-game catalogue. It is the closest the console comes to endorsing flash carts — without ever saying the words.

The Cycle-Accuracy Fight Behind the Patches

You cannot understand the shape of this firmware run without the fight that ran alongside it. Weeks after launch, one of the most respected N64 homebrew developers alive took the Analogue 3D apart in public — and several of the patches that followed read like direct responses.

Kaze Emanuar's teardown

Kaze Emanuar, the developer behind some of the most technically aggressive N64 homebrew ever written, tested the console and did not mince words. Via Notebookcheck (December 22, 2025), his verdict was blunt: "This thing is nowhere near cycle accurate." His measurements put the console's CPU roughly 6% slower than real hardware and — the ugly one — its RSP about 30% slower, with the machine missing the ninth megabyte of RAM that the Expansion Pak provides. Time Extension ran its coverage under the headline "They Lied."

How the firmware answered

Watch the RSP language across subsequent builds. 1.2.3 touched RSP dual-instruction interlocks, CPU CP0, and VI timing. 1.5.0 went further, claiming "RSP scalar/vector interlock behavior fully implemented" and "RSP branch and dual instruction behavior fully implemented," plus a progressive-video jitter fix. That is FPGA logic being rewritten in the field to chase the exact accuracy gaps a critic measured — the reconfigurability pitch made literal. Kaze's follow-up numbers still showed roughly 5% overall lag and a game like Diddy Kong Racing running about 4% slower, so this is closing, not closed.

FPGA is not magic — the honest version

The takeaway is not that Analogue lied; it is that "FPGA" is not a synonym for "perfect." An FPGA recreation is only as accurate as the logic someone wrote, and the Analogue 3D shipped with real, measurable gaps against silicon that stubborn software emulators had already closed. The upside is that, unlike a chip, it can be improved after you buy it — which is precisely what twelve builds in eight months demonstrate.

How We Got Here: Analogue's FPGA Playbook

The Analogue 3D did not appear from nowhere. It is the latest and hardest entry in a decade-long project of FPGA recreations, and its troubled path to market explains a lot about why the firmware run looks the way it does.

From the Nt Mini to the Pocket

Analogue's back catalogue — the NES-focused Nt Mini, the Super Nt for SNES, the Mega Sg for Genesis, and the handheld Pocket — established the formula: license nothing, emulate nothing in software, describe the original chips in FPGA logic, and sell to people who care about the difference. Those were 2D machines with well-understood, comparatively simple silicon. The N64 was a different animal entirely. For the full corporate and technical history, Wikipedia's Analogue 3D page is a clean chronological reference.

Why the N64 was the hard one

The Nintendo 64 pairs a MIPS R4300i CPU with the Reality Coprocessor — an SGI-derived beast split into the RSP (audio and geometry) and RDP (rasterization) — plus a microcode system that let each game effectively reprogram the graphics pipeline. Recreating that in FPGA logic is an order of magnitude harder than an SNES, which is exactly why the RSP became the battleground for the accuracy fight above, and why the N64 had never received a credible FPGA recreation before. Even the console's crown jewels — the kind of games driving Nintendo's own Ocarina of Time remake plans — lean on quirks of that hardware that are miserable to reproduce.

The delayed launch and tariff pricing

Announced October 16, 2023, the 3D slipped repeatedly — from Q1 2025 to July, to late August, to Q4 — before finally shipping November 18, 2025 at an MSRP of $249.99. The first restock on November 24 already carried a tariff-driven bump to $269.99, per Engadget. The console pairs an Intel Cyclone 10 GX FPGA (roughly 220,000 logic elements) with 4K output over HDMI 2.1, including HDR and VRR — the horsepower headroom that made the later upscaling feature possible at all.

Analogue 3D vs Everything Else After Your N64

The 3D does not exist in a vacuum. There are at least four credible ways to play an N64 library in 2026, and the firmware run has quietly moved the 3D's position relative to all of them. Here is the honest comparison.

vs software emulation

RetroArch cores like ParaLLEl N64 and Mupen64Plus-Next, running on anything from a Raspberry Pi loaded with RetroPie to a gaming PC, have offered upscaling, save states, and shaders for years — the exact features Analogue spent 2026 adding. A Steam Deck that emulates the N64 in software will out-feature the 3D and cost more, but it renders through a modern GPU approximating the console, not through a recreation of its chips. That is the whole philosophical split: approximation with features versus recreation with fidelity.

vs MiSTer and original hardware

The open-source MiSTer project has an N64 core in active development on the DE10-Nano FPGA — cheaper in theory, hackable, community-driven, but fiddlier and less polished than Analogue's sealed appliance. At the other end sits the real thing: an original N64 on a CRT is, tautologically, perfectly accurate, because it is the hardware. It just can't output 4K, can't save-state, and increasingly can't find you a good CRT. The table below lays out the trade.

Where 1.5.0 leaves the 3D

Before this firmware run, the pitch for the 3D over a Steam Deck was "accuracy, at the cost of features." With save states, screenshots, per-ROM flash-cart libraries, and now upscaling, that gap has narrowed to the point where the 3D competes on features and fidelity — while still trailing raw software emulation on flexibility and price. It is a materially stronger product than the one that launched, which is the entire point of shipping twelve builds.

What the Critics Actually Said

The Analogue 3D reviewed well at launch and has only strengthened since, though the praise came with consistent asterisks about accuracy and the N64's own limitations. Here is the verified record.

The launch reviews

Tim Stevens at Engadget captured the consensus tension: "Your Nintendo 64 games never looked so good, but Analogue's greatest system yet can't fix some of the N64's inherent flaws." IGN's Seth G. Macy scored it 8/10, calling it "the best possible way to play your N64 library outside of the original hardware hooked up to a CRT." Wired's Matt Kamen went 9/10; GamesRadar+ said it "sets a new bar for retro console remakes," and Digital Foundry called it "the most impressive Analogue 'FPGA' console yet."

The developer community

The homebrew and preservation community was more skeptical, and its skepticism was productive. Kaze Emanuar's cycle-accuracy teardown, covered above, forced a real conversation about what "FPGA accuracy" actually means and — arguably — set the priorities for the RSP work in 1.2.3 and 1.5.0. That is a healthier dynamic than a review-score consensus: a critic measured a flaw, and the hardware got patched toward it.

The upscaling reception

1.5.0 landed to genuine enthusiasm — Time Extension's "A Game Changer," Notebookcheck flagging the upscaling as the release's most significant change — tempered by the honest gap noted earlier: the praise is running ahead of independent measurement. The community capture videos look good. A rigorous, broad comparison test has yet to be published, and until it is, "twice the pixels, zero cost" remains Analogue's claim rather than a verified result.

What Comes Next: 6-12 Month Predictions

Twelve builds in eight months is a trajectory, and trajectories can be extrapolated. None of the following is confirmed by Analogue; all of it is informed guesswork from the cadence and the gaps that remain. Treat it as such.

On the firmware roadmap

Expect the cadence to slow but not stop. The big-ticket items — accuracy, save states, screenshots, upscaling — are now shipped, so late 2026 likely brings a 1.5.x refinement line and a 1.6.0 that either extends upscaling (vertical passes, or per-game profiles) or adds display options nudging toward the shader territory Analogue has always disdained. I would bet that independent frame-analysis of the upscaling appears within three months and forces at least one corrective patch. The RSP work is not finished, either; another interlock-focused build before year's end is the safe money.

On the hardware ecosystem

The 8BitDo Modkit integration in 1.5.0 signals deeper controller partnerships ahead — expect broader third-party pad support and, plausibly, an Analogue-blessed wireless solution to answer the "no WiFi" complaint that screenshots exposed. Limited-edition colorways (Atomic Purple among them) will keep coming, because they are free money. A second hardware SKU or a Pocket-style successor is not a 12-month event.

On the market and pricing

The tariff pressure that pushed the restock to $269.99 is not going away, so expect effective street pricing to sit at or above launch MSRP rather than dropping — retro FPGA hardware does not discount like mainstream consoles. If Nintendo's own N64 offerings expand through Switch Online and remakes, the 3D's value proposition sharpens for owners of physical carts specifically, and blurs for everyone content with a subscription.

How to Install the Update in 6 Steps

Installing 3D firmware is deliberately low-tech: no accounts, no wireless, no launcher. You copy a file to a card and the console flashes itself. Here is the process, plus the recovery path for when a flash goes sideways.

The SD-card method

Download the build from Analogue's official 3D firmware page — the only authoritative source for the file and its checksum — and follow the steps below. Verifying the MD5 before you flash is optional but cheap insurance against a corrupted download bricking a boot.

# Analogue 3D 1.5.0 install (SD-card method)
1. Download the firmware .bin from analogue.co/support/3d/firmware
2. (optional) verify the download:
     md5sum 3D_1.5.0.bin
     expected  a00db9c90a2d8f09f25ec7f2d47c1802
3. Copy the .bin to the ROOT of the microSD card (FAT32/exFAT)
4. Insert the card and power the console on
5. Wait 3-6 min: yellow Power LED + blinking Controller LEDs
6. The console auto-reboots into 3DOS 1.5.0 when finished

The USB-C recovery method

If a flash fails or the console won't boot, there is a USB-C recovery mode: hold the reset and power controls together until the LED turns green, then connect over USB-C to re-flash. Do not pull power or eject the card during a normal flash — the three-to-six-minute window with blinking LEDs is the console writing its own logic, and interrupting it is the one reliable way to turn a $250 console into a paperweight.

What to do first if you're behind

If you have not updated since launch, you do not need to install every intermediate build — flashing 1.5.0 brings you fully current in a single pass. Do it before you complain about anything, because roughly every documented issue from the console's first eight months has been patched somewhere in the eleven updates between 1.1.0 and 1.5.0.