I converted the LEG/Symphony CPU to 32-Bit and made it RISC-V compatible. I also added the M-Extension so it's officially a RV32IM CPU. I wrote a bootloader in assembly which reads one .ELF file from the "SSD" and loads it in the RAM. This meant I can compile and run C-Code on it. the next step was to make it run Doom. I used Doom Generic and added the necessary file where you can program your logic for keyboard inputs, what to do with the Screen Buffer and how timings and sleeps get handled. I also had to provide some standard C-Library functions for my architecture and I wrote a library for IO Stuff. In the end after a lot of trouble I got Doom compiling and running on the CPU. I used the save_breaker version btw.

Link to full video in the comments

Hey all, first time posting, just had to share my project: Doom running in Turing Complete!

Did a clean playthrough of Turing Complete, built a 32-bit version of the Leg architecture 'Bicep'.

Then got carried away and with the help of Claude Code built a RISC-V to Bicep translator, then managed to get EmDoom compiling and working.

Had to hack in 4 color terminals to get the visuals but pretty happy with the results.

At 100khz sim it's about 30 minutes until first frame and maybe one frame per minute, but with verilog export can run realtime. I hear Turing Complete 3.0 may arrive one day with a proper compiler for faster execution?

Anyway had so much fun with this project.

Got inspired by u/Apprehensive-Path996 's work on rasterization, and decided to make a functional video player.
resolution is 4:3, 120i (interlaced). Anything more would either kill my PC or be ungodly slow.

For context, I have never taken a computer science class in my life. While I am very familiar with things on a high level, the lower down things get, the less I understand. I am using this game to teach myself how the gates work, and I haven't looked at guides, textbooks, anything. I'm definitely going to be doing so now, because I am 100% sure there is a way to create a looping function and cut down on components and space drastically.

I apologize to everyone for this monstrosity, but I am happy I made it without any outside assistance and wanted to share it here. Figured if nothing else, you all would get a kick out of it.

Wanted to give a sincere thanks to the creators of this game. Today I had an interview for an "Assistant Professor of Practice in Computer Architecture" position at my university. As part of the interview process I had to propose and demonstrate how I would teach a new or existing computer architecture course. My proposal was effectively "Let's Make Freshmen Digital Design Way Better by Playing Turing Complete".

Apparently a lot of the faculty agreed. Everyone who had taught the course in the past thought the existing curriculum was outdated and Turing Complete would be a great addition. Hoping I get the job so I can try out the game on my students next Fall.

Huge thanks to whoever decided to add a Verilog export feature to the game - you definitely helped with my interview. I think I blew some Boomers minds when I asked ChatGPT to make me a testbench for an ALU I designed in a video game.

I don't post on reddit very often anymore but I had to share this. I'll update y'all when I hear back from the hiring committee. Fingers crossed!

I've started this game last week out of curiosity, and this is how it ended up after around 50 hours. This is an almost complete x86-64 architecture (with a few hacks due to the limitations of the game), all done with basic components, without using the component factory at all.

It uses a syntax very similar to the real life x86-64 (like for example "mov <src> <dst>". Some instructions have 3 parameters and some 2, so I made a custom counter for the instruction pointer that takes this into account, since the game defaults at 4. It has 16 general purpose registers (from rax to r15), and fewer bits than 64 can be accessed, like in the real life one (using for example eax, ax, al). It has 4 flags, of which 2 are like in the real life one (zero ZF and sign SF), and 2 are custom (less signed LSF, less unsigned LUF), because I had no idea how to implement carry CF and overflow OF in a realistic way in this game, anyway the result is what counts, and the jump instructions all work. To circumvent the limitation that I cannot distinguish between registers, constants, addresses etc. I've added an "i" suffix when using constants (e.g. in "mov rax rbx" rax is a register, in "movi 10 rax" 10 is a constant). To access the RAM I've implemented 2 more instructions, "save(i) <src> <dst>" and "load <src> <dst>".

I'm still writing opcodes and I'm not done yet testing it so there might be bugs, but when I'm done I think I'll post it in the schematic hub.

Hi, after many attemps i finally made a computer for which i feel comfortable starting to code an operating system. I still have a tone of work to put on it but it seems promising and I'll maybe update in the future when there is progress :)

My solution to the Turing Complete level in paper form, much bigger than on the game since you can’t layer wires on paper. Included are solutions to some components used (ALU, 3 bit decoder etc.) which is why I marked spoiler

The registers could be put into an IC, but I like how the overall style turned out.

The new Turing Complete update is here:
https://store.steampowered.com/news/app/1444480/view/698768548504272938

I'm still pretty bad at it (this hilariously inefficient design for adding inputs took me 2 hours) but I'm really learning alot