Analogue 3D 1.5.0: N64 Upscaling in 12 Builds

Analogue built the Nintendo 64 the internet spent thirty years demanding, and then spent the next eight months quietly conceding it wasn't finished. The official 3D firmware archive now lists 3D OS 1.5.0, dated 21 July 2026, as the current baseline — the twelfth dated build since the console went on sale in November 2025. That is roughly one firmware release every three weeks for a $250 box that was sold, from day one, as cycle-accurate.

The headline feature of 1.5.0 is internal graphical upscaling, and Time Extension called it "a game changer." It is genuinely clever engineering. It is also, if you read the changelogs as a diary rather than a marketing artifact, the moment Analogue stopped fixing the N64 and started improving it — which, for a company whose entire brand is fidelity to the original, is a far more interesting story than the press release wants it to be.

1.5.0: What Just Landed

The payload

3D OS 1.5.0 shipped with one marquee item and a fistful of quieter ones. The marquee is internal graphical upscaling: the console now renders N64 geometry at higher internal precision before the frame ever reaches the HDMI cable. Underneath sit the load-bearing entries — improved RSP scalar and vector interlock behaviour, progressive-output jitter removal, a fix for simultaneous C-button presses, instant loading of saved positions ("Memories"), a Recent Memory startup option, and rumble support for the 8BitDo N64 Modkit. If you want the granular teardown of the upscaler, we pulled it apart in our companion piece on the 1.5.0 upscaling path across twelve firmware builds. Here, the cadence is the story.

Why the word 'upscaling' matters

Analogue built its reputation on a promise: no scaling tricks, no emulator smell, just original silicon behaviour reproduced in an FPGA. Internal upscaling is, by definition, a scaling trick — a good one, but a trick. The company is conspicuously careful to state that it "doesn't change game timing, frame behaviour or performance," and that 2D layers (menus, HUDs, text) are left untouched. That precision is the tell. You only write a sentence that defensive when you know the purists are reading the release notes with a magnifying glass and a stopwatch.

Twelve builds, eight months

Count them: 1.1.0 at launch, then 1.1.9, the seven-strong 1.2.x run, and 1.3.0 through 1.5.0. That is the twelfth dated build on the public archive in roughly eight months — one release every three weeks. Analogue frames it as post-launch generosity. Read the notes in order and it looks more like a company amortizing a debt it took on the day it called a not-quite-finished console "cycle accurate." The 1.5.0 package ships with the MD5 checksum a00db9c90a2d8f09f25ec7f2d47c1802 — a detail that matters more than it should, for reasons we'll reach shortly.

The N64 That Took Eight Years

The Taber doctrine

Analogue announced the 3D on 16 October 2023 with the same thesis that has powered every product the company has ever shipped: software emulation is a compromise, and compromise is the enemy. CEO Christopher Taber put it in writing at the reveal, telling anyone who would listen that "despite all of the amazing love, effort and work that developers have put into the software emulation of the N64 — it results in an experience that feels unjustly and wrongly aged — generally 'off.'" He later told VGC that not even Nintendo could build a better modern N64. That is the bar Analogue set for itself, in public, on the record. Every firmware release since is measured against it whether the company likes it or not.

A launch defined by delays

The 3D was supposed to arrive in Q1 2025. Then July 2025. Then August. It finally went on sale on 18 November 2025 at $249.99, per the Wikipedia record, with Analogue blaming development refinements and tariff turbulence. A restock on 24 November already carried a tariff-adjusted $269.99 sticker — a twenty-dollar bump inside six days, and a preview of the pricing anxiety that has stalked every piece of hardware in 2026. Reviews landed strong: 8 to 9 out of 10 across IGN, Wired and Time Extension, with the usual caveats about missing software features and no bundled controller.

The Cyclone 10 GX gamble

The 3D's brain is an Intel Cyclone 10 GX FPGA with roughly 220,000 logic elements on a 16nm process — a meaningfully larger part than the chips inside the Super Nt or the Analogue Pocket. It needs to be. The N64's Reality Coprocessor is the hardest 2D/3D console silicon of its generation to reproduce in programmable logic, which is precisely why the MiSTer community spent years on its own N64 core. Analogue bet that a fat FPGA plus HDMI 2.1 output — 4K, HDR, VRR — would be enough to satisfy both the videophiles and the accuracy zealots. The videophiles were satisfied on day one. The zealots were not.

'Nowhere Near Cycle Accurate'

What Kaze Emanuar measured

Three-and-a-half weeks after launch, veteran N64 developer Kaze Emanuar — the man who has spent a decade wringing frames out of real N64 silicon — published a side-by-side test video with the deadpan title Analogue Lied. His verdict, as documented by Notebookcheck, was blunt: "This thing is nowhere near cycle accurate." His numbers, dropped on 14 December: roughly 5% overall performance lag against original hardware, a 6% slower CPU, a 30% slower RSP (the geometry unit), and Diddy Kong Racing running about 4% slower at the frame level. He also flagged the absence of the so-called ninth megabyte of RAM that homebrew coders repurpose from the console's RDRAM.

Analogue's silence

Analogue's response was to say nothing. The company "remained tight-lipped" and made no public statement in the wake of the video. For a brand that markets accuracy as a moral position, silence in the face of a measured accuracy failure is a choice — and not a flattering one. The one crumb Emanuar himself offered was that the core's designer had privately indicated firmware updates would address the timing and precision problems. Hold that thought.

Firmware as public penance

Because that is exactly what the changelog shows. Read the 1.2.0 notes and you find a fix for "cartridge timing when overclocked." Read 1.5.0 and you find "improved RSP scalar/vector interlock behaviour." Timing. RSP. The two organs Emanuar's stopwatch singled out. The dozen-build cadence is not a company lavishing love on a finished product; it is a company closing the gap between what it shipped and what it advertised, in three-week increments, in the open. That reframes every subsequent release. When Analogue adds upscaling in 1.5.0, it is doing so from a position where a respected developer has already put a number on the console's inaccuracy — which makes "we added more pixels" a slightly awkward flex.

Every 3D OS Build, Dated

The 2025 foundation

The first meaningful post-launch build, 1.1.9 on 28 November 2025, was pure fidelity plumbing: manual region selection, a Disable Texture Filtering toggle for people who want their N64 sharper than 1996 allowed, a stronger Unleashed overclock, and compatibility fixes for Bomberman Hero (PAL) and Super Smash Bros. It set the pattern — accuracy and compatibility first, features later.

The 1.2.x grind

January through April 2026 is where the console grew up. 1.2.0 (30 January) fixed 4K display/switch handshakes, HDMI CEC/eARC, audio clipping and — there it is — cartridge timing when overclocked. Williams Pelegrin at It's a Retro Thing called that build "a doozy," noting the biggest addition was the ability to force progressive scan. The point releases that followed were relentless: 1.2.1 killed a bug where playtime over 24 hours broke the library; 1.2.2 added Startup Action and a Power Off menu item; 1.2.3 fixed cartridge detection, GameShark support and OS brightness under HDR; 1.2.4 tackled flash carts; 1.2.5 added Advanced HDR; 1.2.6 stabilised the SD card and squashed Resident Evil 2's progressive-output flicker.

The feature era

From 1.3.0 onward the tone shifts from repair to enrichment. 1.3.0 (15 May) introduced save states, branded "Memories," and — a detail every buyer needs to know — required the 8BitDo 64 Bluetooth controller to be on firmware 2.05 or later. 1.4.0 (23 June) added a screenshot gallery. 1.5.0 (21 July) added the upscaler. The full ledger:

Inside the Upscaler

Where the pixels come from

The trick in 1.5.0 is that it is not a trick at the output stage. As Generation Amiga explains, the system "increases the amount of visual information before the picture reaches your television" rather than stretching a finished HDMI frame. The work happens inside the graphics pipeline, at the Reality Display Processor and Video Interface stages — the console doubles horizontal detail during rendering, giving you twice as many pixels across without re-timing the game. Think of it as rendering the N64's world at a finer grid before the RDP resolves it, not blowing up a small image after the fact.

What it deliberately leaves alone

Two guardrails keep the purists from rioting. First, 2D graphics — menus, text, sprite-based interface elements — are left entirely unprocessed, so your Ocarina of Time HUD is pixel-identical to stock. Second, and this is the sentence Analogue keeps repeating, it "doesn't change game timing, frame behaviour or performance." It can be toggled on or off mid-game without a reboot. This is the opposite philosophy to the DLSS-style neural upscaling that defines modern handhelds; if you want to see how far the machine-learning approach diverges, our breakdown of the Switch 2's 1080p DLSS pipeline is the useful contrast. Analogue's method is dumber, more honest, and — crucially — deterministic.

The 4K payoff and the checksum

The beneficiaries are people running the 3D on a large 4K panel, where N64 polygon edges normally dissolve into mush; the horizontal double gives you cleaner silhouettes and more legible distant geometry. Before you flash anything, verify the package — Analogue publishes the MD5 for exactly this reason, and a corrupted firmware write on an FPGA console is not a Tuesday you want:

# Verify the official 1.5.0 package before you flash it
$ md5sum 3D-1.5.0.bin
a00db9c90a2d8f09f25ec7f2d47c1802  3D-1.5.0.bin   # must match Analogue's listing

# The new toggle lives under the video options and switches mid-game:
Settings > Video > Internal Upscaling > On   # no reboot required

# Prerequisite that bit early adopters on 1.3.0 and later:
8BitDo 64 (BT) controller firmware >= 2.05

Progressive Output, HDR & Bugs

Force Progressive Output's rocky beta

The single most requested feature of the 3D's first year was clean progressive scan, and Analogue delivered it as Force Progressive Output in the 1.2.0 era — then spent months stabilising it. The feature outputs the full progressive framebuffer image, but Analogue itself warned it "may not be fully supported" on games that use field rendering for menus, and some titles threw graphical artifacts with it enabled. The Resident Evil 2 flicker fix in 1.2.6 (24 April) was the poster child: a specific, reproducible flickering bug under progressive output, patched by name. That is the level of granularity the 3D's audience demands — and, to Analogue's credit, receives.

Advanced HDR and brightness

HDR on a console outputting 240p-native content is a genuine engineering puzzle, and Analogue iterated on it in public. 1.2.3 fixed OS brightness behaving badly with HDR enabled; 1.2.5 added an Advanced HDR mode alongside controller-pairing improvements. None of this is glamorous, but it is the difference between an HDR toggle that looks like a marketing checkbox and one that survives contact with your specific television's tone-mapping.

Flash carts and variable headers

The most quietly impressive fix of the year was 1.2.4 (28 March). Flash carts like the EverDrive present a single physical cartridge to the console while cycling through hundreds of ROMs, which used to collapse every game into one library entry with one shared virtual Controller Pak — a save-file blender. As Notebookcheck detailed, 1.2.4 added advanced library detection that reads ROM header changes and tracks each as its own entry. In Analogue's own words: "If a cartridge changes its header, this is detected, added, and tracked in the Library. The Virtual Controller Pak and per-game configuration are applied automatically." Per-game saves, restored, without you touching a setting.

Hardware By The Numbers

Silicon and output

The 3D is a genuinely modern piece of hardware wrapped around a 1996 idea. The Cyclone 10 GX drives an HDMI 2.1 pipeline with 4K, HDR and Variable Refresh Rate — and yes, VRR on a retro console is real, and it matters for the interlaced-content edge cases the 3D still wrestles with. If VRR standards are a rabbit hole you want to fall down, our piece on why the G-Sync module tax finally died in 2026 covers the display side properly. Audio is a clean 48 kHz, 16-bit PCM feed.

Performance modes and the overclock paradox

Here is the philosophical incoherence hiding in the spec sheet. The 3D ships four performance modes — Auto, Enhanced, Enhanced+ and Unleashed, the last pushing up to 50% faster RCP and 33% faster CPU. Overclocking is the literal opposite of cycle accuracy. Analogue sells you a console whose brand is faithful reproduction and then hands you a switch to make it run faster than any N64 ever did. Both things can be good; they cannot both be the point. The 1.2.0 fix for "cartridge timing when overclocked" exists precisely because these two philosophies keep colliding inside the same box.

What's missing

Unlike the Analogue Pocket, the 3D has no openFPGA. There is no sanctioned path to load community cores and turn it into a do-everything FPGA machine — it plays N64 cartridges, region-free, and nothing else. For a $250-plus single-system console in 2026, that is a defensible purist stance and a real limitation, depending on your temperament.

3D vs MiSTer vs Emulation

The FPGA rivals

The 3D's only true philosophical peer is MiSTer, whose N64 core is one of the most demanding targets in the FPGA scene. MiSTer wins on flexibility — it plays dozens of systems on one board — and on openness, but it asks for assembly, configuration and patience, and its N64 output does not natively reach 4K/HDR the way the 3D's does. If you want the current state of dedicated FPGA hardware, our look at the MiSTer Multisystem 2 shipping in 2026 lays out the tradeoffs. The 3D's pitch against MiSTer is simple: plug in a real cartridge, get 4K, touch nothing.

Has software emulation caught up?

For most people, honestly, yes — and that is the uncomfortable subtext of the Kaze numbers. A modern PC running the mature N64 cores in RetroArch will hit reference-grade accuracy that a 5%-slow FPGA can't claim, with upscaling and texture options that make 1.5.0 look conservative. Our walkthrough of the RetroArch core setup for 2026 is the free path. What emulation cannot give you is a real cartridge slot, a real controller port, and a box that boots to a game in two seconds without a Windows update ambushing you first. The 3D sells the appliance, not the accuracy.

The CRT purist holdout

Then there is the person who thinks all of this is theatre and wants an RGB-modded N64 on a Sony PVM. They are not wrong, and the 3D's Original Display Modes exist specifically to court them with BVM/PVM/scanline simulation. The honest framing:

6-12 Month Forecast

The 3D's first year is a legible trend line, and trend lines invite forecasts. Five for the next six-to-twelve months, in descending order of confidence:

1. The accuracy gap keeps closing, quietly. Expect at least two or three more point releases (a 1.5.x and a 1.6.0 are near-certain) that continue chipping at RSP and CPU timing. Analogue will never publish a "we fixed the Kaze delta" note, because admitting the delta contradicts the marketing — but the RSP-interlock language in 1.5.0 tells you the work is ongoing.
2. Upscaling grows a vertical option. 1.5.0 doubles horizontal detail only. The obvious next move is symmetric or vertical upscaling, plus per-game upscaling profiles. Feature parity with what emulator users already expect is the pressure, and Analogue has shown it responds to pressure.
3. The pace slows after the one-year mark. Twelve builds in eight months is a launch-crisis cadence, not a steady state. Once the accuracy debt is paid down, expect the release rhythm to stretch toward monthly, then quarterly. A firmware every three weeks is a signal of unfinished business, and that business is finite.
4. Price stays sticky or rises. The $249.99-to-$269.99 jump inside a week was tariff-driven, and nothing about the 2026 component and tariff environment suggests relief. Do not expect the 3D to get cheaper; a limited-edition colourway at a premium is likelier than a price cut.
5. openFPGA stays locked. The community will keep asking. Analogue will keep declining. The 3D is a statement product about the N64 specifically, and opening it to community cores would dilute that. Bet against it happening this cycle.

The Machine's Verdict

Who should install 1.5.0 today

If you already own a 3D, this is not a decision — flash it. Verify the checksum, update your 8BitDo 64 to 2.05+ first, and take the free upscaling, the free save states, and the accumulated year of bug fixes. 1.5.0 is the best the console has ever been, by a wide margin, and it costs nothing. The firmware is the product now; the box was just the delivery mechanism.

Who should still wait

If you don't own one yet, the calculus is more interesting. IGN's Seth Macy called the 3D "the best possible way to play your N64 library outside of the original hardware hooked up to a CRT," and after twelve builds that is closer to true than it was at launch. But Kaze Emanuar's stopwatch hasn't been repealed, the price only moves up, and a mature RetroArch setup remains free and, on paper, more accurate. The 3D is for the person who wants the appliance — real cartridge, real controller, 4K, no fuss — and is willing to pay a premium and tolerate a 5% asterisk for it. That is a real and defensible want. Just buy it for what it actually is in August 2026: a very good, still-improving N64 that spent its first year becoming the console it was sold as. Buy the firmware. The box came free with it.