this post was submitted on 12 Sep 2023
1182 points (99.0% liked)
Game Development
2814 readers
2 users here now
Welcome to the game development community! This is a place to talk about and post anything related to the field of game development.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You sound like you dont know anything about programming (at least engine programming). Most Engines have to run in something like assembly, else they would be too slow. (They use others too but Assembly is in like all, i am a junior dev so i could be wrong)
Assembly is already a large hurdle.
I mean it is "simple" as the arch linux type of "simple". (Nothing more than you need to run it and nothing more)
So the option is to learn assembly or hire someone (or multiple) who can, good luck by finding one that is capable of developing an engine that does not suck and does not cost a fortune.
Then you need to know what the engine should do.
If you "only" need 2D or even only some system to interact with the console you will be fine, maybe.
3D is a bit more complicated, the reason why there are so much 2D/2,5D games out supports this claim.
Then particle support if you want it...
Every feature you want has to be supported!
And every feature costs and maybe needs maintenance when bugs occur. Supporting an operating system is a feature too :)
So the engine has to be updated when a mayor OS update comes out
There are more points for why not to make an own engine and use one of the marked that fits ones needs even if it is closed source.
You where so fond of Godot so trying to help them might be a good starting point for you to life your ideals. I sincerely dont want to mock you with the sentence. If you can successfully help a larger open source project everyone is happy. If you can learn something new i am sure it can benefit you. I was only a bit mad because it felt like you are comparing engines with "weekend projects" what they are definitely not in the slightest.
Assembly usage is pretty minor in these engines. Tends to be for just a few very tight loops. It has to be redone for every platform, too. Assembly for x86-64 doesn't work on ARM. Hell, some things on 32-bit x86 won't even work on x86-64. You would never want to do more than a function of inline ASM here or there. It'd be a nightmare if you did.
That said, it's barely even touching on the complexity of modern engines. Unity and Unreal aren't just engines, they're a whole development ecosystem.
I'd like to jump out of the system for a moment and opine a few things:
And there's a very good reason for that: you are vastly understating how difficult it is to make something on the level of Unity or Unreal, and people here can see it. It's not merely difficult, but completely out of reach for anyone without hundreds of millions of existing revenue. Open source is not going to get you there anytime soon. By the time it could even get to the current level of the big two engines, those two would have already moved on to something even better.
It's not a choice between a corporate licensed engine or an open source one or an in-house one. It's a choice between a corporate engine and having a finished product in any kind of reasonable time frame, or having a finished product that's anything close to modern looking.
Now, I happen to agree with the statement "I want shorter games with worse graphics made by people who are paid more to work less and I'm not kidding". So if that's what you're getting at, then I agree. But know that this is what you're asking for.
That's a naive way of pretending to be above it all. People downvote for a reason, and it can be useful to think about those reasons. Meanwhile, while complaining that "You’re also not listening to what I’m telling you . . . " while clearly not even bothering to address most of my points.