search

korejan / ALVR

Stream VR games from your PC to your headset via Wi-Fi
https://alvr-org.github.io/
MIT License
187 stars 26 forks source link

ALXR Client on Pico 4 does not display any Interface #77

Closed ZhenyaPav closed 1 year ago

ZhenyaPav commented 1 year ago

I am currently having the same issue as described in alvr-org/ALVR#1337, not being able to launch the client properly. It doesn't display anything other than the two default cubes and the Alvr server also doesn't detect it. 209954129-cbf2b3c5-8b84-448d-8a4d-df77b16022dd

korejan commented 1 year ago

@ZhenyaPav Hi, this is how it currently looks when there is no stream, a custom "lobby" screen and UI is planned. Which version of the alvr server are you using? currently only v18.2.3 is supported, v19/20 support will come in the near the future. If you are using v18.2.3 on windows and the client is not discovered make sure windows network discovery is enable, you can also manually add client IP address.

ZhenyaPav commented 1 year ago

I've used the wrong server version, it works with 18.2.3. However there is significant latency, and unlike VD and AirLink, it seems to affect rotation as well, so unfortunately it's not very usable rn.

korejan commented 1 year ago

I've used the wrong server version, it works with 18.2.3. However there is significant latency, and unlike VD and AirLink, it seems to affect rotation as well, so unfortunately it's not very usable rn.

@ZhenyaPav which version of ALXR are you using? if you're not already using it please use latest nightly builds, the last stable release is very out of date. Also consider tweaking the controller position & rotation offsets in the ALVR dashboard with advance options on, the default values were set for the original v18 client on a quest with different api.

korejan commented 1 year ago

I've used the wrong server version, it works with 18.2.3. However there is significant latency, and unlike VD and AirLink, it seems to affect rotation as well, so unfortunately it's not very usable rn.

@ZhenyaPav which version of ALXR are you using? if you're not already using it please use latest nightly builds, the last stable release is very out of date. Also consider tweaking the controller position & rotation offsets in the ALVR dashboard with advance options on, the default values were set for the original v18 client on a quest with different api.

@ZhenyaPav I forgot to mention as well as the above, use TCP connection. UDP connections are not stable and cause visual artifacts in v18.

ZhenyaPav commented 1 year ago

I've used the wrong server version, it works with 18.2.3. However there is significant latency, and unlike VD and AirLink, it seems to affect rotation as well, so unfortunately it's not very usable rn.

@ZhenyaPav which version of ALXR are you using? if you're not already using it please use latest nightly builds, the last stable release is very out of date. Also consider tweaking the controller position & rotation offsets in the ALVR dashboard with advance options on, the default values were set for the original v18 client on a quest with different api.

I've used the version v0.10.0+nightly.2023.02.18. The issue with rotational latency is still here, however the client also crashes after about 20 seconds.

korejan commented 1 year ago

I've used the wrong server version, it works with 18.2.3. However there is significant latency, and unlike VD and AirLink, it seems to affect rotation as well, so unfortunately it's not very usable rn.

@ZhenyaPav which version of ALXR are you using? if you're not already using it please use latest nightly builds, the last stable release is very out of date. Also consider tweaking the controller position & rotation offsets in the ALVR dashboard with advance options on, the default values were set for the original v18 client on a quest with different api.

I've used the version v0.10.0+nightly.2023.02.18. The issue with rotational latency is still here, however the client also crashes after about 20 seconds.

@ZhenyaPav which PUI version do you have installed? when you say rotational latency are you referring to headset or controllers?

Something else i forgot to mention is that in the recently released PUI 5.4.x, a long standing bug in Pico's OpenXR runtime has been fixed but in previous versions I have a workaround that I need to disable. This new version also introduced a new issue that effects the colour output. I will be working on these today. If you don't mind could you post a copy of your sessions.json file so I can see & testing the settings you used.

ZhenyaPav commented 1 year ago

@korejan I am referring to headset rotation. The PUI version is 5.3.2 I've attached the session.json session.json.txt