Apart from the firing about 150 developersGoogle Stadia’s restriction has really let a lot of early adopters down. Stadia was slandered from the beginning, and if the latest experience from Stadia users is any indication, it certainly doesn’t leave a positive impression on the way out.
One of the few games Google actually owns – although it was first released on consoles and PC before making its Stadia debut – used to be Travel to the Savage PlanetGoogle has acquired Typhon Studios before the end of 2019, and the deal meant that Travel to the 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 shutdown of Google’s gaming ambitions, the developers were let go there with everyone else. However, for users still playing on Stadia: at least the ones that don’t sue Google – that caused a bit of a problem as there is no one around to fix their games.
Anyone who has tried to play Travel to the Savage Planet – which came to Stadia Pro only a few weeks ago – ran into a series of bugs, including freezing on the main menu Crashes, and hanging. And since it’s located on Stadia, where the game files are stored on a server farm far from your PC, regular users have no responsibility to fix the problem themselves.
G / O Media can receive a commission
Can’t play trip a user contacted in single player or co-op the publisher of the game, 505 Games. After the Stadia social team was told they would work with the publisher on a solution, the publisher said, “ Actually, we can’t fix this for you at all.
“Unfortunately, there is nothing we can do on our part at this point, as all game code and data on Stadia is owned by Google,” the 505 support agent said in an email.
In a follow-up a few days ago, another 505 Games support representative suggested the user remind Google that Google is responsible for publishing everything on Google Stadia
As the original poster lordubuntu pointed out, the situation is complete shit show. You can’t really blame the original developers – Google fired them all, so it’s not really their fault for troubleshooting Google’s service. (I’m sure they don’t like letting their customers down, but at the same time would you like to raise a finger to help Google after firing you and all of your colleagues?) And Google support should know from the outset that traditional publishers can’t fix Stadia issues like they could for a normal game.
It’s not the fault, of course of individual support staff. It’s just an absolute mess, albeit one many expected given Google’s track record cancel projectsIt’s also worth remembering that games are still coming to Stadia“You can continue to play all of your games on Stadia and Stadia Pro, and we will continue to bring new third-party titles to the platform,” said Stadia’s Phil Harrison in a blog post. earlier this month
But if this is the quality of service users can expect when things go wrong, why invest further in your Stadia library, especially when better services exist
This story originally appeared on Kotaku Australia