2048
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 14 Sep 2023
2048 points (99.2% liked)
Games
32561 readers
649 users here now
Welcome to the largest gaming community on Lemmy! Discussion for all kinds of games. Video games, tabletop games, card games etc.
Weekly Threads:
Rules:
-
Submissions have to be related to games
-
No bigotry or harassment, be civil
-
No excessive self-promotion
-
Stay on-topic; no memes, funny videos, giveaways, reposts, or low-effort posts
-
Mark Spoilers and NSFW
-
No linking to piracy
More information about the community rules can be found here.
founded 1 year ago
MODERATORS
Because changing the engine in an existing project is a huge pita that requires many, many hours and possibly in some cases a full rewrite.
This also applies to games that would be released in 2023 or 2024.
Nobody should be considering Unity for a new project, but it's understandable to make either decision for many existing projects.
Ripping out the engine of your game isn't a trivial thing.
Many many hours is a massive understatement.
Thousands and thousands of hours is more appropriate
I don't know how you could change the engine without rewriting the entire thing basically from scratch.
It really depends on how modular their codebase is. The Doom 1/2 modern ports they did in 2019 use Unity. But it's actually still the original Doom underneath and just using Unity for input and output to make porting easier
I agree, although a lot of the work going into a game is the game design, art, and iteration, and not just the programming and rigging. And it may actually be a catalyst to rewrite parts better
Strongly disagree. While a lot of work does go on to art assets which should be simpler to migrate, the code is absolutely what makes the game. There are tons of very successful games with low quality or stock assets, there are very few popular games with broken code.
Even then, it's still a lot of effort to check every asset you're using to ensure they work as expected in your new engine.
I agree for a specific scenario: if you don't use many unity specific packages or assets. Then, perhaps you are correct, still I don't blame anyone staying even in that case, as it is still daunting to take on such a task.
You're completely right
In this case it sounds like they were talking about their next game rather than a current project.
"has been hard at work these past 2+ years"
That doesn't sound like a current project to you?
I didn't click through and was going based on the headline. My mistake.
Their next game would be a current project.
Yeah, you're right. I was thinking of it in terms of current project -> next project, but I see that's not what was meant.