CD Projekt quest designer discusses the "challenge" of developing Cyberpunk 2 for Unreal Engine
CD Projekt quest designer discusses the "challenge" of developing Cyberpunk 2 for Unreal Engine
Cyberpunk 2077's lead quest designer Pawel Sasko has shared a few thoughts on the next Cyberpunk game, the mysterious "…
Article based on the interview at by The Neon Arcade at https://www.youtube.com/watch?v=4b_o5ueZRF0
You're viewing a single thread.
There's an old adage in programming that you should almost never rewrite everything: https://www.onstartups.com/tabid/3339/bid/2596/Why-You-Should-Almost-Never-Rewrite-Your-Software.aspx
Going from their existing RED engine to Unreal is basically the same idea. Almost nothing from the original Cyberpunk game is going to be easily translated to the new platform. I think CDPR just set their development timeline back by at least 3 years.
set their development timeline back by at least 3 years or more.
This is based on the assumption that they'll finish the game before releasing it.
To be fair, in this case there is increased value because eventually the engine work requirements will be significantly reduced.
This isn't rewrite everything, it's basically remove a bunch of stuff and rewrite the rest.
Given how massive their game is, I'm doubtful. So much of what they did in the first game will have to be rebuilt. Compared to just reusing most of the original assets and code, this sounds like a lot more work.
Maybe, it might also be easier to reuse portions of the engine in Unreal Engine while using parts of Unreal (like its rendering engine) than you think though. Assets largely I'd expect to be portable or at least comvertable with a custom asset loader.
I'm talking a little out of my ass though, and neither of us is familiar with the code. Point being though, it's a little different moving engines than rewriting a complicated web server (a project I have been a part of and would not recommend).