CyberChud, a TempleOS 3D game engine

I was always impressed with your ResetEra ban-scraping site, but this is pretty cool too. I'm not sure Terry would have necessarily approved of the content/context, but he would have been pleased to see dev work put in and a functional piece of software get used and distributed, big ups!
 
When I run it in VMWare the game opens but freezes after a few seconds, the frame counter at the top just says infinite. I gave it 4 cores and 8gb of RAM, am I retarded and doing something wrong? I've never used a VM before.
I haven't experienced that. If there is a serious warning or error it will pipe it out over serial port. I've been using 4 cores and 4GB and it's fine. The other thing I can say is make sure you set it to "Other 64-bit". More serious debugging would involve running a debug build and watching the serial output.

I'll be uploading a WASM build shortly.
 
Fucking sucks that Terry ended up the way he did. Guy was clearly insanely talented. He was the one true "Comfycow": never malicious, just weird in an oddly delightful and sometimes genius way.
You did him justice OP. Sneed on in caring for God's Temple.
Oh, and he also turned out to be very much right about glowniggers and the way they glow in the dark. We didn't listen to you Terry...
 
WASM build is up, URL subject to change: https://cyberchud.kiwifarms.gg/cyberchud-bin.html

If you have issues, refresh the tab, seriously, refresh it again until it's working. If it's working, try refreshing a few times until it stops working. If you don't like the state of emscripten, just refresh. WASM has never stopped being a delicate fragile neurotic mess.
 
This is genuinely incredible.
OK I have a favor to ask.

I am a dev and I do exactly what null was lambasting this afternoon. I write in Python and typescript, I create apis and frontends for genai applications and I deploy to a big container orchestration platform for a living. I love what I do tbh.

But... I know nothing about memory allocation or cpu usage or anything low level. So what can I do to learn? C? Rust? Go? Read a book about assembly?

If anyone can recommend a project I can build to help understand these concepts, to learn a compiled language, and make me a better programmer I'd appreciate it. I also watched a video by Jonathan Blow (who apparently is hated by the troons? I dunno why) where he was basically saying exactly what Josh was saying this afternoon.
 
You magnificent bastard
TerryDavis.jpg
RiP Terry. Miss you big guy.
 
Unit
This is genuinely incredible.
OK I have a favor to ask.

I am a dev and I do exactly what null was lambasting this afternoon. I write in Python and typescript, I create apis and frontends for genai applications and I deploy to a big container orchestration platform for a living. I love what I do tbh.

But... I know nothing about memory allocation or cpu usage or anything low level. So what can I do to learn? C? Rust? Go? Read a book about assembly?

If anyone can recommend a project I can build to help understand these concepts, to learn a compiled language, and make me a better programmer I'd appreciate it. I also watched a video by Jonathan Blow (who apparently is hated by the troons? I dunno why) where he was basically saying exactly what Josh was saying this afternoon.
Unironically, the Pokémon Crystal disassembly is a great way to learn memory allocation and how a low level programming language interacts with the hardware. It helps that there’s functionality tutorials as well as extensive documentation of the gameboy’s specific brand of assembly.
 
I was always impressed with your ResetEra ban-scraping site, but this is pretty cool too. I'm not sure Terry would have necessarily approved of the content/context, but he would have been pleased to see dev work put in and a functional piece of software get used and distributed, big ups!
He would most likely called CrunkLord a nigger but still high praise in my eyes.

This is genuinely incredible.
OK I have a favor to ask.

I am a dev and I do exactly what null was lambasting this afternoon. I write in Python and typescript, I create apis and frontends for genai applications and I deploy to a big container orchestration platform for a living. I love what I do tbh.

But... I know nothing about memory allocation or cpu usage or anything low level. So what can I do to learn? C? Rust? Go? Read a book about assembly?

If anyone can recommend a project I can build to help understand these concepts, to learn a compiled language, and make me a better programmer I'd appreciate it. I also watched a video by Jonathan Blow (who apparently is hated by the troons? I dunno why) where he was basically saying exactly what Josh was saying this afternoon.
Learn holy c you nigger.

If not that, find a dogshit Linux game, get it running and a start tweaking it. Nigger.
 
This is genuinely incredible.
OK I have a favor to ask.

I am a dev and I do exactly what null was lambasting this afternoon. I write in Python and typescript, I create apis and frontends for genai applications and I deploy to a big container orchestration platform for a living. I love what I do tbh.

But... I know nothing about memory allocation or cpu usage or anything low level. So what can I do to learn? C? Rust? Go? Read a book about assembly?

If anyone can recommend a project I can build to help understand these concepts, to learn a compiled language, and make me a better programmer I'd appreciate it. I also watched a video by Jonathan Blow (who apparently is hated by the troons? I dunno why) where he was basically saying exactly what Josh was saying this afternoon.
Progress is iterative. You don't really need to know memory management or how the memory stack works in python or JS to use them. An electronic motor is an important part of a drill, but I have no idea how the motor itself works. No one on a job site or during a build has ever shamed me for not knowing how an electronic motor works. Don't feel bad about not knowing because you really don't need to.
Now if you really want to know how the motor works. Learn C and then use LEX/YACC to make a basic compiler with function calls. I would recommend writing it to output x86 assembly as a text file. Implementing function calls is really important because then you understand how a stack works. You can cheat if you want to by just using the same three registers for all ops, and off loading to memory after each op, but you must make your own symtable implementation.
 
Last edited:
Back