68
CD Projekt quest designer discusses the "challenge" of developing Cyberpunk 2 for Unreal Engine
(www.rockpapershotgun.com)
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 13 Nov 2023
68 points (87.0% liked)
Games
32449 readers
1157 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
Aka "we don't know the engine well enough yet to be aware of bottlenecks during our concepting phase and that's challenging."
They haven't even seriously started on implementation with the engine yet for Cyberpunk. This is somewhat of a nothing article that's trying to get clicks by making a very normal thing seem like a potential controversy.
I don't see where it's trying to make it sound controversial. Switching game engines isn't a "normal" thing developers usually do very often, especially after releasing such high-profile games with an in-house engine.
And with how often you see gamers demand developers "just use a different engine" to solve some specific complaint I think it's reasonable to remind people why that isn't usually a good idea.
It's not completely uncommon for a company to transition to a new engine between games when one fails to provide a sufficient solution for where they want to take the sequels.
Or just if daddy EA decides everyone needs to use Frostbite.