Apart from the dismissal of about 150 developers, the predicament of Google Stadiums has let down a bunch of early adopters. Stadium was maligned from the beginning, and if the latest experience from Stadia users is an indication, it is sure not to leave a positive impression on the road to the outside.
One of the few games that Google actually owns – although it was first released on consoles and PC before it made its Stadia debut – wash Travel to the Savage Planet. Google acquired Typhon Studios before the end of 2019, and the agreement meant it Travel to the Savage Planet was one of the few games that came free at the Stadia Pro subscription.
Typhon Studios was the first studio Google acquired, but with the effective closure of Google’s ambitions to play, the developers there let everyone else go. For users still playing on Stages, however – at least those who do not accuse Google – it caused a bit of a problem because there is no one to fix their games.
Anyone who tried to play Travel to the Savage Planet – who only came to Stadia Pro a few weeks ago – ran into a series of bugs, including freeze on main menu, collapse, en hang. And because it is on Stages, where the game files are stored on a server farm, far away from your computer, regular users have no task to solve the problem themselves.
G / O Media can get a commission
Can not play Travel in single player or collaboration, a user after the game’s publisher, 505 Games. After the social team of Stadia said that they would work with the publisher on a solution, the publisher said: We can actually not fix it for you at all.
“Unfortunately, at the moment we can not do anything on our part because all the game code and data on Stadia are in the possession of Google,” 505 support staff said in an email.
In a follow-up a few days ago, another 505 support staff from the Games suggested that the user remind Google to Google is responsible for publishing everything on Google Stadiums.
As the original poster lordubuntu noted, the situation is a complete shitshow. You can not really blame the original developers – Google fired them all, so it’s not really their fault to fix problems. (I’m sure they are not excited about letting their customers down, but would you at the same time raise a finger to help Google after firing you and all your employees?) And Google’s support should be from the beginning that traditional publishers can not solve problems with Stadia as for a normal game.
Of course this is not the fault of the individual support staff. It’s just an absolute mess, though one that many expected, given Google’s record cancel projects. It’s also worth remembering games still coming to Stadiums. “You can continue to play all your games on 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 that users can expect if things go wrong, why invest further in your Stadia library – especially when better services exist?
This story originally appeared on Kotaku Australia.