Google said that an Intel Core i3 paired with 4GB of RAM will not work, and even certain supported configurations will encounter some issues. Start Steam Link and Steam Controller should work.Google has listed the following Chromebook models as compatible with Steam: Acer Chromebook 514 (CB514-1W), Acer Chromebook 515 (CB515-1W), Acer Chromebook Spin 713 (CP713-3W), Asus Chromebook Flip CX5 (CX5500), Asus Chromebook CX9 (CX9400), HP Pro c640 G2 Chromebook, and the Lenovo 5i-14 Chromebook.
In the Bluetooth Connection screen on Chromebook IMPORTANT DELETE PREVIOUS STEAM CONTROLLER REGISTER AND SELECT NEWLY PAIRED CONTROLLER!Ħ. Pair Steam Controller with Chromebook by holding Steam Button and B while controller is off.ĥ. Unplug Steam Controller and Return to Chromebook.Ĥ. Hear the audio cue on Steam Controller and wait 5 seconds.ģ. Plug Steam Controller into PC while Steam Streaming Client is open.Ģ. I have had some success performing the following actions to reconnect the controller:ġ. The controller is unable to continue to be connected to the Chromebook at this point and continually turns off when trying to use with the Steam Link After the controller turns off when you turn it on subsequently it disconnects after about 10 seconds.Ĥ. After you start the Steam Link App and see the status of the Streaming PC, Controller, and Connection after you input the code and get to PC the controller turns off.ģ. Turning on the Steam Controller and pairing to the chromebook from the last session connects for about a minute.Ģ. So in troubleshooting using the Steam Controller on my ASUS Chromebook Flip C302C the issues I have noticed are:ġ. The only semi-workaround that I have been able to get working is to connect the controller wireless to my PC and then start streaming. I'm guessing this is because there isn't a ChromeOS driver for the controller? I am also unable to get the controller to connect using the wireless dongle or through USB. Any idea why this causes the controller to turn off?
:(Īh gotcha, sounds like a big issue on Google's end.
I suspect there's not an easy fix for it. I suspect this might be part of why it reports Chromebooks aren't officially/formally supported. It seems to happen consistently when switching activities (as happens with going from the shell to the streaming client). but there's a bug in the Android Runtime for Chrome where it says it's lost the Context for the connection ID - as a result, it looks like the underlying Bluetooth never reports back that the connection succeeded. Opprinnelig skrevet av Packetdancer:When I try on my Pixelbook, if I use adb to view the logs, I see that the connection to the Steam Controller is made.
0 kommentar(er)
