2043
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
2043 points (99.2% liked)
Games
32597 readers
1534 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
As I said, it depends on how it's built. And how proprietqry the engine is.
Unity from what I know supports universal code/mesh/texture formats, but if the devs opted for the "easier to use" proprietary systems- well, that's a problem.
Now what I don't know is how easy are scenes to export in Unity. They're probably built with Blender or something else though in most cases, unless Unity has drastically changed.
Assets are safe, but they often need to be re-rigged or re-formatted. It’s still a non-trivial task though. Levels will need to be rebuilt, open worlds have to be started almost from scratch, and a lot of other things I can’t think of off the top of my head.
The real problem is underlying systems. Unity often handles networking, render engines, game logic and most other things. The reason Unity was so popular was because it was easy to use (and free). Game code will need to be at minimum heavily refactored, if not rewritten, as anything that interfaces with the engine needs to be changed over. Just like you can’t just port c++ -> c# without major changes, you can’t port a game engine without major changes too.
Unless theyve built everything as a separate code bundle, only interacting with the engine at a bare minimum, there’s no way to change with minor impact. It’ll be a huge project that will also require the engineers to learn a new stack that behaves differently, further slowing down the process.