The culprit in file “Preferences” is "media_stream_mic" (→ .profile.content_settings.exceptions.media_stream_mic). Removing it—or just blocking the microphone for Stadia in chrome://settings—solves i...
See more...
The culprit in file “Preferences” is "media_stream_mic" (→ .profile.content_settings.exceptions.media_stream_mic). Removing it—or just blocking the microphone for Stadia in chrome://settings—solves it. I can start games after the first session. It apears to me that whatever Stadia contacts for voice-chat is faulty, throws an error, and any switch to the actual game streaming is being aborted by the (silent) error. Without a microphone made available everything works fine because the the erroneous path in Stadia's JS is not being taken or triggered. On any first and fresh Chrome/Chromium run I'm being asked whether to allow Stadia to access the microphone. As a human I'm too slow to react and grant the permission, hence the microphone is not available when the transition to game streaming happens and the error is not triggered on that very first start as well. (Please forward it to the devs, @ChrisFromGoogle , as I believe this could help and save time.) (I really wish I'd not have to do QA work for y'all for free.)