Analogue 3D Firmware 1.5.0: 12 Builds, N64 Upscaling

When Analogue shipped the 3D in November 2025, the pitch was hardware: a field-programmable gate array impersonating a Nintendo 64, feeding a modern television up to 4K over HDMI 2.1, region-free, cartridge slot intact. The pitch worked. Reviews landed between 8/10 and 9/10, the first batch sold out, and tariff-inflated restocks followed within a week. Then something more unusual happened. Analogue kept shipping — not hardware, software.

Twelve public builds of the 3DOS firmware went out between launch and the end of July 2026. The last of them, version 1.5.0, quietly did the one thing FPGA purists insisted the console would never stoop to: it upscaled the picture from inside the rendering pipeline. This is the story of that update, and the eleven that dragged it there — dated, decoded, and where necessary, doubted.

A Firmware Every Three Weeks

Twelve builds in eight months

Count them. The initial 3DOS release was 1.1.0 on 2025-11-18, the day the console shipped. The latest is 1.5.0 on 2026-07-21. Between those two dates sit ten more public builds: 1.1.9, 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 1.3.0, and 1.4.0. That is twelve releases across roughly eight months — a public drop, on average, every three weeks. For a premium sealed appliance from a company famous for going quiet after launch, that cadence is the actual headline. Analogue's official firmware page lists every one, complete with file sizes and MD5 checksums.

1.5.0 is the payoff, the cadence is the plot

It is tempting to treat 1.5.0's upscaling as the story and the rest as changelog noise. That reading gets it backwards. The upscaler only exists because Analogue spent eight months rewriting the console's internals in public — cartridge detection, RSP timing, HDR brightness, controller pak logic — until the pipeline was stable enough to double a horizontal line count without wrecking timing. If you want the deep technical teardown of the upscaler itself, we cover it separately in our 1.5.0 upscaling breakdown; here the interest is the arc.

Free, and delivered over an SD card

Every one of these builds is free and installed the same low-tech way: drop a .bin file onto the root of the microSD card, power on, wait. There is no WiFi, no over-the-air push, no account. That constraint — which the 3D shares with the rest of Analogue's line — turns out to matter later, when we get to the one feature owners keep begging for and still do not have.

Inside 1.5.0: Upscaling, Explained

Doubling the pixels, sparing the 2D

The headline feature of firmware 1.5.0 is Internal Graphical Upscaling, which Analogue describes as enhancing "detail and clarity while remaining faithful to the original hardware rendering process." Mechanically, the resolution is "doubled horizontally for twice as many pixels onscreen without affecting 2D graphics," with "no impact to timing authenticity or performance." This is not a sharpening filter bolted onto the HDMI output and it is not host-GPU trickery — there is no host GPU. It happens at the FPGA level, inside the reconstructed RDP and VI, before the frame is ever resampled for your panel. Menus, HUDs, and 2D interface elements are deliberately left alone, which spares N64 games the smeared-text look that afflicts naive upscalers.

The RSP rewrite buried in "Core Improvements"

Read past the marketing and the meat is in the Core Improvements list. 1.5.0 claims "RSP scalar/vector interlock behavior fully implemented" and "RSP branch and dual instruction behavior fully implemented," plus expanded progressive-video support that reduces jitter in select titles. Translated: Analogue rewrote large parts of how its Reality Signal Processor handles instruction ordering. That is not a cosmetic change — it is the kind of low-level accuracy work that the console's harshest critics said was missing at launch. The build weighs 22.3 MB (MD5 a00db9c90a2d8f09f25ec7f2d47c1802), a hair heavier than the 21.8 MB that most 1.2.x and 1.3–1.4 builds occupied.

OS and controller housekeeping

The quality-of-life additions are real but minor next to the upscaler: Quick Load for a Memory (Analogue's save state) is now instant; a new Recent Memory Startup Action boots you straight back into your last save; advanced overclock settings moved to a dedicated Advanced menu; and the 8BitDo N64 Modkit's simultaneous C-button bug and USB rumble were fixed. Notebookcheck's Andreas Sebayang summarized the priority correctly on 2026-07-23: "The latest version of 3DOS introduces numerous changes, the most significant of which is likely Internal Graphical Upscaling."

Every 3DOS Build, Dated

The launch baseline (1.1.0–1.1.9)

Version 1.1.0 established the launch software. Ten days later, 1.1.9 (2025-11-28) arrived with manual region selection, a "Disable Texture Filtering" toggle, and improvements to the baked-in Unleashed overclock tier — the aggressive mode that helps CPU-bound titles like Perfect Dark and GoldenEye 007. The overclock is not a hidden hack; it ships in four tiers (Auto, Enhanced, Enhanced+, Unleashed) and runs at Auto by default.

The 1.2.x sprint (January–April 2026)

After a holiday pause, Analogue sprinted. 1.2.0 (2026-01-30) patched HDMI problems, added Force Progressive Output, brought in Nintendo Switch Online N64 and wireless controller support, and force-disabled the Expansion Pak for Space Station Silicon Valley (USA) to dodge a game-breaking bug. 1.2.1 (2026-02-13) fixed playtime tracking past 24 hours and refined automatic Controller Pak/Rumble Pak selection. 1.2.2 (2026-02-27) added a Startup Action to boot directly into the inserted cartridge and a Power Off command. 1.2.3 (2026-03-13) fixed GameShark compatibility and cartridge detection and, notably, touched RSP dual-instruction interlocks and CPU CP0 behavior — the first hint of the timing work that 1.5.0 would finish. The full run continued through 1.2.4, 1.2.5, and 1.2.6.

The feature era (1.3.0–1.5.0)

Once the plumbing was stable, the marquee features came fast: save states in 1.3.0, screenshots and a gallery in 1.4.0, upscaling in 1.5.0. The table below dates every build; the full patch notes live on the Analogue firmware index.

Installing any of them is the same three-minute ritual, and Analogue publishes an MD5 for every build so you can verify the download before you trust it:

# Flash 3DOS (per analogue.co getting-started)
1. Download 3D-<version>.bin from analogue.co/support/3d/firmware
2. Copy the .bin to the ROOT of the microSD card (not a subfolder)
3. Insert card, power on the console
4. Wait 3-6 min: yellow Power LED + blinking Controller LEDs = flashing
5. Console auto-reboots -- do NOT pull power
# USB-C mode: hold Reset + Power until the LED turns green

# Verify your download (MD5, published by Analogue)
1.2.3  0ed9d8906f7cf68a740e424ef5598a41
1.2.5  5eaee5e0988dbc9dd69646d6e1829f34
1.2.6  47c05610e401c4bff29d3181ff204d9f
1.3.0  a24cc15d8a874872cc0773cbc1bdbbd3
1.4.0  b7cfc37a0b1d4c92698cd57990868f90
1.5.0  a00db9c90a2d8f09f25ec7f2d47c1802

The 1.2.4 Flash-Cart Fix

One cart, many ROMs, one confused library

Of the twelve builds, the one that generated the most trade-press attention was not a headline feature — it was 1.2.4 (2026-03-28). Before it, the 3D treated a flash cartridge such as an EverDrive 64 as a single Library entry, no matter how many ROMs lived on the SD card inside it. That meant one shared save file, one shared Controller Pak, one shared everything, across your entire flash-cart collection. For the substantial slice of buyers who run an EverDrive, that was a daily annoyance.

Advanced Library detection

1.2.4 introduced what Analogue calls "Advanced Library detection for variable game headers." In plain terms, the console now reads each ROM's header and gives it its own Library entry, with its own saves, rumble, and Controller Pak data. If you dump and load your own carts — a workflow we walk through in our cartridge-dumping guide — this is the update that made a flash cart behave like a shelf of individual games.

The verdict from the trade press

Notebookcheck's Rahim Amir Noorali framed it bluntly, noting that with 1.2.4 "switching between ROMs now automatically creates new entries." The outlet's headline called it a fix for "flash-cart headaches" — a rare case of a point-release changelog line mattering more to real owners than a marquee feature.

Memories, Screenshots, No WiFi

Save states, branded "Memories"

1.3.0 (2026-05-15) added save states, which Analogue markets as Memories — up to 20 per game, with the oldest auto-deleted unless pinned. Time Extension called it the console's most significant update yet at the time, and for good reason: save states on original hardware require a battery, a Controller Pak, or a mod, and here they arrive on cartridges that never supported them. 1.5.0 later made loading a Memory instant and added the Recent Memory boot option.

4K HDR screenshots and the Gallery

1.4.0 (2026-06-23) followed with screenshots and a built-in Gallery, capturing "definitive recreations of original CRT displays" in what Analogue bills as bit-perfect 4K HDR. Capture is hotkey-driven — Star on the 8BitDo 64 pad, Capture on the NSO controller, or Z+Start+R on an original.

The WiFi that isn't there

And here the SD-card constraint bites. You can screenshot in 4K HDR, but you cannot get the file off the console without pulling the microSD card and reading it on a computer. MMORPG.com's Joseph Bradford put the obvious wish on the record: "I do wish that the A3D had a WiFi feature so I could simply upload the screenshots direct from the console." There is no WiFi radio in the 3D. Software cannot add one. This is a hardware ceiling the firmware cadence will keep bumping into.

The Cycle-Accuracy Fight

Kaze Emanuar vs the FPGA

The most substantive criticism of the 3D came not from a reviewer but from a developer. Veteran N64 homebrew author Kaze Emanuar tested the console against real silicon and, via Notebookcheck in December 2025, concluded: "This thing is nowhere near cycle accurate." His numbers: the CPU ran roughly 6% slower than hardware, the RSP roughly 30% slower, and the implementation was missing the ninth megabyte of RAM that the N64's RDRAM exposes. For a $250 device sold on fidelity, that is a serious charge.

What the RSP notes are answering

Read the firmware history back in light of that critique and a pattern emerges. 1.2.3 touched RSP dual-instruction interlocks and CPU CP0 behavior. 1.5.0 claims RSP scalar/vector interlocks and branch/dual-instruction behavior "fully implemented," plus a progressive-video jitter fix. None of the patch notes name Kaze, but the timing and the targets read like a months-long answer to exactly the areas he flagged. Whether the RSP is now cycle-accurate, or merely closer, Analogue has not published independent benchmarks to prove.

Upscaling: claim versus test

Which is the caveat on 1.5.0 worth stating plainly. Every figure in the upscaling announcement — "twice as many pixels," "no impact to timing authenticity or performance" — comes from Analogue's own copy. As of this writing, no independent lab has published frame-timing captures confirming the zero-cost claim. Given that the same company shipped a launch product a respected developer called "nowhere near cycle accurate," the correct posture toward the upscaler's marketing is interested skepticism, not applause. If you want a platform where the accuracy debate is settled by open cores you can inspect, that argument runs through RetroArch's N64 cores and the MiSTer ecosystem, not a sealed box.

How Analogue Got Here

The FPGA doctrine

The 3D is not Analogue's first rodeo; it is the doctrine taken to its logical extreme. The company built its reputation on FPGA recreations — the Super Nt, the Mega Sg, the Pocket — that reimplement original console logic in reconfigurable silicon rather than emulating it in software on a CPU. The Analogue 3D is the first fully FPGA-based recreation of the Nintendo 64, built around an Intel Cyclone 10 GX with roughly 220,000 logic elements, and it is the first Analogue flagship whose entire value proposition rested on 3D hardware that is markedly harder to recreate than the 2D consoles that came before it.

The delay gauntlet (2023–2025)

Announced on 2023-10-16, the 3D then ran a two-year gauntlet of delays — Q1 2025, then July, then late August, then Q4 — before shipping on 2025-11-18. The N64 is a notoriously awkward machine to reproduce, and the slipping dates were the first sign that Analogue was still finishing the silicon-behavior work when it shipped. The dense firmware cadence since launch is, read charitably, the completion of that work in public; read less charitably, a product that went out the door early.

The $249.99 that wasn't $399.99

One correction worth making, because the wrong number circulates: the 3D's launch MSRP was $249.99, not the $399.99 sometimes quoted. A tariff-driven restock on 2025-11-24 nudged it to $269.99, per Engadget. The frequently-cited $39.99 is the separate 8BitDo 64 wireless controller, not the console and not an EverDrive. A real EverDrive 64 X7, if you want one, runs roughly $175–215 on its own.

Analogue 3D vs the Alternatives

Versus MiSTer

The FPGA purist's alternative is MiSTer, the open Cyclone V platform whose N64 core has been a long, halting work in progress. MiSTer wins on openness and breadth — one board plays hundreds of systems — but loses on N64 specifically: no real cartridge slot, ROM-from-SD only, and 1080p output rather than 4K. Turnkey MiSTer boxes such as the Multisystem 2 start around the 3D's price once you add cases and I/O, and they demand far more tinkering.

Versus real hardware plus a flash cart

The other alternative is the genuine article: an original N64, RGB-modded, feeding a scaler, with an EverDrive for your ROM library. This is the only option that is unarguably cycle-accurate, because it is the actual chip. It is also the option that outputs 240p/480i, needs a mod and a scaler to look clean on a modern panel, and costs real money in carts and adapters. The 3D exists precisely to skip that chain.

Versus software emulation

And then there is software emulation, still the cheapest path, running on hardware you already own. A tuned N64 core in a distribution like Batocera gives you shaders, save states, and any output resolution for nothing but the host machine's cost — at the price of input latency and per-game accuracy fiddling that the 3D handles at the hardware level.

What the Critics Actually Said

The launch verdicts

The launch reviews were warm but qualified. Engadget's Tim Stevens summed the tension up: "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 the 3D "the best possible way to play your N64 library outside of the original hardware hooked up to a CRT." GamesRadar+ went further, writing in its review that the console "sets a new bar for retro console remakes," while Digital Foundry called it "the most impressive Analogue 'FPGA' console yet." The Verge landed on "the perfect console for N64 collectors," and Ars Technica flagged the lack of openFPGA support as the notable omission.

The developer dissent

Against that chorus sat Kaze Emanuar's cycle-accuracy critique, which is the single most important dissent because it is the only one backed by comparative testing rather than impressions. It is also the critique the firmware has spent the most effort answering.

The firmware-era reappraisal

By mid-2026, the conversation had shifted from "is the hardware good" to "how far can the software take it." The upscaling in 1.5.0 is the clearest evidence that Analogue intends to keep raising the ceiling on a device many buyers assumed was feature-complete at launch — a genuinely unusual posture for sealed retro hardware, and one that rewards owners who keep flashing.

What Comes After 1.5.0

OpenFPGA stays off the table

First prediction: no openFPGA. The 3D's Pocket sibling opened its FPGA to community cores; the 3D has not, and Ars Technica's complaint about the omission has gone unanswered for eight months and twelve builds. Expect Analogue to keep the 3D a closed, N64-only appliance through at least mid-2027. The company has never retrofitted openFPGA to a cartridge flagship, and nothing in the cadence suggests a change of heart.

The cadence cools

Second: the every-three-weeks pace slows. Twelve builds in eight months is a launch-stabilization sprint, not a sustainable rhythm. Look for 1.5.x point releases tuning the new upscaler — likely a vertical or per-game option in response to testing — before any 1.6.0 feature drop, and expect the overall interval to stretch toward monthly or longer through the back half of 2026.

The features still missing

Third: no WiFi, ever, because the radio isn't in the box — screenshot export stays SD-card-only no matter how loudly owners ask. Fourth: independent testers will put the "no performance impact" upscaling claim under a capture card, and Analogue will ship a corrective 1.5.x if the numbers don't hold. Fifth: expect continued limited-edition colorway restocks and a held price of $249.99/$269.99 through holiday 2026, with tariff pressure making a cut unlikely. The color options already expanded to nine in-library cartridge shades back in 1.2.6; the physical SKUs will follow the same playbook.

The Bottom Line

Who 1.5.0 is for

If you already own a 3D, 1.5.0 is a mandatory, free flash: sharper output, instant save loading, and the most complete RSP timing work the console has shipped, all for the cost of copying a 22.3 MB file to an SD card. There is no argument against installing it.

The catch

If you don't own one, 1.5.0 does not change the underlying math. The 3D is still a $250 sealed box that a serious developer measured as meaningfully off cycle-accurate, still lacks openFPGA, and still can't get a screenshot off itself without a card reader. The upscaler's marquee claims remain Analogue's own, unverified by outside testing. The firmware cadence is impressive; it is not a substitute for independent measurement.

The Machine's call

What 1.5.0 proves is narrower and more interesting than "the 3D got better." It proves that a sealed FPGA appliance can be treated as a living platform, patched monthly toward a moving target of accuracy and features its buyers didn't pay for up front. That is the genuinely new thing here — not the doubled pixel count, but the fact that a company shipped a console in November and was still fundamentally rewriting its processor behavior the following July. For once, "we'll fix it in a patch" turned out to mean it.