Analogue 3D Firmware 1.3.0: Save States Hit 900 Games

Analogue shipped firmware 1.3.0 for the Analogue 3D on 15 May 2026, and for once the headline feature is not a footnote buried under a changelog. It is Memories — the company's branded save-state system — and it works across the full 900+ N64 cartridge library the 3D claims to support. That is the feature owners have been asking for since the console shipped, and it is the feature that, conspicuously, was not there at launch. Eighteen months of firmware releases later, the 3D is finally doing the one thing a modern FPGA console is supposed to do: let you suspend a real cartridge mid-level and walk away.

This is a console that sells itself on hardware authenticity, on cycle-accurate field-programmable gate array logic rather than software emulation. Save states are, philosophically, an affront to that pitch — the N64 never had them. And yet here they are, applied uniformly across a library Analogue had to reverse-engineer cartridge header by cartridge header. The tension between purity and convenience runs through every line of the 1.3.0 notes, and it is the most interesting thing about this update. Let us go through it properly, with the numbers.

Memories: Save States Land at Last

What Memories actually does

Memories is Analogue's save-state implementation, and the operative detail is coverage: it applies across the entire supported library, reported by Analogue as 900+ N64 titles. That breadth matters more than it sounds. Save states on a software emulator are trivial — you snapshot RAM and a few registers. On an FPGA console that reconstructs the N64's Reality Coprocessor, the Reality Display Processor, and the cartridge bus in hardware, capturing and restoring complete machine state across hundreds of differently-behaved carts is a genuine engineering problem. A library-wide guarantee implies Analogue solved state capture at the logic level, not per-game.

Why it took eighteen months

The 3D launched without save states, and the omission was not an oversight — it was a sequencing decision. Analogue prioritized compatibility and display correctness first, which, as the firmware record below shows, consumed most of late 2025 and early 2026. Memories is the kind of feature you ship once the underlying emulation is stable enough that a restored state behaves identically to the original run. Ship it too early on a flaky core and every reload becomes a bug report.

The purist objection, answered

If you want the museum-piece experience, ignore Memories and the cartridge behaves exactly as it did in 1996. Nothing is forced. The feature is additive, and that is the correct call. For the broader picture on how this rollout landed, our coverage of the 1.3.0 save-state launch in 2026 tracks the owner reaction in more detail. The short version: relief, mostly.

The Spring 2026 Firmware Timeline

A genuinely fast cadence

The most under-discussed fact about the Analogue 3D is how aggressively it has been patched. Analogue's official firmware page documents releases arriving roughly every few weeks through early 2026. 1.2.2 landed 27 February 2026. 1.2.4 followed on 28 March 2026. 1.2.6 shipped 24 April 2026. Then 1.3.0 on 15 May 2026. That is four documented releases in under three months, and it does not count the point releases in between. For a boutique hardware company, that is a software cadence closer to a games-as-a-service title than a $250 retro box.

The numbers, in one place

Why cadence is the real story

Hardware emulation companies have historically shipped a console, patched it twice, and moved on. Analogue's spring schedule signals the opposite posture — the 3D is being treated as a maintained platform, not a sealed object. As Engadget and other outlets have noted across Analogue's product line, the company's update discipline is part of the value proposition, not a bonus. You are buying future firmware as much as present silicon.

Progressive Output and the 8BitDo Caveat

The beta nobody asked about

Alongside Memories, 1.3.0 improved Progressive Output (beta) for certain games. The N64 was an interlaced-output machine in most of its library, and progressive output — clean, non-interlaced frames — is one of the genuine quality-of-life wins a modern display chain can offer over a CRT-era console. Analogue flagging it as beta is honest; progressive conversion on a per-game basis is fiddly, because games handle field rendering differently. Some titles will look transformatively cleaner. Others will not engage the path at all yet.

The 8BitDo controller dependency

Here is the gotcha buried in the notes: Analogue states the 8BitDo 64 BT controller must be updated to version 2.05 or later for the 1.3.0 feature set to work properly. This is the kind of dependency that generates support tickets, because the average owner does not think to flash their controller firmware before flashing their console. If your inputs behave strangely after updating to 1.3.0, the controller — not the console — is the first thing to check.

Controllers are now part of the platform

That dependency is a small sign of something larger: the input layer is now firmware-coupled to the console. The same dynamic plays out across modern retro hardware — pairing, latency, and feature gating all live in firmware now, not in the cable. If you are weighing input ecosystems generally, our Retroid Pocket 6 vs G2 comparison for 2026 digs into how much controller and software pairing actually matters in practice on adjacent hardware.

Library Detection for Flash Carts

The 1.2.4 breakthrough

If Memories is the crowd-pleaser, the 1.2.4 update from 28 March 2026 is the one flash-cart owners actually needed. It introduced advanced library detection for variable game headers, which lets the 3D treat each ROM loaded from the same flash cart as a distinct library entry. Before this, a single physical EverDrive registered as one library item no matter what you booted from it. After 1.2.4, the console reads the changing header and catalogs each game separately — playtime, configuration, and all.

Per-game config that follows the cartridge

The same update automatically applies the Virtual Controller Pak and per-game configuration when a cartridge header changes. For flash carts like the EverDrive 64 and SummerCart 64, this is the difference between a usable daily driver and a constant settings dance. Swap games on the cart, and the 3D remaps its saved configuration to match — no manual intervention. If you are building out a dumping and flash-cart workflow, our Retrode3 ROM-dumping walkthrough in 14 steps pairs naturally with this firmware behavior.

Small package, real impact

Analogue described the 1.2.4 firmware as a 21.8 MB download — trivially small, and early users characterized it as a quality-of-life upgrade rather than a visual overhaul. The update also added a "Ready" prompt in the OS, letting players press B in the library menu to jump in faster depending on the inserted cartridge. None of this makes a screenshot. All of it makes the console less annoying to live with, which is the harder and more valuable kind of work.

3DOS v1.2.0: The Foundation Patch

The features people actually feel

The earlier 3DOS v1.2.0 release — the one that drew video coverage in the Engadget mold — is the load-bearing update of the whole timeline. On the convenience side it added total playtime tracking, game added dates, Expansion Pak and Controller Pak indicators, and faster boot times. These are the OS-level affordances that make a library browsable rather than just bootable, and they are the scaffolding that later features like Memories sit on top of.

Fixing the living room

1.2.0 also fixed a pile of display-chain problems that disproportionately hit modern setups: compatibility issues with some 4K TVs, HDMI switches, HDMI CEC/eARC, corrupted system graphics, and audio clipping. If you run your retro hardware through a soundbar and a switch into a 4K panel — which is to say, if you own a normal 2026 living room — these fixes are why your 3D stopped dropping handshake or clipping audio. This is unglamorous interoperability work, and it is exactly what a premium console should ship. The Verge has covered how brittle HDMI CEC and eARC chains remain across the industry; the N64 era never anticipated any of it.

Targeted game fixes

Crucially, 1.2.0 addressed specific titles — Space Station Silicon Valley and Gauntlet Legends among them — proving Analogue was still doing per-game compatibility work well after launch. That is the tell of a maintained core. A company that had walked away would never bother chasing two mid-library titles. If you want a sense of how much per-title tuning matters in software emulation by contrast, our breakdown of RetroArch cores in 2026 across 200+ plugins shows the scale of the problem on the other side of the fence.

Emulation Accuracy and Unleashed Mode

The deep core work

1.2.0 went beyond features into the emulation logic itself: improved CPU accuracy, fixed RSP/RDP timing, and improved cartridge handling including overclocking support. RSP/RDP timing is the hard part of N64 reproduction — the signal-processing and display coprocessors ran on tight, interdependent timing that determines whether effects render correctly or glitch. Fixing it at the FPGA level, rather than papering over it per-game, is the difference between an emulator and a recreation.

Unleashed mode and the framerate question

The earlier 1.1.9 update is where performance tuning got explicit. It improved unleashed mode overclock for CPU-bound games — naming Perfect Dark and GoldenEye 007 specifically. Those two Rare shooters are infamous for tanking below 20 FPS on original hardware during firefights. An overclock path that lifts CPU-bound titles is the FPGA equivalent of the overclock patches the PC emulation scene has used for years, except applied to hardware logic rather than a software loop. It is opt-in, and it is the most interesting performance lever the 3D exposes.

Region, filtering, and rumble

1.1.9 also added manual region selection in the in-game configure menu, a disable texture filtering option, improved rumble pack behavior, and fixed library-title truncation. Disabling the N64's notoriously aggressive bilinear filtering is a long-requested purist option — that blurry texture smear was always a hardware choice, and being able to switch it off is a small act of restoration. Together these settings show Analogue tuning the platform along two axes at once: more authentic when you want it, more forgiving when you do not.

How N64 Hardware Emulation Got Here

The console nobody could emulate well

The Nintendo 64 was, for two decades, the hardest fifth-generation console to emulate accurately. Its microcode-driven RSP, its unusual unified memory architecture, and the sheer variety of ways developers abused the hardware meant software emulators spent years chasing high-compatibility, low-glitch reproduction. Where the SNES and Genesis were largely solved by the early 2010s, the N64 remained a moving target, with major emulators still fixing fundamental rendering bugs into the 2020s.

FPGA changes the proposition

Analogue's whole thesis — across the Pocket, the Super Nt, the Mega Sg, and now the 3D — is that field-programmable gate arrays let you rebuild the original logic rather than approximate its behavior in software. That sidesteps the per-game hack problem in principle: get the hardware description right once, and every cartridge runs because the silicon runs. The catch, as the 3D's eighteen months of firmware proves, is that "get the hardware description right" is itself a years-long iterative process. FPGA is not magic; it is a different, and arguably more honest, place to spend the same effort. Ars Technica has documented this trade-off across the FPGA-versus-software-emulation debate for the better part of a decade.

Why the 3D's patch record matters historically

The spring 2026 cadence is, in a sense, the public version of what software emulator teams did privately for twenty years — except compressed into months and shipped to retail hardware. That visibility is new. Owners are watching N64 reproduction get solved in near-real-time, version by version, on a box they already paid for. The N64's reputation as the unemulatable console is being retired in firmware notes.

Analogue 3D vs the Alternatives

The three ways to play N64 in 2026

There are broadly three paths: a real N64 on original hardware with an upscaler, an open-source FPGA build like a MiSTer N64 core, or the Analogue 3D. Each makes a different bet. The original console is maximally authentic and maximally inconvenient. MiSTer is flexible, community-driven, and cheaper in parts but assembly-required. The 3D is the polished, sealed, maintained-firmware option — and the only one shipping a library-wide save-state system out of the box.

The comparison, in numbers

Where the 3D wins and where it doesn't

The 3D's edge is the combination of FPGA authenticity, retail polish, and a save-state guarantee no real cartridge ever offered. Its weakness is the same as every Analogue product: you are locked to one vendor's update schedule and one vendor's compatibility decisions. Software emulation remains more flexible and free; the comparison there resembles the broader console-value debates we covered in the Switch 2 2026 release and sales analysis, where polish and ecosystem command a premium over raw capability. The 3D is the premium pick, and it now has the feature list to justify the position.

What Comes Next: 6 to 12 Months Out

Predictions for late 2026 into 2027

Based on the documented cadence and the trajectory of the changelog, here is where the 3D is likely headed over the next six to twelve months:

1. Progressive Output exits beta. Given how prominently 1.3.0 flagged it, expect Analogue to graduate Progressive Output from beta to a supported, broadly-compatible feature by late 2026, with per-game coverage expanding patch by patch.
2. Memories gets depth. The first release covers the library; the next phase is usually multiple save slots, in-OS state browsing, and possibly cloud or USB backup of states. Save-state features rarely ship complete and stay still.
3. The cadence slows but does not stop. The every-few-weeks tempo of early 2026 is unsustainable long-term. Expect it to settle into a monthly-to-quarterly rhythm as the core matures and the easy compatibility wins run out.
4. Flash-cart support keeps deepening. Having solved variable-header detection in 1.2.4, Analogue is well positioned to add more EverDrive and SummerCart 64 niceties — per-game artwork, cheat handling, or improved homebrew detection.
5. Unleashed mode expands its title list. The Perfect Dark and GoldenEye overclock work in 1.1.9 was clearly a template. Expect more CPU-bound titles to get explicit overclock tuning as owners report the worst framerate offenders.

The bet on maintained hardware

The throughline of all five predictions is the same: Analogue has committed to the 3D as a living platform, and the firmware record is the proof. Buyers in late 2026 are not just buying current silicon; they are buying a roadmap that, so far, the company has actually delivered against. For coverage of how Analogue's claims hold up over time, outlets like Polygon remain worth watching as the patch cycle continues.

The verdict from here

1.3.0 is the update that retroactively justifies the 3D's launch-day omissions. Memories was always going to be the feature that mattered most, and Analogue held it until the core underneath could support it cleanly across 900+ titles. The result is a console that, eighteen months in, is finally the thing it promised to be — and one still being improved on a schedule most retail hardware would envy. If you bought in early and felt short-changed, the spring 2026 firmware run is your refund, paid in features.