Cyberpunk 2077's engine lead says some of its legendary launch failures occurred because the alternative was even worse: "Either you do a T-pose or you crash hard... we prefer not to crash hard."

As someone who only played Cyberpunk 2077 for the first time after It's received its major 2.0 makeover, and I'm confident it's one of my favorite RPGs of the last decade. A real blast that I picked up again almost immediately – this time 100% the game with a Netrunner build – as soon as I played through it the first time.

But it wasn't always like that, was it? About four years ago, Cyberpunk was in the midst of its historically poor release when it was banned from the PlayStation Store entirely due to a wave of bug reports. Do you think Bethesda games are chaotic on day one? Cyberpunk 2077 hit the digital distribution platforms in millions of different pieces and they were all on fire.

But it could have been worse, if you can imagine it. In a major glitch in CDPR's comeback following the game's disastrous launch on Eurogamer, Cyberpunk's lead engine programmer Charles Tremblay narrowly collapsed Why The game was so legendary back then. As expected, it was a mixture of several factors. The first of these was the fact that old-fashioned spinning hard drives simply weren't up to the type of streaming the game required. But also? Sometimes the game could fail or crash completely, and the developers preferred option one.

According to Tremblay, Cyberpunk suffered from memory leaks. “Theoretically, the game could run indefinitely, and at some point we would run into fragmentation or memory issues.” Once you get to that point – which isn't hard, especially with the 8GB of RAM in the PS4/Xbox One era of consoles – you have no more space to deal with other things. “And then you have a choice,” says Tremblay, “either you do a T-pose or you fall hard. What do you prefer? We prefer not to fall hard.”

I'm also brave enough to admit that I prefer not to take a hard crash. T-posing is either captivating or funny – sometimes a bit of both – while sacrificing progress to crash is completely out of place. No wonder the developers made the decisions they did: letting the game freak out instead of crashing hard into the wall because there's no RAM left.

No doubt other developers make the same decision all the time on other games, and this won't be anything new for them. But for laypeople like you and me, it feels like a fascinating insight into the countless strange compromises that have to be made in development, especially in games as huge and unwieldy as Cyberpunk, with “a lot of complexity, a lot of interconnected ones systems”. per Tremblay. Put the thing in the hands of tons of players and things get weird. “You have all these permutations of conditions, you multiply them by a million people, and then you just have a weird error – you're like, 'Oh my God.'” Or, you know, you have the launch of Cyberpunk 2077 .

Cyberpunk 2077's engine lead says some of its legendary launch failures occurred because the alternative was even worse: “Either you do a T-pose or you crash hard… we prefer not to crash hard.”

You may also like...

Recent Posts

Cyberpunk 2077's engine lead says some of its legendary launch failures occurred because the alternative was even worse: “Either you do a T-pose or you crash hard… we prefer not to crash hard.”

You may also like...

Laura Loomer, who spread a conspiracy theory about 9/11, joins Trump in ceremonies commemorating the attacks

Record heat in summer in Death Valley National Park

Man accused of smashing car windows and setting fire in Moses Lake

Recent Posts