安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
I've reviewed it but can't necessarily make out what it says -- I do see that there are messages showing that it receives a specific video sequence that are different than expected, thus a lost data disconnect.
For example -- "CLIENT: Got video sequence 4178, expected 4153, sending lost data notification"
If this isn't the case, possibly try running a ping from the host to link... see if there's packet loss?
Initially, I had my computer (WIndows 7) and the Steam Link wirelessly connected to the home router (Actiontec C1000A). This setup was easy to do, and the results were pretty decent from a streaming perspective, only experienceing occasional stuttering and bouts of lower quality.
This issue started happening when I intalled a powerline adapter with a switch and ran cable from both devices into it, with the other end of the powerline adapter connected to the router.
I can get the computer to show up in the Steam Link (as well as two Windows machines) long enought to start streaming from it and get to Rocket League's title screen before the stream dies and the Link loses connection entierly. The whole process can be restarted after power cycling the Steam Link.
All this said, I'd be interested to hear about how everyone has their Links setup since, as is my case, the problem came up after I changed mine.
EDIT: Just a passive observation: my Link is recieving an IP address (and subnet mask) that's wildly outside of the normal rang for my network. This is strange to me since my computer (which is plugged into the same PL adapter as the link) gets an IP in the normal ranges for my network.
The only thing I changed was the network settings: I tried to set it to prioritize and messed with the encoding (turned it off).
However I changed everything back to default and still cant connect. But the fact that it worked before to me implies there is something in those settings that messed it up.
Presently it's connected wirelessly, which had never been an issue in the past, but after rebooting my router, my pc, and my Steam Link (and checking for updates for all 3), I'm afraid I'm no closer to a resolution than when I began. The only thing that's happened recently is my Steam controller performed a firmware update, but I can't see how that could be connected to the issue.
Has anyone had any luck with this? I'd be most grateful for any assistance that either Steam (or the community) could provide. Cheers! :)
::Update::
I finally fixed the problem. Recently, I had purchased a wireless Blackweb keyboard to use with my Steam Link. That seems to have been the culprit, because as soon as I disconnected the USB dongle for it, my streaming is back to working perfectly. I hope this is helpful to everyone! :)
Interesting solution, but I have the issue even when I'm wired in. I wonder if it's a PC setting on the ethernet port?
1/ rebooted router No Fix
2/ rebooted windows - No Fix
3/ rebooted Steam Link - No Fix
4/ reset Steam Link to factory settings - No Fix
5/ Uninstalled a lot of new Microsoft Programs, Lavasoft and what I thought might be the culprit Nvidia Experience Program - SOLVED
I hope it helps.
Now if I can just get it to work lag free - arghhhhhh.
Unbelievably frustrating. Hours spent opening ports on port forwarding on router, etc. resetting to factory settings on steam link, all that jazz. At least 20 restarts of everything, cable modem,router, steam link and Pc.
Im getting really frustrated at this point. Did all the troubleshooting and reconnecting. Did the factory reset and went to the beta build for hope. Im feeling like an idiot wasting $50 on this because my RIG is pretty high end and this should work.