قالب وردپرس درنا توس
Home / Technology / Stadia developers can not fix the bugs in their own game because Google fired them

Stadia developers can not fix the bugs in their own game because Google fired them



Illustration for the article titled Stadia Developers Can't Fix The Bugs In Their Own Game Because Google Fired Them

Picture: Travel to Savage Planet

Except dismissal of around 150 developers, the strangulation of Google Stadia has left lots of early adopters well and truly in the swing. Stadia var injured from the start, and if the latest experience from Stadia users is any indication, it is certain that it does not give a positive impression on the way out.

One of the few games that Google actually owns – although it was first released on consoles and PCs before it debuted in Stadia – spring Travel to Savage Planet. Google acquired Typhon Studios before the end of 2019, and the agreement meant it Travel to Savage Planet was one of the few games that came free with the Stadia Pro subscription.

Typhon Studios was the first studio to be acquired by Google, but with the effective end of Google’s gaming ambitions, the developers there were unleashed with everyone else. For users still playing at Stadia – at least those who do not sue Google – it has caused a bit of a problem, because no one can fix their games.

Anyone who has tried to play Travel to Savage Planet – who only came to Stadia Pro a few weeks ago – has run into a number of errors, including freezing on the main menu, crashes, and hanging. And because it is at Stadia, where the game files are stored on a server farm far away from the PC, regular users have no responsibility to troubleshoot the problem themselves.

Can not play Travel in singleplayer or co-op a user reached out to the game’s publisher, 505 games. After being told by Stadia’s social team that they wanted to work with the publisher on a solution, the publisher said: Actually, we can not fix this for you at all.

Illustration for the article titled Stadia Developers Can't Fix The Bugs In Their Own Game Because Google Fired Them

Screenshot: Reddit (without lordubuntu)

“Unfortunately, there is nothing we can do from our end right now, since all the game code and data on Stadia are owned by Google,” 505’s support staffer said in an email.

In a follow-up a few days ago, another 505 support staff suggested that the user remind Google that Google is the one responsible for publishing everything on Google Stadium.

indefinite

Screenshot: Reddit (without lordubuntu)

As the original poster lordubuntu noted, the situation is a complete shit show. You can not really blame the original developers – Google fired them all, so it’s not really their fault to fix problems with Google’s service. (I’m sure they are not thrilled about leaving their customers, but would you at the same time lift a finger to help Google after they fired you and all your colleagues?) And Google’s support should know from the start that traditional publishers can not solve problems with Stadia as they could for a normal game.

That, of course, is not the fault of the individual support apparatus either. It’s just an absolute mess, albeit one that many expected given Google’s overview cancel projects. It is also worth remembering games are still coming to Stadia. “You can continue to play all your games at Stadia and Stadia Pro, and we will continue to bring new third-party titles to the platform,” Stadia’s Phil Harrison said in a blog post. earlier this month.

But if this is the quality of service users can expect when things go wrong, why would you want to invest more in your Stadia library – especially when better services exist?

This story originally appeared on Kotaku Australia.




Source link