if(Fishe)

7:53 I TOTALLY AGREE

Why? Cause I need a final project for my code and nothing else has been cool or fun enough... So, why not create my own game engine! No clue what I'm doing, but I'll figure it out...

this is awesome dude keep it up seriously super awesome stuff right over here in this video! NO REALLY KEEP US UPDATED YOU HAVE TO!!! O_O

how do you even make a game engine

for fun

i tried to make a game engine, now it just lies around as a reminder how much i suck at c++

I tried making my own engine a bunch of times, because pre-created things in Godot and Unity just annoyed me. After a few years of just making engines and never actually making games, I joined a gamejam for funsies and my mind was blown going back to Godot how easy everything felt. "Look, I don't even have to write another collision detection system, it's just there, and it works". tl;dr making my own engines made me really appreciate what pre-built engines give you and how much time they save you.

Fascinating stuff...

I want to make my own to learn how game engines do it. Plus the game idea I got needs a custom engine. Then another idea needs one to deal with millions of images being rendered on-screen and moved/animated. Maaaaaaay need a custom one there (definitely for the first).

Welp, guess I better go make a game engine

Unity is nice till you try to do something really specific, then its implementation is full of problems or stuff you think work one way won't, so you end up coding a heavily modify version of it or your own entirely. It is pretty slow to load, and from what people told me, it's REALLY a problem when you are working on a big project.

cool video!

Where can I find this gxp game engine?

I think every serious game programmer should make their own engine at some point for education purposes, it is a ton of fun and extremely rewarding. Existing engines are bloated and could be overkill for the type of game you're making, this might warrant another approach. I find it frustrating the amount of loading bars and waiting I have to do in these engines. It depends what your goal is, if you want to release game, writing a game engine for your FIRST game is a guarantee that you will not ship and burnout. There's a lot to making games than just the engine, game design, level design, gameplay, making things 'fun', and 'feel good' etc... Those are all things that you won't really get to experience in the game engine stage. My advice would be to make a few games using existing engines, to get good at those higher level skills, and to PROVE that you can make and FINISH a game, then come back and make a game in your engine if you so desire. At that point you've proven you know what you're doing, you know what it takes, so you can make better decisions in your engine design, what libraries to use, what shortcuts to take, and what battles to fight. You will also grow appreciation of how much work engines do for you, once you try to tackle your own art pipeline, animation system, collision detection and handling etc. Just my 2 cents learning the hard way. I would LOVE to have the runway now to make a (yet another...) custom engine for my PS1-inspired games, but I can't keep doing what I'm already good it and not work on my weaknesses, I would just get nowhere. In the end, just go for it, execute and learn, don't over think it, overthinking leads to indecision and nothing will get done.

2D engine: for fun! 3D engine: masochism

As someone who's currently growing white hairs with a C++ Vulkan renderer, the "horrors of Vulkan" definitely hit a bit home. Having said that, it's not /that/ bad once you cry with it for like a month!

i can 100% agree i still remeber the time i got my transfrom component to work and i could acualy fully utalise 3d thats probobly the most fun i had coding

making a game engine to escape having to use other annoying engines is where its at lmao. I started making my own 3D engine on top of love2D when the unity runtime fee bullshit went down. i was in the middle of making a commercial game in unity when they did that. I never really liked unity in the first place for how bloated and slow it was. plus I barely used any of its features cause i make alot of systems form scratch including collision. too much dead weight for no reason. 1 year later and now I got my game ported to my own engine and had a successful demo booth for my game at a indie showcase event. Making a game engine in the long term was the best decision I've made just cause i have a way to make games quickly the way I want and each new system and dev tool added makes development even easier.

Is simple, is the difference between needing 2GB of ram just to start the engine against needing less thann128 MB. Also, royalties...

I love Godot (it's read go-dot), its GDScript and C#, but I despise Unity, but your engine looks cool, so I maybe try it in feafture. I would love if some one would bring back Boo as scriping game langue from the death - its C# but with Python syntax.

I have bad experience with generic channel names, its imposisble to find them unless theyre really big like Cold Fusion. Consider slight change like: Cpt. Slock

I honestly find it fascinating that anyone would be interested in something as complicated as making a game engine. I was happy hearing about how much fun you're having and I found it interesting because that's not something I'd ever be interested in doing (too much work). I'm more interested in creating games but I definitely subscribed and I'd watch more of your videos!

When I was fresh out of college, I was all about making my own game engines because I wanted to have total control over everything. Turns out it's really hard to get anything as performant at high loads as the major game engines, and also if you're a solo dev, you're likely to cut some kind of corner that'll bite you later when something's coupled a bit tighter than it should be. Making an engine is a good exercise, but for how many YT vids I've seen of people talking about making their own engines, it seems like none of them are actually finishing their games, which doesn't surprise me much. Out-of-the-box engines definitely have their limitations, but they can typically be worked around with some elbow grease (or re-implementing the subsystem yourself, which you would've had to do anyway if you were making your own engine).

nice story telling!

Unity is slow for you to start up because it requires a good pc

the only guy on youtube who knows how to capitalize a title

Because I write games for the Commodore Plus/4. Each new game is a new game engine too.

zoomers finally discovering you can make your own game engine without resorting to industry slop and making le video essay about it. Very chungus epic le reddit karma.

c++ is more weakly typed than gdscript btw

1:37 reminds me of something

this is actually a good video good job man, shoutout plimbo Anyway, back to thinking about my game idea and not making it

This video was so enjoyable, I actually want to make my own engine now! Thanks!

rIght cuz i value my time i''d better do games than these side quests. Ngl this is a heck of achievement

3:43 Rain world? … Rain world: downpour? Edit: Yes, it most certainly is Rain world: downpour, and the song name is Overcast. Gosh I love indie game music, especially rain world’s.

i love the idea of building my own engine. but for now i just want to learn to make my own tools and stuff by combining building blocks that already exist. that's why i recently switched from godot to bevy, excited to see where this journey will lead me

Open Source your stuff

I like your perspective on this! I've been toying with the idea of making a game engine, but if I do I'll have to never expect to actually make a game with it. It sounds like a fun learning experience though

Really hoping that more people try out SDL3 because it's a relatively accessible way to get started with doing graphics programming on a near-Vulkan level but without being as overwhelming. Still gotta finish that tutorial....

neat!

Because it’s fun. You have to use whatever makes you want to get up and work on your projects every day. If that’s unity, unreal, godot, Defold… then great! But if that’s making your own engine, then that might be right for you. But it does affect how you work and what you can work on, eg writing your own engine instead of using unreal means you probably should give up on lumen+nanite photorealism. But as long as you’re ok with the trade offs, using your own engine is fine, regardless of what other people say. Plenty of great games are done in custom engines. I would say one thing though: you should make a game(or multiple little games/demos) first and refactor its code as you go into your engine, rather than trying to write an engine up front and then hoping to make a game with it later. This is because if you make the engine first, it’ll be forever before you actually can work on your game and then you likely will find out that the engine isn’t all that suited to your game or it’s hard to work with, by building the engine around your game (rather than building a game around your engine), you are guaranteed to get a design that works for your game, and that you work on features that your game actually needs and uses.

bro has only used java and C#, i couldent pick a worse entrypoint into programming if i tried! hope you are joking and if not get well soon!

awesome video

Thank you Caps Lock, you have convinced me to make my own engine. Do I need to? Absolutely not? Am I gonna try? Hell yeah.

I went into the rabbit hole of creating game engine for my game (against all recommendations) and found out that I enjoy programming game engines more than games themselves.

As much as i want to make my own engine too i dont think I have the confidence to do that, i hate this corporate bs with game engines nowadays . But really this is awesome and im looking forward to seeing updates on this project

Unity is great what so ever, don't mind people and do your stuff

programmer's ego or just programmer's fun... nothing wrong with it... but for an indie project for sure it' an overkill. Unity canceled runtime fee btw

1:09 🙄 duh, is pretty obvious, you are opening a project, it needs to load all your stuffs -.- also, if you are creating a project with a example template of course is going to be slow -.- is loading all the stuffs on the project. I can not believe people don't get that already, godot starts faster because godot is not even half the tech of unity or Unreal (the only game engines people knows) i don't think creating a game engine is fun, i think creating games is fun, that's why i prefer to use a prefab XD, but good luck with yours

More power to you! I don't see myself doing it though. The deepest I can see myself diving is using Raylib or something.