- Don’t roll out your own crypto suite
- Don’t write your own game engine
- Don’t create your own OS from scratch
- Don’t build another multipurpose framework
- …
Whom am I kidding, go do all of that! Learn why you most probably shouldn’t 😆
Ew, knowledge and experience, pweh disgusting
I want to learn how to write a physics engine.
Those are easy, unless you want 128bit resolution, relativistic effects, collisions, or fancy stuff like that.
PS: Bonus points if you write one without collision detection, then sell it as a game on Steam.
PS2: Super Bonus points if you make it 64bit, then keep crowd-funding it for 10 years.
What if I make an OS that’s also a game engine?
Hear me out: a fully fledged desktop environment, like KDE Plasma or Gnome, but it’s a 3D world - “windows” are just walls, the file explorer is just a bunch of procedurally generated condos, and you get a Gmod physics gun to move stuff around.
Soooo… Microsoft Bob in 3d?
Microsoft bob in 3D with a Gmod physics gun
Making your own engine is worthwhile learning experience. The same as trying to recreate any of the foundational tools that you use. Might not be the fastest or best way to make a game but a good way to make yourself a better developer.
Not the fastest
This is my 4th Vulkan related “project” and 2nd attempt at making something other than a glorified tutorial workspace in 6 years, and it took me 4 weeks to draw this stuff with minimal technical debt.
I could just use an existing game engine, but what’s the fun in not manually sorting all draw commands by mesh>pipeline>material and hunting synchronization hazards by just looking at funny glyphs for extended periods of time?
deleted by creator
Eh, at this point it happens every 3 commits, you get used to abusing gdb (since valgrind just dies).
I hope the police doesn’t find my unregistered breakpoint minigun…
GET OUT. OF MY CAR. NOW
Why are you yelling at me?
