this post was submitted on 31 Dec 2025
127 points (97.0% liked)
Cyberpunk 2077
4806 readers
1 users here now
Everything Cyberpunk 2077
Rules
-
Be cool. No racism, sexism, homophobia, transphobia etc.
-
Mark spoilers and NSFW
Friends
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If you're specifically working on a game that stock UE5 can't do, e.g. you need to make the kind of far-reaching changes that Valve had to make to Source to make Portal possible, you end up with most of those problems even if you're doing it by modifying UE5 rather than modifying your in-house engine. You're still ending up with a custom engine at the end of the process and still need to make tooling for it and onboard everyone, even if it ends up fairly similar to stock UE5 due to being modified UE5. It doesn't necessarily work out any more scalable or sustainable than modifying an in-house engine once you're making this kind of change. The outcome ends up being that games that can't be made in close-to-stock UE5 just don't end up getting made.
If you continuously make games like that, sure! But CDPR doesn't do that.
I didn't say that they did, just that switching to UE5 can be a mixed bag rather than always unambiguously better. My original comment was pretty explicit about it not being applicable to CDPR.