Show HN: A working Nintendo in ~1GB of Qwen weights
dbreunig
227 points
118 comments
October 30, 2026
Related Discussions
Found 5 related stories in 134.9ms across 11,107 title embeddings via pgvector HNSW
- Show HN: Running 104GB Qwen3.8-Flash-Next on 48GB Mac with at ~12 tok/s carloslfu · 187 pts · September 01, 2026 · 62% similar
- Show HN: PS2 games statically recompiled to WebAssembly deadxwarrior · 284 pts · October 12, 2026 · 58% similar
- Show HN: Three genlocked RP2350B make a console – 3k sprite pixels per line) papyDoctor · 11 pts · September 20, 2026 · 57% similar
- Show HN: I shrank DeepSeek V4 Flash to 57GB and it wrote a compiler on my Mac hacklas · 17 pts · August 16, 2026 · 56% similar
- Show HN: A techno machine in one HTML file, with verifiable renders ssx360 · 187 pts · August 24, 2026 · 55% similar
Discussion Highlights (18 comments)
jacquesm
I love these hacks, even though from an efficiency point of view it is horrifying to my assembly-code-golfing-brain. And it also gives some new appreciation for how much more efficient deterministic programs are compared to AI.
amelius
How do they know it's "working"? Did they test every possible input/output combination?
WoodenChair
I guess I don't understand the point of this. Of course a set of digital logic circuits can be reduced to a set of weights. Am I missing something?
woah
This is like when people used to make tetris using only CSS or whatever in the 2010s. But it's less impressive because Claude Code can slop it out in an afternoon.
mlmonkey
Can someone give a TL;DR ? What's the input to the model? What's the output?
cafebeen
I expected this to only simulate the CPU itself, but was surprised to find they actually simulate the RAM as well (contained in the model itself via the gated deltanet architecture). So in my understanding, the CPU, ROM, and RAM are all handled internally by the model, and the only inputs after initialization are the controller events, wild.
creposukre
Omg what is this sorcery?!
pbohun
>Overall, nesformer runs 150–290× slower than the real console. I like these kinds of projects because it helps to show the massive compute requirement between LLMs and ordinary programs. A while back I saw some people saying we would just have LMMs hallucinate an entire operating system every single frame . I guess technically it's now proven to be technically possible, but it would be thousands of times slower while requiring thousands of times more compute (a multi-million x difference from an ordinary OS!).
armcat
This opens up so many interesting opportunities. In principle one could compile a small VM inside the LLM weights. The VM can host for example a Python interpreter, a shell and tools like sed, cat, grep etc. Instead of LLMs having to do slow autoregressive token emission with the current "external" tool calling, it could literally execute everything except web search, inside the LLM, with just matmul operations. You could probably optimise this so it runs in batches. You could have a gdb like application that can step through the LLM forward pass. Anyway, just a crazy thought. Have a great weekend everyone!
munro
Woowww this is cool, not trained is even cooler--maybe I'm probably a bit naive, but to me it demonstrates an understanding of how an LLM can compute
dbreunig
A couple thoughts on the process here… First off, Opus 5.5 built working weights and code with only two prompts: 1. Read this article and any relevant source code: https://divagr.com/blog/qwenputer . Then explore if you could emulate the chip and ram in a Nintendo Entertainment System (as people do today with FPGAs in MISTRs) using this technique. If so, what size model would you have to build and if you could use smaller faster ones, could you get it to be at the standard clockspeed. It returned charts well illustrating any model would be _slow_. But it's still fun, so the second prompt was: 2. I think we should build it! Just for fun. It's okay if it's not fast. We want to be able to have the weights, and a cli to run them that we can point at a ROM. Now while this was an _epic_ run by Opus (5.5 is a crazy capable model), this is a surprisingly well-structured challenge. There is a long-lived and incredible community of classic gaming emulation work online for it to reference. And that community has created…conformance tests! Opus found them and built against one, that has >3k golden instructions: https://github.com/christopherpow/nes-test-roms/blob/master/... Also, there is the original Qwenputer repo that Opus used to drive the weight writing. That was essential. But this is a great example of what these models can do with proper reference materials, great specs, conformance tests, and clear direction.
nico
> nesformer builds on Qwenputer by Divyansh Agrawal, which compiled a CHIP-8 and then a RISC-V CPU into Qwen3.5-4B. It reuses Qwenputer's compiler and its central trick: the model's Gated DeltaNet state is the machine's memory This is amazing, love it! Qwenputer is very cool too
akie
I'm guessing it's safe to say that LLMs can run Doom.
vorticalbox
Has anyone tried training a diffusion model for speed ?
lachlan_gray
It mentions a greedy decoder in the readme, I'm curious what would happen if you run it stochastically with T>0. Vibe NES? Or does it just crash.
dormento
B-but "there's no such thing as a Nintendo". https://www.reddit.com/media?url=https%3A%2F%2Fi.redd.it%2F5... "Mario thanks you".
fnord77
so, are LLMs going to be come the universal computing medium?
publlus_enigma
Sorry, I couldn't parse the obviously AI written README. If the author can't be bothered writing it, I can't be bothered reading it. Maybe the bots will appreciate it more, after all, it seems to be written for them.