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.
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.