Update: Google have actually now released an upgrade that must resolve a significant bug affecting Journey To The Savage Planet. More listed below.
Journey To The Savage Planet landed on Google Stadia last month, but unfortunately it got here with a game-breaking bug that makes it unplayable. It’s a quite serious concern that you ‘d believe the designers would be dealing with ASAP. Google are in the process of moving those developers to new roles within the company after shutting down their studios earlier this month, and now no one seems to know who’s expected to be working on a repair.
It’s a quite serious problem that you ‘d think the developers would be working on ASAP. Journey To The Savage Planet was made by Typhon Studios, who were bought by Google in 2019. Stadia support said that they should get in touch with 505. 505 stated that all of the game code and data for Stadia was owned by Google, so there wasn’t anything they could do. I do hope a repair comes for players who’ve been enjoying the game on Stadia.
Journey To The Savage Planet was made by Typhon Studios, who were bought by Google in 2019. Regretfully, the studio was closed down when Google shut down their internal studios simply a couple of weeks back, which affected around 150 jobs. Google tells us “most” of those developers will be moving on to new roles within the company.
On Stadia, some gamers are unable to play the game at all since it freezes when they try choosing an alternative on the primary menu. Searching for a repair to this, Reddit user ” lordubuntu” contacted both Google and Journey To The Savage Planet’s publisher, 505 Games, who both seemed to point the finger at one another to state “that’s their problem”.
Stadia assistance said that they need to contact 505. Nevertheless, 505 stated that all of the game code and data for Stadia was owned by Google, so there wasn’t anything they might do. 505’s assistance stated that Google acted as publishers for the game on Stadia because they owned Typhoon Studios, so Google were the only ones that could really resolve the problem.
A talk about lordubuntu’s thread from a Stadia community supervisor, who writes: “I comprehend how aggravating this circumstance is, and I’m sorry for the delayed upgrade. We’re actively working with our partners to identify a fix, and I will do my finest to pass updates along.”
A comparable response on Stadia’s Twitter says they’re working with their “partner publisher” on a fix. I can’t help however question who they mean by that. If 505 didn’t deal with the Stadia variation, then surely it can’t be them?
I do hope a fix comes for gamers who’ve been taking pleasure in the game on Stadia.