cancel
Showing results for 
Search instead for 
Did you mean: 

JohnZoidberg's Posts

Hello @egesteve  It may depend on whether you've kept macOS updated, but if you want to give it a quick try, I would fire up Destiny 2 for free and see how well it works for you on that machine: ht... See more...
Hello @egesteve  It may depend on whether you've kept macOS updated, but if you want to give it a quick try, I would fire up Destiny 2 for free and see how well it works for you on that machine: https://stadia.google.com/games/destiny-2  Even if Destiny 2 isn't your thing, it should give you an indication if your hardware is capable of playing Stadia games. Do keep in mind the network requirements, though – Stadia requires a steady, reliable network. I would try to connect via Ethernet or a very strong 5GHz WiFi connection just to be sure your test is as accurate as possible.
Hello @Zuro  As an avid Call of Duty player myself, I'd love to see this as well. But, it's really up to the developer and publisher to make this happen, so reaching out to them to let them know yo... See more...
Hello @Zuro  As an avid Call of Duty player myself, I'd love to see this as well. But, it's really up to the developer and publisher to make this happen, so reaching out to them to let them know you'd like to see it may be the best thing you can do.
Hello @cheatah3344  Google doesn't typically announce their plans for new features like this, so it's hard to know whether this is something they already have in the works or not. Personally, I thi... See more...
Hello @cheatah3344  Google doesn't typically announce their plans for new features like this, so it's hard to know whether this is something they already have in the works or not. Personally, I think the strongest use-case for enabling Bluetooth in the controller would be to connect it to a phone instead of using a USB cable when that phone isn't on WiFi, which sounds like what you'd like to see as well. The best advice I can provide is to use the "Feedback" feature in the Stadia app to let Google know this is something you'd like to see.
Hello @Iustin  If you buy a game with a Stadia Pro discount while you have Stadia Pro, it's yours to keep and play as much as you want even after you cancel your Stadia Pro subscription. You will j... See more...
Hello @Iustin  If you buy a game with a Stadia Pro discount while you have Stadia Pro, it's yours to keep and play as much as you want even after you cancel your Stadia Pro subscription. You will just fall back to 1080p and Stereo audio, and you'll lose access to any Stadia Pro games you "claimed", but you will not lose access to any game you purchased.
Hello @RedLion  The Founder Edition bundle was a perquisite of being a founder. Having a founder badge and #0000 number is also a perk of being a founder. Having possession of a founder bundle does... See more...
Hello @RedLion  The Founder Edition bundle was a perquisite of being a founder. Having a founder badge and #0000 number is also a perk of being a founder. Having possession of a founder bundle does not enable becoming a founder – the window on that closed long, long ago. Enjoy using the hardware, though!
Hello @dominico  10Mbps is the minimum required speed to play Stadia at the lower resolution. At the highest resolution (4K), you would need 35Mbps. Here's a help page that may provide more informa... See more...
Hello @dominico  10Mbps is the minimum required speed to play Stadia at the lower resolution. At the highest resolution (4K), you would need 35Mbps. Here's a help page that may provide more information: https://support.google.com/stadia/answer/9607891?hl=it  But, beyond minimum throughput, it's important to understand that network stability is just as important. If the minimum speed is only met on average, but sometimes dips below and sometimes rises above the requirement, you may not have a good experience.
I'm afraid I can't provide more details, since I don't use the streaming feature myself. But, I believe the incoming stream gets decoded for local display only – I don't think there's any way for OBS... See more...
I'm afraid I can't provide more details, since I don't use the streaming feature myself. But, I believe the incoming stream gets decoded for local display only – I don't think there's any way for OBS to capture it in its encoded form. It would only be able to capture the screen contents to re-encode for upload. Even if it could capture the encoded version of the stream, it would have to decode it to composite your webcam PiP into it and then re-encode the result.
Hello @Isbey  First, a significant caveat – I don't stream, and I am not familiar with OBS. But, I know a bit about how Stadia streaming works. The two sets of instructions on that page describe tw... See more...
Hello @Isbey  First, a significant caveat – I don't stream, and I am not familiar with OBS. But, I know a bit about how Stadia streaming works. The two sets of instructions on that page describe two different methods for streaming. The first option, streaming directly, doesn't need (or use) OBS, and doesn't support including a webcam picture-in-picture, etc. But, it does get a copy of the Stadia game video stream directly from the Stadia game server and uses that as the source of the YouTube game stream. So, in that case, you don't need to do a local capture, encode, and upload at all. The second set of instructions describe using something like OBS to capture your local screen, and composite your webcam view into it, etc. followed by encoding and uploading that stream to YouTube – just like you would for non-Stadia game play. I believe the instructions for connecting your Stadia game session to the YouTube stream are to enable support for things like Stadia-specific features (like Crowd Choice or Crowd Play). So, I would pick one of those two sets of approaches and stick with it.
Hello @LuisRafael96  I assume you're referring to game play with this question. Stadia has a unique feature of being able to start a game on one device and move that game-play session to other devi... See more...
Hello @LuisRafael96  I assume you're referring to game play with this question. Stadia has a unique feature of being able to start a game on one device and move that game-play session to other devices (e.g., televisions, computers, phones tablets, etc.). The games themselves aren't impacted by these transitions – they just pause and unpause while Stadia takes care of the change in stream encoding and destination. In order to make this work, the aspect ratio of all of those devices needs to match. So, the 16:9 aspect ratio of typical televisions is the one that Stadia uses on all devices. The result is some unused space on the left and right side of the screen when playing on a device that has a wider screen like most phones and ultra-wide PC monitors or unused space on the top and bottom of the screen when playing on a device like an iPad that is a bit more squarish. In short, for Stadia to support aspect ratios other than 16:9, the game developers would have to incorporate support for dynamically-changing the aspect ratio, whereas today, the game just needs to know the original resolution when it starts. So, this isn't impossible, but it may not be at the top of the list of priorities given it would impact every game. All of that said, if this is something that is important to you, please use the "Feedback" feature in the app to let Google know.
Hello @Zeapo  These are great suggestions – to make sure Google sees them, please use the "Feedback" feature in the Stadia app on a phone or tablet.
Hello @Bunion_L  As @Deleted User suggested, using the feedback feature in the Stadia app is a good way to let Google know what you want to see. However, since game availability is largely up to th... See more...
Hello @Bunion_L  As @Deleted User suggested, using the feedback feature in the Stadia app is a good way to let Google know what you want to see. However, since game availability is largely up to the developers and publishers rather than Google, you should also get in touch with them directly to let them know there are people wanting to buy their games on Stadia.
That is a very good question. But, it is a question for the Chrome browser team, since it's not a Stadia-specific issue.
I do wish I'd known you were trying to use a Linux client – that is a known and ongoing challenge. Without hardware decoding of VP9, software decoding can end up taking enough time to start looking l... See more...
I do wish I'd known you were trying to use a Linux client – that is a known and ongoing challenge. Without hardware decoding of VP9, software decoding can end up taking enough time to start looking like latency, which makes it seem like a networking problem rather than a software problem. I do wish there was better support for this on Linux, but I don't personally have a lot of suggestions on that angle (I use Linux for a whole lot of things, but Stadia isn't one of them – I have a Windows PC and a Mac mini I use for Stadia gaming). You may be able to find some useful tips for this with a Google search for something like "stadia hardware vp9 linux chrome". I just tried that and found some older articles, but I am hesitant to link to any of them (since I don't have any way to know which are still relevant). I wonder if Google's CloudReady distribution (from neverware, which Google bought some time ago) might work? That's a build of ChromeOS that can be installed on most PC hardware. I don't know whether it has the right drivers installed to enable hardware VP9 decoding or not, but it may be more likely than typical distributions, since Chromebooks tend to run Stadia well if the underlying hardware is capable of it. You can download a USB image and just try booting from that to try it out without installing it. I know that's not a solution to making it work properly on Linux, but at least it would let you avoid having to install Windows just to make it work.
Hello @Withhonorgraham  I have an M1 Mac mini running macOS Monterey. I just fired up 100 Days to check really quickly, and it worked fine for me. Now, I don't use a controller with this, so I didn... See more...
Hello @Withhonorgraham  I have an M1 Mac mini running macOS Monterey. I just fired up 100 Days to check really quickly, and it worked fine for me. Now, I don't use a controller with this, so I didn't try that, but at least the core features are working properly. Do you by any chance have "iCloud Private Relay" enabled? That shouldn't affect Chrome, but it might interfere with unencrypted traffic from non-Safari browsers on macOS if it's enabled.  I would make sure Chrome is up-to-date, and I'd try running it in an incognito window and with all browser extensions disabled.
Hello @firtade_adrian  That's a good question. So far, there haven't been any indications when or if this game (or any of the CoD games) will come to Stadia. I would love to see them on the platfor... See more...
Hello @firtade_adrian  That's a good question. So far, there haven't been any indications when or if this game (or any of the CoD games) will come to Stadia. I would love to see them on the platform myself, but the best thing we can do is lobby Activision Blizzard directly to port it.
Can you take a look at all of the Stadia Enhanced statistics? In particular, the decoding time? It sounds like you are seeing high packet loss, which usually indicates a networking issue. But, if tha... See more...
Can you take a look at all of the Stadia Enhanced statistics? In particular, the decoding time? It sounds like you are seeing high packet loss, which usually indicates a networking issue. But, if that were the problem, you should see it in bootcamp as well. Even so, eliminating the WiFi connection as an issue would be a good thing to try – you'd just need an inexpensive USB-C Ethernet adapter. Do you have any additional security software installed in macOS? Antivirus or firewall software, for example?
You may be able to disable hardware decoding through a Chrome browser flag. But, if you haven't done that, it should already be enabled. To check on this, go to the "System" section of Chrome's setti... See more...
You may be able to disable hardware decoding through a Chrome browser flag. But, if you haven't done that, it should already be enabled. To check on this, go to the "System" section of Chrome's settings: chrome://settings/system and make sure "Use hardware acceleration when available" is enabled. Then, go to Chrome's flags (chrome://flags/ ), search for "decode", and make sure "Hardware-accelerated video decode" is enabled as well. But, if both of these are already enabled, and Stadia still isn't using it, then there's another problem (like something got broken in a version of Chrome).
Hello @F8Tarnished  The NVIDIA Shield hardware can decode VP9 (the video codec Stadia uses), but only in standard dynamic range – not high dynamic range (profile 2). This is a limitation of the Shi... See more...
Hello @F8Tarnished  The NVIDIA Shield hardware can decode VP9 (the video codec Stadia uses), but only in standard dynamic range – not high dynamic range (profile 2). This is a limitation of the Shield Pro hardware.
Hello @Paulo5  I assume you're asking about the Stadia controller and the Chromecast Ultra used to play Stadia games on a TV. Here's a link to the Google Store for all of the different Stadia-relat... See more...
Hello @Paulo5  I assume you're asking about the Stadia controller and the Chromecast Ultra used to play Stadia games on a TV. Here's a link to the Google Store for all of the different Stadia-related products: https://store.google.com/product/stadia where you'll find the "Premier Edition" (controller plus Chromecast Ultra) or the play & watch bundle that comes with a controller and a Chromecast with Google TV (a newer – and nicer – device than the Chromecast Ultra). There may be other ways to play on your TV, depending on whether it is based on Android TV (or you have an Android TV device connected to it). Those may support connecting just about any Bluetooth controller instead of using the official Stadia controller. You can also just play on a phone or a computer. Here's a support article that has more details (hopefully this link will give you the French version): https://support.google.com/stadia/answer/9551446?ref_topic=9634925 
Hello @VR6Pete  The CCU will be making the decision about which band to connect to. Google/Nest WiFi "band steering" is really just an implementation of the 802.11k and 802.11v standards, which let... See more...
Hello @VR6Pete  The CCU will be making the decision about which band to connect to. Google/Nest WiFi "band steering" is really just an implementation of the 802.11k and 802.11v standards, which let it give clients some extra information they can use to make better decisions about which access point and which band to connect to. But, the decision is still theirs – Google/Nest WiFi can't force them to do anything. However – and this is an important "however" – fixed devices like the CCU almost never implement 802.11k and 802.11v. So, it's highly likely the CCU isn't getting those "band steering" hints in the first place. It will just do a signal quality scan on startup and pick the best option. It's possible it's connecting to the primary Google WiFi unit at 2.4GHz rather than the closer secondary access point. This is more likely if you have restarted the Google WiFi network without also restarting the CCU. I would first try just unplugging the CCU after the Google WiFi network is up and stable, then plug the CCU in and see if it does a better job of connecting at 5GHz to the nearby access point. If that doesn't work, then the most likely explanation is interference. If you have a wireless subwoofer, a wireless surround sound system, or even just a set of wireless gaming headphones nearby, they are very likely to be using the same part of the 5GHz band that Google WiFi does, and using it in a way that makes sharing that spectrum almost impossible. That could cause the CCU to see very poor signal quality in the 5GHz band and fall back to 2.4GHz instead. All of that said, the CCU has an Ethernet jack in the power supply. If there's a Google WiFi access point 1.5m away, just buy an Ethernet cable and connect the CCU directly into one of the Ethernet jacks on that Google WiFi access point. That way you won't be using WiFi at all (however, if that's a secondary access point, and you do have interference from nearby equipment, you'll still need to address that issue, since the Google WiFi secondary units talk to the primary using the 5GHz radio as well). I hope some of this helps – I'm a product expert in the Google/Nest WiFi community, too.