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
This can have many reasons.
Can you for now first give us all of your PC specs and if you play wired or wireless? If you play wireless which system (VD, Steam Wireless, Oculus wireles, .. )are you using?
Kind regards,
Koen
What windows version are you using?
I would firstly make sure all your drivers are up to date.
Secondly try to do a repair steam files.
If that does not work can you reach out to me on our discord, my name there is Koen.
I will instruct you to download dev build which generates detailed logs, we can use that to try and pinpoint your problem.
Kind regards,
Koen
All other drivers are also uptodate.
will try to connect you at discord
But i dont knew discord, so you must say whatto do
If you were using a reverb before your open xr runtime was probably set to windows, if you would have reset it to oculus thne that should have done the trick.
Installing stram vr put the runtime to steam and then together eith using steamOpenVR your game can noe actually launch.
Some months ago there was no such problem, but now if I start Hubris in OpenXR runtime (Steam > library > Hubris > Play > openXR) it only shows black screen with sound, so I can only run the game successfully in SteamVR runtime.
Windows 10, RTX 4090.
This is because of Virtual Desktop now having the VDXR runtime enabled by default for our game.
You should be able to just go for VDXR in combination with the right Pico openXR runtime?
If that does not work then you will indeed have to use SteamVR and the the regular VD runtime.
I can't understand you. Can you clarify, what is "right Pico openxr runtime" and what is "regular VD runtime"?
If in VD I choose VDXR as a runtime, Hubris won't work (no matter what runtime choose when launching the game) - it shows only black screen with sound, as I mentioned before.
Ah so I double checked current Pico implementation and it looks like Pico does not use openXR but just uses steamVR.
https://www.reddit.com/r/PicoXR/comments/11g4827/openxr_runtime/
So I assume thats why you have to run the game over regular Virtual Desktop and also use the non openXR option and then the setup works.
Thanks for bringing this to our attention this way we can better inform our players!
That is strange, because few months ago I could successfully run Hubris in OpenXR runtime (it was clearly visible for me, because of lack of SteamVR overlays (fpsvr, ovras, etc.) and increased game performance, so I definitely launched Hubris in OpenXR mode in the past).
But a few months ago there was no VDXR so it was by default running over steamVR or did you use cable back then?
And release page (https://github.com/guygodin/VirtualDesktop/releases/tag/v1.29.6) says VDXR feature was released in October 2023.
And I never had cable, don't even know how to connect it)
weird so you are saying since the latest update the Pico over VDXR no longer works with our openXR version. We did not change anything to any of that build though.
Are there other open XR pico games you can run over VDXR? Is this issue only with our title?
Can't say if it is since latest or since some pre-latest.
Also it can be caused by SteamVR update or Steam update or VD update.
> Are there other open XR pico games you can run over VDXR?
Can't answer now, because I haven't played any openxr game besides Hubris.
By the way I assume we can leave my problem be, as it is not critical. Besides we already went offtopic - this thread is about Quest 3.
upd 09.06.24. My problem is fixed with update 1.32.4 of VD.