@@octoson5944 TL;DR: How to make an engine varies a lot with what you want and how you wanna do it. IMO it's best to learn from using existing engines, using lower level frameworks, experience and practice. I realize this doesn't answer your request for resources, so sorry for that, but I hope it still helps in some way. I believe it would be hard to find some resource that accurately describes the process of making an engine because that is very dependent on the goals and methods of each engine. Of course there's some basic stuff, you probably want a way to render things, manage objects, do physics, etc., but that's about all that you can say that applies to most engines. How exactly you implement each of these can vary wildly, with so many different libraries and methods and techniques for all of them that will all also depend on what you want for your engine in particular. In my opinion, if you want to make an engine or learn how that process would work, you should learn from how other people did it and through practice. If you use one or multiple engines for an extended period of time, you start to get at least a basic feel for how it works under the hood and what an engine even needs to do in the first place. Also, from experience you can learn what you want or don't want for your engine. If you work with lower level graphics, physics, etc. you can understand how you would implement the systems yourself, and also what kind of abstractions the engines have to simplify this process, which you would also have to make for your own engine. What I did and would recommend is to make simple games without an engine, using a lower level framework (raylib is great!). Each time it felt like I was making the starting ground for an engine for each game, building abstractions on top of the framework. It's also always very useful to just look at how existing engines do things, Godot is great since it's free (as in freedom and as in free beer) and open source. Doing all this should give a great idea of how an engine works and what it would take to build one, at least that's how I learned what I needed to start building my own :3
@@octoson5944 Which type of game are you trying to build, 2d or 3d, multiplayer or singleplayer. Then question is why you want write engine, its for learning, curiosity, or you want just make your game?
I'm currently making a game engine, with features being the reason, and so far it's daunting. On a side note, I see some devs stating that they make their own engines to avoid making payments to the game engine owners.
Avoiding royalties is a valid reason to make your own engine. Just depends if you have the time and resources necessary to actually make an engine. It's a very time-consuming task so paying to use an existing one may be the better option.
Whatever feature you're trying to implement, Unity can probably do it easily with minimal scripting. Nothing falls into the 2nd category nowadays. It's sometimes the 1st but mostly the 3rd.
@@nick15684 it's also kind of dumb. You're assuming that your game is gonna be so big that taking that hit with the royalties will be a net detriment which I think relates neatly to an ego issue. The royalty issue is really only a concern if you're an established studio, your game is revolutionary kinda like Fez was, you have a huge marketing budget or you simply get insanely lucky but your game has to be good either way.
Noita is an engineering marvel. Every pixel is not only physical, it also can burn, evaporate, solidify and even melt. This game is THE definition of why you'd need your own engine And i won't even talk about the layers or the lore, this game really is its own little world
I remember watching tutorials and learning about game dev a few years ago and it was absurd how many people recomended creating your own game engine to beginners. Its like saying you gotta build your own canvas if you want to paint or make your own guitar if you want to be a guitarist.
Option 4- i just find it fun. I like writing stuff from scratch and i’d rather build a game from the ground up engine and all because i find joy in every step of the process.
Also Factorio , Because all of the belts and materials being 1million in production in and out of screen. They need to make it custom or your pc would burn and have 10 fps or none at all.
The first one has been my driver. learning is lotsa fun and even been programming for over 3decades I still find so many new things. Its also nice to try similar stuff on multiple platforms and also older hardware
The fourth would be, you don't want to deal with something that other engines come with, that you don't want. With some engines out there it's harder to remove all the stuff that you don't need bogging everything down, rather than making it all from scratch heavily optimized for performance. Some might have costs, licensing models or the like you don't want to deal with or other reasons like it.
Under point one is really great because if you learn how to make one you can create custom plugins for UE or any other engine and which leads into point 2 anyway. Always learn to adapt and improve not reinvent the wheel.
I can think of a 4th reason, that's valid And that's if your game is simple enough to be made with an extremely lightweight custom engine, it might be better to do that. Not that it can't be done with an existing engine, but that the engine is just overkill. It's similar to reason 2, but different enough I think
fez does not need a custom engine at the time, this is an example for inflated-ego.the 3d rotations of fez where also not 100% inuque at the release of fez, but fez refined them, just like there exists a portal-like game as a quake-mod, that is older than portal1, that let you place portals on VERY FEW surfaces, each surface being a longer script to toggle leaf-portals.
Path of Exile devs faced the same question and the reason they wrote the game from scratch was that 1) too expensive 2) nothing at the time would support the game's enormous complexity 3) would not be optimized for their instancing or systems.
I kinda wanna do that "Fez" thing where you can enter doors but it just perspective swaps into a new 2D plane for creating levels without a loading screen
This is the same as developing any programs in general. What he says casually about game engines is very much the same thing professors will tell you in undergrad classes about programming libraries. If I want to write code for a specific purpose, the best thing is to look for what individual tasks I need to implement and combine to achieve the code's purpose, and import libraries with modules that contain those individual tasks I need. That said, If I want to learn things and be a better coder/developer I might write them by hand as a training exercise, and see how (mostly worse) it is compared to existing libraries. But I prefer to "stand on the shoulders of giants" and not try to reinvent the wheel. It's redundant, and there are better things to spend time and effort on.
I remember when Konami made the Fox engine seem pretty good at the time mgs5 run at 60fps on ps4 it works on ps3 now it just makes Football games if they still using it.
A fourth reason, and the reason I'll be going back to the DirectX suite if Unity goes belly up, is size. I can make a full game on par with Final Fantasy II in DirectX smaller than a Unity program that's just a single blank scene. Download speeds may be blazing fast compared to the dark ages of dialup, but storage space is still limited. I can fill up a 1tb drive as fast as I filled a 20gb one in 1999 and I had to uninstall my favorite game because it took half of my 1tb drive.
I like how when I code my engine I'm extremely familiar with how everything works. When I use UE or Gadot or Unity I have to learn where they have hidden everything. When it's mine, then I know exactly where it is.
4th reason, Steal people's money. I forgot which game studio did it (they were small I think), but they tried to sell themselves, making a new engine for a new revolutionary game to get donations, they took forever to deliver practically nothing, practically thievery.
I have worked at so many companies where they pick #3... it's ridiculous... really wish we'd pick a commercial engine for our next project, but alas, we can't have nice things.
"Real programmers write their own fucking compilers. I wrote my own operating system." -King Terry Real ones make their own language with which to program their game.
The third one is basically CD Red building Cyberpunk engine and then bailing on it and finally putting it on unreal and then wow look at that the game actually works now
My third reason would be remembering what happened when Unity got under the administration of a "genius of finances" who tried to pull a fast one to "monetize Unity". That one got rough real fast...
Ego can be quite useful. Many advancements wouldn't have happened if some mathematician or engineer had been humble and thought "much better people have tried to solve this". Having said that, for most things you could probably just add features to Godot rather than start from scratch.
You forgot a 4th. Idk what exactly to define it as, but factorio is possible to make in unity godot or almost any other engine. The issue comes that optimizing those engines for factorio would be more work than making a new engine for factorio.
So go to an open source engine, like Godot? Sure you don't "own" the engine, but they aren't in a position to take your work away with a snap of their fingers. Unity also went back on their pricing model changes as far as I know.
You can absolutely benefit from a game from scratch even if you could have used an engine, think of Animal Well do you think it would have been so tiny in size if it used an engine? Nope, that game is like 33mb. Apart from this there are benefits like having the freedom to do whatever and keep things simple vs. generic.
Is getting upset at a company for not updating their engine since the dawn of time a valid reason to learn how to make an engine, make it and then give it to the company so I can enjoy the game longer?
If you want to be able to rerelease in 10 years or not pay out of your wazoo for consoles you absolutely have to use your own engine or an open source engine that you can compile and now how to change
Can I ask, how were you able to start a team to make games? Because I have ideas for games I wanted to make, but the best I can do is illustrate/draw my ideas out, though I wish I can do more then just that
One big missed reason is performance and memory constraints. Modern game engines are very bloated. There's no real reason for indie games to be taking hundreds of megabytes, let alone GBs. Triple A studios are particularly egregious with the space their games take up. There's also no reason for most indie games to be performing at less than 240 fps, unless you're ray-tracing or doing massive physics simulations or something.
Then we got… creation engine that’s been in service sense 2003… god I hate Bethesda still uses that thing. Loads quick easy to use but a pain to actually make shit in from what I’m told. I haven’t dared touch it but I watched people use it and the whole time they have either said “I’ve wasted away a lot of my life in this thing I understand it more then I do my self” or “this is the biggest piece of shit I ever worked on and now understand why mods and things take so long to make and fix in this god forsaken engine” yeah neither comment makes me feel like it’s a enjoyable experience.
this must be synchronicity, I'm currently learning how to build my own code to have a higher dimensional entity cast a "shadow" that is the player, it's just a tesseract gamespace but yea, it's so I can learn math not build a game
That's why he said making an engine to learn how and making an engine cause you can't find an engine that will express your ideas properly are both valid reasons to make a game engine. He was saying only a dip decides they are going to waste game creating time on making a new game engine for something that could be dumped out of unity or unreal in a month.
@omerhalitipekci2256 You might not need to make one but making one will teach you a big set of skills. Also there's so many resources available on "how to make a game engine" that simply watching a series through with some popcorn will give you ideas.
Teardown is another great example. The ENTIRE engine, from the raytraced voxel rendering to the super advanced physics were written mostly by one guy, Dennis Gustafsson.
Teardown is genuinely one of the few games I'd consider a 10/10. In the sense that there aren't really things I can complain about it. I love everything about it.
Programming a game is already hard enough, but making an own engine for it is a whole another level. Respect to devs who do that, especially Indie devs. Even AAA game Studios nowdays still use 10-20 year old game engines and just update them overtime.
@@OkOkOkIMightKnowYou Unity is still the most technically advance general purpose engine. Unreal is the most *powerful* general purpose engine. You can code basically everything in Unity with basekit or addons, but will falter on performance at times. Unreal has slightly less option with basekit or addons, but can do pretty good on performance with the available options. For a quick example, Unity thrives on 2D, varied lighting, and Rendering just as a quick example, meanwhile Unreal has difficulty on them, making a lot of Unreal Games look the same-y 3d graphics game. Hopefully Godot keeps getting their support and catches up to the years of Upgrades Unity has had.
Instructions unclear, im now running unreal in my toyota prius
But does it play Doom? :D
@@danielodonnell360 Probably not, but I bet it could play Outrun in a Crysis.
You kid, but Rivian vehicles do actually use Unreal Engine 5 for much of their UI
@@VirtualTrucker74 Frames of Doom can be rendered on bacterium, I think he can get the game working on a car.
it can do that sometimes
My reasons:
1. I like doing things from scratch.
2. I like learning.
3. Because I can.
based!
Building top down 2d mmorpg game from scratch working alone will take you few years :)
do u have any resources for making a game engine? ive been wanting to at least learn how it works but i havent been able to find many good resources.
@@octoson5944 TL;DR: How to make an engine varies a lot with what you want and how you wanna do it. IMO it's best to learn from using existing engines, using lower level frameworks, experience and practice.
I realize this doesn't answer your request for resources, so sorry for that, but I hope it still helps in some way.
I believe it would be hard to find some resource that accurately describes the process of making an engine because that is very dependent on the goals and methods of each engine. Of course there's some basic stuff, you probably want a way to render things, manage objects, do physics, etc., but that's about all that you can say that applies to most engines. How exactly you implement each of these can vary wildly, with so many different libraries and methods and techniques for all of them that will all also depend on what you want for your engine in particular. In my opinion, if you want to make an engine or learn how that process would work, you should learn from how other people did it and through practice. If you use one or multiple engines for an extended period of time, you start to get at least a basic feel for how it works under the hood and what an engine even needs to do in the first place. Also, from experience you can learn what you want or don't want for your engine. If you work with lower level graphics, physics, etc. you can understand how you would implement the systems yourself, and also what kind of abstractions the engines have to simplify this process, which you would also have to make for your own engine. What I did and would recommend is to make simple games without an engine, using a lower level framework (raylib is great!). Each time it felt like I was making the starting ground for an engine for each game, building abstractions on top of the framework. It's also always very useful to just look at how existing engines do things, Godot is great since it's free (as in freedom and as in free beer) and open source. Doing all this should give a great idea of how an engine works and what it would take to build one, at least that's how I learned what I needed to start building my own :3
@@octoson5944 Which type of game are you trying to build, 2d or 3d, multiplayer or singleplayer. Then question is why you want write engine, its for learning, curiosity, or you want just make your game?
I'm currently making a game engine, with features being the reason, and so far it's daunting. On a side note, I see some devs stating that they make their own engines to avoid making payments to the game engine owners.
Avoiding royalties is a valid reason to make your own engine. Just depends if you have the time and resources necessary to actually make an engine. It's a very time-consuming task so paying to use an existing one may be the better option.
@@nick15684 Or using engines that don't ask your payment? Open source is an option yknow
Whatever feature you're trying to implement, Unity can probably do it easily with minimal scripting. Nothing falls into the 2nd category nowadays. It's sometimes the 1st but mostly the 3rd.
@@nick15684 it's also kind of dumb. You're assuming that your game is gonna be so big that taking that hit with the royalties will be a net detriment which I think relates neatly to an ego issue. The royalty issue is really only a concern if you're an established studio, your game is revolutionary kinda like Fez was, you have a huge marketing budget or you simply get insanely lucky but your game has to be good either way.
Noita is an engineering marvel.
Every pixel is not only physical, it also can burn, evaporate, solidify and even melt.
This game is THE definition of why you'd need your own engine
And i won't even talk about the layers or the lore, this game really is its own little world
I remember watching tutorials and learning about game dev a few years ago and it was absurd how many people recomended creating your own game engine to beginners. Its like saying you gotta build your own canvas if you want to paint or make your own guitar if you want to be a guitarist.
Fez is one of the dopest games I've ever played
i still can't comprehend how anyone makes an engine.
So glad I found this guy. I'm finding games I've never heard of and my child like gaming experience has been brought back after years of jaded gaming
Vortex Game Engine - Making it coz 1. I can 2. I want to 3. It is a flex 4. It will look good on my github account 5. EGO
Games that required custom engines are some of my favorites:
Noita
Teardown
No Man’s Sky
Dwarf Fortress
Cube World
"Make an engine"
C++: come to me baby. by the time you're done, you'll have got your engine and some suicidal thoughts
Option 4- i just find it fun. I like writing stuff from scratch and i’d rather build a game from the ground up engine and all because i find joy in every step of the process.
Also Factorio , Because all of the belts and materials being 1million in production in and out of screen.
They need to make it custom or your pc would burn and have 10 fps or none at all.
MANY game studios have fallen on their arse because they refused to pay for an engine, but wanted to make their own.
Number 4, you don't want other companies who rely on developers who use their engine to start demanding an abussive cut of your work.
The first one has been my driver. learning is lotsa fun and even been programming for over 3decades I still find so many new things. Its also nice to try similar stuff on multiple platforms and also older hardware
_"Neat game. What engine is it running on?"_
Commodore BASIC
The fourth would be, you don't want to deal with something that other engines come with, that you don't want. With some engines out there it's harder to remove all the stuff that you don't need bogging everything down, rather than making it all from scratch heavily optimized for performance. Some might have costs, licensing models or the like you don't want to deal with or other reasons like it.
Under point one is really great because if you learn how to make one you can create custom plugins for UE or any other engine and which leads into point 2 anyway. Always learn to adapt and improve not reinvent the wheel.
Maaaan I loved FEZ. RIP FEZ II.
Wow i never saw that 2D Plattform game. Its actually a nice idea
#4 performance,
#5 no lockin to expensive engines
I can think of a 4th reason, that's valid
And that's if your game is simple enough to be made with an extremely lightweight custom engine, it might be better to do that.
Not that it can't be done with an existing engine, but that the engine is just overkill.
It's similar to reason 2, but different enough I think
oh I see the point
I def need this when making story RPG with rpgmaker. all that battle parameters are never needed 😓
fez does not need a custom engine at the time, this is an example for inflated-ego.the 3d rotations of fez where also not 100% inuque at the release of fez, but fez refined them, just like there exists a portal-like game as a quake-mod, that is older than portal1, that let you place portals on VERY FEW surfaces, each surface being a longer script to toggle leaf-portals.
Number 4: You're targetting a platform that doesn't have a pre-made general purpose engine.
Super paper Mario (2007) was a 2d platformer inside of a 3D environment so I wouldn’t say it was never heard of.
He said Noita perfectly. It is finnish for "witch".
Fez blew my mind
Shout out for shouting out FEZ
i watched mikeakaB phony play it
it seemed so much fun and music was great
Path of Exile devs faced the same question and the reason they wrote the game from scratch was that 1) too expensive 2) nothing at the time would support the game's enormous complexity 3) would not be optimized for their instancing or systems.
I kinda wanna do that "Fez" thing where you can enter doors but it just perspective swaps into a new 2D plane for creating levels without a loading screen
A: hey mr SquareEnix , why do you wanna make engine ?
SE : 3 x 3
i would love to hear this man voice some of Cayde-6's lines from destiny
You missed Option 4, it's fun.
This is the same as developing any programs in general. What he says casually about game engines is very much the same thing professors will tell you in undergrad classes about programming libraries. If I want to write code for a specific purpose, the best thing is to look for what individual tasks I need to implement and combine to achieve the code's purpose, and import libraries with modules that contain those individual tasks I need. That said, If I want to learn things and be a better coder/developer I might write them by hand as a training exercise, and see how (mostly worse) it is compared to existing libraries. But I prefer to "stand on the shoulders of giants" and not try to reinvent the wheel. It's redundant, and there are better things to spend time and effort on.
I love Fez
I thought this dude was talking about car engines
I remember when Konami made the Fox engine seem pretty good at the time mgs5 run at 60fps on ps4 it works on ps3 now it just makes Football games if they still using it.
Fez! I never beat it. So many good little games in my library that Ive never finished.
there's the easy way to do things, and then there's the right way
That 2D/3D existed on an old PSP game about solving puzzles by a sleepy guy
I shouldn't be surprised that you can just make an engine lol
Remember, building your own engine for ego is only valid if you use your own compiler and programming language. Rip Terry
What if my ego is so big that I think that I can learn how to make an engine, but actually can't?
Super paper mario on the wii was also a 2d platformer on a 3d world
well, that person who made a 3D Geometry Dash map just made a game engine inside of a fucking game!
I always liked the serious engine by croteam
Fez is an awesome game.
Cost to save is #4 for major game studios.
Or you're john carmack, 20th level dev wizard and master of the great powers.
A fourth reason, and the reason I'll be going back to the DirectX suite if Unity goes belly up, is size. I can make a full game on par with Final Fantasy II in DirectX smaller than a Unity program that's just a single blank scene.
Download speeds may be blazing fast compared to the dark ages of dialup, but storage space is still limited. I can fill up a 1tb drive as fast as I filled a 20gb one in 1999 and I had to uninstall my favorite game because it took half of my 1tb drive.
I so badly want to make a visual script engine for pygames just to learn it and have a “fun” large scale project.
I like how when I code my engine I'm extremely familiar with how everything works. When I use UE or Gadot or Unity I have to learn where they have hidden everything. When it's mine, then I know exactly where it is.
That was hot af.
I’m buying FEZ just to pay my respects
Well, there was a game called 'Nebulus' on ZX Spectrum which had 3d tower rotating so this is definitely not the first time
Ah, quake 2 engine is where it's at
Tomba! came out in like, 1997 and did 2d in a 3d world.
I made j2dge because I wanted to learn how to make an engine and wanted to share it with everyone
That was also possible in captain toad treasure tracker lol
4th reason, Steal people's money.
I forgot which game studio did it (they were small I think), but they tried to sell themselves, making a new engine for a new revolutionary game to get donations, they took forever to deliver practically nothing, practically thievery.
I have worked at so many companies where they pick #3... it's ridiculous... really wish we'd pick a commercial engine for our next project, but alas, we can't have nice things.
"Real programmers write their own fucking compilers. I wrote my own operating system."
-King Terry
Real ones make their own language with which to program their game.
Fez was revolutionary you say?
"Revolutionary" lol
The third one is basically CD Red building Cyberpunk engine and then bailing on it and finally putting it on unreal and then wow look at that the game actually works now
Crush on the PSP did the same thing as Fez 5 years earlier
My third reason would be remembering what happened when Unity got under the administration of a "genius of finances" who tried to pull a fast one to "monetize Unity". That one got rough real fast...
I'd say that there's a secret 4th reason called "for funsies" but that probs falls under learning doesn't it
Ego can be quite useful. Many advancements wouldn't have happened if some mathematician or engineer had been humble and thought "much better people have tried to solve this".
Having said that, for most things you could probably just add features to Godot rather than start from scratch.
Wow, so galaxy brained, crazy
that reminds me, i never finished playing fez...and that i need to try noita bc it's been sitting in my library for a while
Noita mentioned! 🎉
I think the unicorns of engines are the ones that can run amazing with extremely weak hardware.
You forgot a 4th.
Idk what exactly to define it as, but factorio is possible to make in unity godot or almost any other engine. The issue comes that optimizing those engines for factorio would be more work than making a new engine for factorio.
My entire life is based on the third
I've been wanting to learn how to make a voxel engine to fulfill the vision for my game. Any ideas on where to start learning?
4 you own it
it’s funny that he talks about unity engine when they made changes to its pricing model.
So go to an open source engine, like Godot? Sure you don't "own" the engine, but they aren't in a position to take your work away with a snap of their fingers. Unity also went back on their pricing model changes as far as I know.
Would there be scenarios where a feature you want would be possible in another engine, but could be implemented more efficiently if you made your own?
Eyy, i was making an engine before this (:
You can absolutely benefit from a game from scratch even if you could have used an engine, think of Animal Well do you think it would have been so tiny in size if it used an engine? Nope, that game is like 33mb.
Apart from this there are benefits like having the freedom to do whatever and keep things simple vs. generic.
Ego so big had to make my own os
Is getting upset at a company for not updating their engine since the dawn of time a valid reason to learn how to make an engine, make it and then give it to the company so I can enjoy the game longer?
If you want to be able to rerelease in 10 years or not pay out of your wazoo for consoles you absolutely have to use your own engine or an open source engine that you can compile and now how to change
I love fez
What if I don't need it but my big ego helps me learn? Eh?
Can I ask, how were you able to start a team to make games?
Because I have ideas for games I wanted to make, but the best I can do is illustrate/draw my ideas out, though I wish I can do more then just that
Shi i go straight at 3
One big missed reason is performance and memory constraints.
Modern game engines are very bloated. There's no real reason for indie games to be taking hundreds of megabytes, let alone GBs. Triple A studios are particularly egregious with the space their games take up.
There's also no reason for most indie games to be performing at less than 240 fps, unless you're ray-tracing or doing massive physics simulations or something.
super paper mario > Fez
minecraft made an engine
Own custom engines? Sounds like Japanese companies up until recently.
Then we got… creation engine that’s been in service sense 2003… god I hate Bethesda still uses that thing. Loads quick easy to use but a pain to actually make shit in from what I’m told. I haven’t dared touch it but I watched people use it and the whole time they have either said “I’ve wasted away a lot of my life in this thing I understand it more then I do my self” or “this is the biggest piece of shit I ever worked on and now understand why mods and things take so long to make and fix in this god forsaken engine” yeah neither comment makes me feel like it’s a enjoyable experience.
Love your videos. Do you use a mouse to sketch or a pen. If it’s the latter, which one ? Thanks.
this must be synchronicity, I'm currently learning how to build my own code to have a higher dimensional entity cast a "shadow" that is the player, it's just a tesseract gamespace but yea, it's so I can learn math not build a game
We might not need to make an engine. But we should learn how it is done.
That's why he said making an engine to learn how and making an engine cause you can't find an engine that will express your ideas properly are both valid reasons to make a game engine. He was saying only a dip decides they are going to waste game creating time on making a new game engine for something that could be dumped out of unity or unreal in a month.
@omerhalitipekci2256 You might not need to make one but making one will teach you a big set of skills. Also there's so many resources available on "how to make a game engine" that simply watching a series through with some popcorn will give you ideas.
you should learn how to make clay bricks so you dont freeze to death in the winter.
@@durden91tyler There's always 1 guy who derails the conversation onto clay bricks. Who is paying you people
So what you are saying is you should make one. 😅
Teardown is another great example. The ENTIRE engine, from the raytraced voxel rendering to the super advanced physics were written mostly by one guy, Dennis Gustafsson.
I remember when the game was just a tech demo from the guy all these rears before.
I love Teardown
@@TeardownDestructionClipswho could have thought
i had no idea they done all that too. i probably buy the game just cause that lol.
Teardown is genuinely one of the few games I'd consider a 10/10.
In the sense that there aren't really things I can complain about it. I love everything about it.
We might not need to make an engine. But we should learn how it is done.
Programming a game is already hard enough, but making an own engine for it is a whole another level. Respect to devs who do that, especially Indie devs. Even AAA game Studios nowdays still use 10-20 year old game engines and just update them overtime.
That's 'cause they mostly make the same/similar sort of games they did 10-20 years ago. Why make a new engine if the mechanics are the same?
Unreal is a 20 year old game engine updated over time. It’s the most technically advanced general purpose game engine rn
@@OkOkOkIMightKnowYou Unity is still the most technically advance general purpose engine. Unreal is the most *powerful* general purpose engine. You can code basically everything in Unity with basekit or addons, but will falter on performance at times. Unreal has slightly less option with basekit or addons, but can do pretty good on performance with the available options.
For a quick example, Unity thrives on 2D, varied lighting, and Rendering just as a quick example, meanwhile Unreal has difficulty on them, making a lot of Unreal Games look the same-y 3d graphics game.
Hopefully Godot keeps getting their support and catches up to the years of Upgrades Unity has had.
Looking at you, Bethesda.
my friend coded a rudimentary physics engine back in high school brother is cracked
Hearing "falling everything engine" just unlocked a bunch of memories of the falling sand games i played when i was younger
That's basically the pitch of Noita: those sandboxes, but also you're a wizard.
Noita is actually inspired by that exact game. One of the devs talked about it in a presentation about the making of Noita IIRC
Noita: falling sand games if the sand also killed you
@@Dracomancili wizard sandspiel
falling sand, hell of falling sand, powder game, powder game 2
good fuckin times