Analogue 3D 1.5.0: N64 Upscaling, 12 Builds Deep

On 21 July 2026, Analogue posted a 22.3 MB file to its support server — 3DOS 1.5.0, MD5 a00db9c90a2d8f09f25ec7f2d47c1802 — and for the first time since the console shipped in November 2025, the headline is not a bug fix. It is a capability the Nintendo 64 never had at the silicon level: internal graphical upscaling. This is the twelfth firmware build in roughly eight months, on a $249.99 console that plays original cartridges, and it is the first one that changes what the hardware actually draws.

1.5.0 Lands, and It Touches the Pixels

Analogue does not do launch events for firmware. It posts a binary, a date, and an MD5, and lets the release notes do the talking. The 1.5.0 notes talk more than usual. For eight months the 3D's changelogs read like a triage board — HDMI handshakes, corrupted OS graphics, playtime counters. 1.5.0 reads like a feature announcement.

The one line that matters

Buried under General Features is the sentence Analogue wants you to read: internal graphical upscaling doubles horizontal resolution without affecting 2D graphics, with no timing or performance impact. In plain terms, the console now renders twice as many pixels across each scanline inside the graphics pipeline, before the frame ever reaches your TV over HDMI. It is not a sharpening filter and it is not a TV-side scaler. You toggle it under Settings > Advanced > Horizontal Upscaling, and it composites with every one of Analogue's Original Display Modes.

What else shipped in the box

1.5.0 is not a one-trick release. Quick Loading makes save-state loads instant; a new Recent Memory startup action boots you straight back into your last save on original cartridges; and Gallery screenshots now flow through the new upscaling pipeline. There is also a pile of controller plumbing — restored USB rumble and simultaneous C-button support for the 8BitDo N64 Modkit, which needs its own firmware 1.04 or later — plus the two lines that matter most to the accuracy crowd, which we will get to.

Why a hash belongs in a news story

Analogue publishes an MD5 for every build, and 1.5.0's is a00db9c90a2d8f09f25ec7f2d47c1802. That is not trivia. Firmware for these consoles is a single binary you drop on an SD card, and a corrupted copy can strand the box mid-flash. Verifying the hash before you write is the difference between a five-minute update and a support ticket. The company has earned some trust here — twelve clean builds, no bricking scandal — but the discipline is worth keeping.

Twelve Builds in Eight Months

The cadence is the story. Analogue shipped the Analogue 3D on 18 November 2025 and has not stopped since. The pattern is legible: compatibility triage first, quality-of-life second, platform features third. Here is the whole run as listed on Analogue's own 3D Firmware page, with the headline change for each build.

The compatibility era (1.1.0 to 1.1.9)

Launch firmware 1.1.0 got the console out the door; 1.1.9, ten days later on 28 November 2025, was the first real patch — manual region selection, a Disable Texture Filtering toggle, tightened overclock behavior, and library stability. That set the tone: Analogue treats the 3D like a live platform, not a sealed appliance. It is the same doctrine that keeps a modern console patched, applied to a box whose entire selling point is that it recreates 1996 hardware in logic gates.

The 1.2.x grind (January to April 2026)

Eight builds carry the 1.2 prefix. 1.2.0 fixed HDMI handshakes, a corrupted-OS-graphics bug, and a specific Expansion Pak fault in Space Station Silicon Valley (USA), while adding Force Progressive Output and Nintendo Switch Online N64 controller support. 1.2.1 corrected playtime tracking past 24 hours — the kind of unglamorous bookkeeping that tells you someone is actually reading bug reports. Builds hovered around 21.8 MB through this entire run, which is itself a tell: the core logic was stable and Analogue was iterating on behavior, not rebuilding the machine.

The feature jumps (1.3.0 to 1.5.0)

Then the platform started to grow. 1.3.0 on 15 May added save states. 1.4.0 on 23 June added screenshots and a Gallery. 1.5.0 on 21 July added internal upscaling and pushed the binary to 22.3 MB — the first size jump in months, which lines up with new graphics-pipeline logic rather than a behavioral tweak. Three consecutive minor-version bumps, each a genuinely new capability. This is not a company winding down support.

Internal Graphical Upscaling, Decoded

The N64's graphics live in the Reality Coprocessor: the RSP, a MIPS-derived vector unit running graphics and audio microcode, feeds the RDP, the rasterizer, and the Video Interface — the VI — scans the framebuffer out to the display. Analogue's changelog says 1.5.0 adds RDP and VI enhancements for upscaling support. That placement is the entire point.

RDP and VI, not a TV scaler

Because the doubling happens at the RDP/VI stage — inside the emulated console — the extra horizontal samples exist before any HDMI scaling. That is categorically different from what a modern TV or an external upscaler does downstream. As Time Extension framed it, the system increases the amount of visual information before the picture reaches your television. Polygon edges gain definition; the soft, blurry N64 look tightens up without a generic sharpen pass smearing the whole frame.

Why the 2D layer is left alone

The design constraint that makes this defensible: 2D graphics are untouched. HUDs, text, and pre-rendered sprite work — the elements that look wrong the instant you stretch them — bypass the upscaler entirely. This is the same philosophical line Sony walks with PSSR, and we covered the machine-learning version of that argument in our look at the PS5 Pro's PSSR rollout. Analogue's approach is dumber and more honest: deterministic horizontal doubling, no neural guesswork, no invented detail that was never in the source.

The no-performance-hit claim, examined

Analogue states there is no timing or performance impact, and on an FPGA that is plausible in a way it never is on a CPU — you are not stealing cycles from a shared processor, you are widening a parallel datapath. But plausible is not proven. Notebookcheck's Andreas Sebayang called the feature likely the most significant change in the update, while noting the coverage relies primarily on Analogue's general claims rather than independent testing. Nobody has published frame-timing captures yet. Treat no impact as a manufacturer claim, not a measured result — at least until someone straps a capture card to it.

Memories, Gallery, and the QoL Turn

Between the compatibility grind and the upscaling headline, Analogue spent the spring bolting on the conveniences that emulator users take for granted and cartridge purists never had. This is where the 3D stopped being a fancy cartridge slot and started being an operating system.

Save states, branded Memories (1.3.0)

1.3.0 introduced save states under the name Memories — up to 20 per game, with the oldest auto-pruned and pinned entries preserved. On real N64 hardware your only options were the cartridge's battery-backed SRAM or a Controller Pak, and both had a habit of dying. Save states on original silicon, driven by an FPGA snapshotting machine state, is exactly the kind of thing the cartridge-fundamentalist crowd swore they did not want and now quietly rely on every time they quit mid-dungeon.

Screenshots with no way off the box (1.4.0)

1.4.0 added screenshots and a Gallery, capturing frames in what Analogue calls bit-perfect 4K HDR. The catch is comedy: there is no WiFi and no network stack, so your bit-perfect captures are stranded on the SD card. Writing for MMORPG.com, Joseph Bradford put it plainly: I do wish that the A3D had a WiFi feature so I could simply upload the screenshots direct from the console. Instead you power down, pull the card, and go find a reader like it is 2009.

Quick Loading and Recent Memory (1.5.0)

1.5.0 rounds out the save-state system: Quick Loading makes a Memory load instantly, and the new Recent Memory startup action drops you straight back into your last save when you power on with an original cartridge inserted. Combined with the boot-into-cartridge startup action that landed earlier in the 1.2.x line, the 3D can now behave almost like a sleep-resume handheld — from a box with a cartridge slot on top and no battery in sight.

The Cycle-Accuracy Fight Analogue Won't Name

Here is the subtext running under every one of these release notes. In December 2025, respected N64 homebrew developer Kaze Emanuar ran the 3D through his own test suite and concluded the marketing oversold the silicon.

Kaze Emanuar's teardown

Speaking via Notebookcheck, Kaze was blunt: this thing is nowhere near cycle accurate. His numbers: the CPU ran roughly 6% slow, the RSP roughly 30% slow, and he flagged a missing ninth megabyte of RAM — a nod to the N64's odd 9-bit RDRAM, where the extra bit per byte feeds the RDP's coverage and anti-aliasing. Across a broader set he estimated about 5% lag overall, with titles like Diddy Kong Racing running about 4% slower than hardware. For a machine sold on authenticity, a 30%-slow signal processor is not a footnote.

The RSP notes that read like a reply

Now reread the firmware log. 1.2.3 quietly added low-level work on RSP dual-instruction interlocks, CPU CP0 behavior, and VI register timing. 1.5.0 escalates it to full RSP scalar/vector interlock behavior implementation and complete RSP branch and dual instruction behavior implementation. Analogue never names Kaze. But three of the most technical changelog lines in the entire 2026 run target precisely the subsystem he measured as most inaccurate. Draw your own conclusion about who is reading whose test videos.

What an FPGA can and can't fix

The lesson worth internalizing: FPGA does not mean cycle-accurate. It means reconfigurable logic. Accuracy is a function of how faithfully the core is described in hardware description language, and that description is software — shipped in firmware, patchable, and evidently still being patched. The upside is that a timing bug found in December can be narrowed in July. The downside is that you bought a box whose accuracy is a moving target. That is the trade the entire platform is built on, and 1.5.0 is the clearest evidence of it yet.

How We Got Here: Analogue's Firmware Doctrine

None of this cadence is new for Analogue. The firmware-as-platform approach has a lineage, and the 3D is its most ambitious application.

From the Super Nt to the 3D

Analogue built its reputation on FPGA recreations of 8- and 16-bit systems — the Super Nt, the Mega Sg, the Nt Mini, and the handheld Pocket — each a clean-room logic implementation rather than software emulation. The 3D is the first time the company tackled the fifth generation, and the N64 is a brutal target: a 64-bit MIPS CPU paired with a microcoded coprocessor that emulator authors spent two decades wrestling. Doing it in gateware, in a shipping consumer product, was never going to be a solved problem on day one — and the changelog proves it was not.

A launch three delays deep

Announced on 16 October 2023, the 3D slipped repeatedly through 2024 and 2025 before shipping on 18 November 2025 for $249.99. Reviewers were warm but qualified. Engadget's Tim Stevens summed the tension up in his review: 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.

3DOS as a platform, not a BIOS

What separates the 3D from a passive clone is 3DOS — a real operating system with a library view, display modes, overclock tiers (Auto, Enhanced, Enhanced+, Unleashed), and now a save-state and screenshot layer. The GamesRadar+ verdict that the console sets a new bar for retro console remakes was written before half of these features existed. The bar has moved twice since — once at 1.3.0, again at 1.5.0.

The Numbers People Keep Getting Wrong

Firmware coverage is where pricing myths metastasize, so let us fix the record. The Analogue 3D is not a $399.99 console, and the cheap accessory people keep citing is not an EverDrive.

The $249.99 console (not $399.99)

The 3D launched at $249.99 on 18 November 2025. A 24 November restock nudged to $269.99, which Engadget attributed to tariff pressure rather than a base price change. Any figure near $399.99 is either a scalper's markup or a confused writer folding a controller and a flash cart into the console line. It ships with a 16 GB microSD card preinstalled — the same card you drop firmware onto, which is a nice touch given the update process depends on it.

The $39.99 controller trap

The 3D does not include a pad. The reference controller is the 8BitDo 64, a wireless modern-take design, at $39.99 separately. That $39.99 gets misfiled constantly as the price of a flash cart or a storage add-on. It is neither. If you want the console-plus-controller reality, budget $289.98 before tax — and note that the 1.5.0 controller fixes specifically target 8BitDo's N64 Modkit, not this pad.

Flash carts, EverDrives, and the cost of a library

To load ROMs you need a flash cart, and the class standard is Krikzz's EverDrive 64 X7, street-priced around $175–$215. That is the number that pushes a full setup toward $500 — and it makes 1.2.4's per-ROM Library detection a material feature, not a nicety. If you would rather dump your own cartridges than buy dumps, our Retrode 2 cartridge-dumping walkthrough covers the own-the-silicon path.

3D vs. MiSTer vs. Software Emulation

The 3D does not exist in a vacuum. Its rivals are another FPGA platform and a mature software stack, and 1.5.0 shifts the calculus in one specific way.

MiSTer's unfinished N64 core

The open-source MiSTer project runs on Intel Cyclone V hardware and covers an enormous library, but its N64 core remains the difficult, community-maintained frontier — demanding, incomplete, and nobody's idea of turnkey. If you want the DIY FPGA route and its economics, we broke down the boards in our MiSTer Multisystem 2 coverage. The 3D's advantage is that it is one N64 core, tuned relentlessly, on hardware you do not have to assemble or flash core-by-core.

Software emulation grew up

N64 emulation was historically the hardest console to get right; low-level RDP emulation only became practical with Vulkan-era projects like ParaLLEl-RDP. Today a decent PC or handheld runs it well, and if that is your lane, our RetroArch cores guide and the reliably frozen RetroPie image are the reference points. Software wins on flexibility, resolution, and price; it loses on input latency, real-cartridge support, and the CRT-authentic display modes Analogue models.

Where 3DOS pulls ahead in mid-2026

Before 1.5.0, the honest pitch for the 3D was authenticity plus 4K output. After 1.5.0, it also offers internal upscaling that respects the original render — a middle path between pixel-exact and full software supersampling. That is a narrower, more defensible claim than most emulators make, and it is the strongest position the 3D has held since launch.

How the Update Actually Installs

The mechanics are deliberately boring, which is the point. There is no account, no launcher, no forced telemetry. You move a file.

The SD-card method

Download the 1.5.0 binary from Analogue's firmware page, verify the MD5, and copy it to the root of the console's microSD card. Power on. The 3D detects the file, flashes, and reboots on its own. Expect three to six minutes, and do not cut power while it works.

1. Download 3DOS 1.5.0 (22.3 MB) from analogue.co/support/3d/firmware
2. Verify MD5 = a00db9c90a2d8f09f25ec7f2d47c1802
3. Copy the .bin to the ROOT of the microSD card (not a subfolder)
4. Insert the card and power on the Analogue 3D
5. Wait 3-6 min — Power LED yellow, controller LEDs blinking
6. Console reboots to the library on the new build

Recovery: hold RESET + POWER until the LED turns green (USB-C mode)

The USB-C recovery path

If a flash fails or the box will not boot cleanly, the 3D exposes a USB-C recovery mode: hold the reset and power inputs together until the LED turns green, which puts the console into a state a host can talk to. It is the safety net that makes a twelve-build cadence tolerable — a botched update is recoverable, not terminal.

Reading the LEDs

During a normal update the Power LED sits yellow while the controller-port LEDs blink; that is the console working, not hanging. When it goes dark and reboots to the library, you are on the new build. Confirm under the OS version display before you assume anything — and before you post that the upscaling did nothing because you never actually updated.

Six to Twelve Months Out

Extrapolating from a company that has shipped a build roughly every three weeks, here is where I would put my chips through early 2027.

Vertical upscaling and higher multiples

1.5.0 doubles resolution horizontally and explicitly leaves the vertical axis alone. That asymmetry is a roadmap, not a limit. Expect a follow-up — call it 1.6.0 — that adds vertical upscaling or a 2x/4x option, most likely gated behind a warning about interlaced and high-fill-rate titles where the RDP is already stressed and the timing budget is thinner.

WiFi, cloud saves, and the missing pipe

The screenshot-with-no-WiFi problem is too obvious to survive. I do not expect Analogue to retrofit radio into shipped units, but I would bet on either a documented SD-card sync workflow or a USB-C data path that turns the console into mass storage for pulling captures and Memories off the box. That USB-C port almost certainly has an unused data lane sitting behind the recovery mode.

The cadence bet

The safest prediction: the updates keep coming. Twelve builds in eight months is not a launch-window scramble; it is a maintenance philosophy. Expect the RSP and CPU timing work started in 1.2.3 and escalated in 1.5.0 to continue, quietly narrowing the gap Kaze Emanuar measured — and expect Analogue to keep not mentioning him while doing it. I would wager the console is on a 1.7.x build by the time the holidays hit, with at least one more headline-grade feature between now and then.

The Machine's Verdict

1.5.0 is the most interesting firmware Analogue has shipped for the 3D because it is the first that changes the image rather than the plumbing. It is also a quiet admission that day-one silicon left detail on the table.

What 1.5.0 gets right

Internal upscaling done at the RDP/VI stage, with 2D left untouched, is the correct engineering answer — no invented pixels, no neural hallucination, deterministic and reversible with a toggle. Quick Loading and Recent Memory finish the save-state system properly. And the RSP interlock work signals a company still chasing accuracy eight months in. For a $249.99 box, that is a lot of free forward motion.

What's still missing

No WiFi, no off-device path for captures, no vertical upscaling yet, and — critically — no independent frame-timing verification of the no-performance-impact claim. Notebookcheck's caution that the coverage leans on Analogue's own claims is the right posture. Until someone captures the frames, no impact is a promise, not a measurement.

Update or wait?

Update. The USB-C recovery net makes the downside small, the upscaling is genuinely worth seeing on your own library, and the accuracy tweaks only help. Just verify the MD5 first, and do not expect a doubled horizontal resolution to make every N64 game look reborn — some of these titles were soft by design, and no firmware rewrites 1996.