Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
AFAIK I am using the official release channel (I don't even see any other versions when I look at game > Properties > Betas)
Kilotesla - are you also using Virtual Desktop by chance?
We'll get it sorted, thanks for your patience and reporting!
- Connect to your PC via the Oculus PC App and Questlink / Airlink
- Start Steam VR
- Launch BRINK Traveler from within Steam VR.
Does that launch the app in the correct VR mode? Thanks!
Note: I just use my Rift S with the default cable and the Oculus PC App. Since it's not a Quest, I don't need Questlink/Airlink.
Screenshot: https://imgur.com/a/k57fn2S
want to inform you, that I have the same Problem now!
Cant launch Brink Travelers!
The only thing that's changed is my new Quest 3 (and all the new Oculus/Meta settings in my PC). Q3 is sometimes connected via Steam Link but it doesent matter. If I use my Vive Pro directly, Brink App won't start anymore!
Hope you can find the issue.
Thanks für your active support.
Michael
Thanks a lot!
Michael
If I use new Steam Link app on my Quest to wirelessly connect to my PC, and have SteamVR set as my OpenXR runtime in the SteamVR settings, then the app correctly runs in VR mode when I launch it from SteamVR home.
Could you confirm if that works for you? Seems like some Oculus and SteamVR OpenXR runtimes are fighting each other for control depending on which headset / connection technology you're using. We'll try to get a beta build prepared which will hopefully solve this issue once and for all! Thanks for your help!