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 (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
-Edit
I started a new conversation page!!! :)
@rmoney - If you are willing to explain to us, please let us know:
1. What router make/model do you use?
2. If you are willing to run a test, if you switch back to the public (not Beta) on the Quest side (so before 2.0.3.666) does SteamVR activate on your host PC and identify the headset or does it not? We are trying to plan what we would do for users moving forward, and if there's any way for us to auto detect. Additionally, if you DON'T toggle the Disable QoS option on Beta (both sides) what happens?
Hi charlesl,
I'm using my ISP's (Bell) stock modem, the Home Hub 4000. It supports Wifi 6 (but not Wifi 6E unfortunately).
I've done a few case tests:
✓ Interestingly, using non-beta SteamVR v2.2.3 on the PC and the beta (v2.0.3.666) on the headset works perfectly fine.
✓ Beta on both + toggling Disable QoS option = working fine.
✖ Beta on both + not toggling Disable Qos option = failure (200)
✖ Downgrading to non-beta client (v2.0.2.638) on headset and staying on beta 2.3.1 on SteamVR = failure (200).
In this case, SteamVR DOES activate on my host PC, it DOES identify the headset, the connection IS successful and steam menu shows up in the headset, but then literally after a few seconds the connection drops and the error 200 message shows up. As soon as the error 200 message shows up in the headset, SteamVR gets a message saying "Standing by Put on your headset to wake VR." However my VR headset is still on my face with the error 200 screen when this message appears (I check the status of SteamVR on the PC screen by peeking through the gap in the nose notch on the headset).
✖ Downgrading to non-beta on both devices = Same behavior as above ^
I hope this helps the dev team narrow down the issue.
Thanks for creating Steam Link/Steam VR for the community. I hope it stays free to encourage growth in the VR arena.
HP laptop
Cpu: Ryzen 5
GPU: RTX3050ti
Laptop is connected to router with wire, headset is on 5g wireless, and router is approx 20cm from headset
Then I disabled oculus audio device in windows - the sound came back.
then on the second launch I have error 200
my gpu is rtx2070s. last driver 546.33
I switched oculus audio device back, but still cant fix the error.
I even tried steam vr betta - same issue
Router: TP-LINK Archer C6
Connection: PC wired to the router, Quest 3 in the same network
CPU: AMD 5600X
GPU: RTX 3070 TI
Router: Virgin Media Hub 3.0 2.4GHz and 5.0Ghz with smart wifi option.
connection: PC wired to the router
headset: Meta Quest 3
CPU: AMD Ryzen 7 3700X
GPU: AMD Radeon RX 6750 XT OC
I also lowered my bitrate and tried beta on both. nothing is working. I just want to play Alyx ;_;
Here is my initial bug report with info on how to disable hw GPU acceleration:
https://steamcommunity.com/app/250820/discussions/3/4134934526939630581/
My setup for those who facing the same issue:
Headset: Meta Quest 3
CPU: Ryzen 5600X
GPU: RTX 3070 Ti, 8GB
RAM: 32GB
Motherboard: MSI B550 Tomahawk
Router: Archer C6 (5Ghz connection) - PC is wired to the router.
Steam Link used to work perfectly for me earlier, I have played for hours on several different games. This issue appeared for me today.
Headset: Meta Quest 3
Laptop: MSI Alpha 15 A3DC
CPU: Ryzen 7 3750H
iGPU: RX Vega 10
dGPU: RX5300M
RAM: 16 GB
Network: Laptop via Ethernet to 5Ghz router (also tried wirelessly, i get the Ethernet warning but code 200 issue persists)
Things I've tried:
- changing the bitrate
- forcing Windows Graphics preferences for vrdashboard.exe between the iGPU and dGPU.
- tried to see if it connects using mobile hotspot + USB tethering
- changing to 2.4 GHz bands
I would like to re-emphasize that this used to work seamlessly for me, until today.
you are a godsend