35 minutes ago, Bjoern said:

Same for the WiVRn server built in Envision.

Someone on their discord had the exact same error messages with a different app. Same behavior (ctrl+c, etc).

They claim that the only solution was to compile Envision on their own instead of using the git binary. As far as I can see in my limited internet sleuthing (and w/out a hmd to test with), monado shouldn't be showing up anywhere in your process. Neither in the AUR build nor in the servers that you initialize. Someone else over there also then chimed in with:

Quote

...WiVRn doesn't work with envision appimage, so you need to build it or get it from aur...

 

All this is why I build the pieces manually. I'd be trying to compile wivrn on my own after seeing all this. Build deps should all be there if AUR was already successful once.

The non-steamVR route is certainly still a ball of worms right now. No harm in letting it ferment a bit longer.

Correction. Wivrn does use some of monado as a build dependency lib. Not as the server. They released a new version today too. Might be worth checking out if that's not what Envision built.

I've built Envision from AUR, same for wivrn-server, so both should have picked up the correct dependencies (unless there are bigs in the PKGBUILDs).

All of yesterday's testing was with WiVRn 0.18.

Note that Monado on its own works fine in XP in as in that I can switch to VR mode.

I can try to go for a non-AUR build from Git for Envision and WiVRn or unpack Envision's Appimage for WiVRn (as suggested on the LVRA wiki) and then build WiVRn.

P.s: It might be better to continue this on the Org because it derailed the thread a fair bit.

Edited August 14, 20241 yr by Bjoern

3 hours ago, Bjoern said:

All of yesterday's testing was with WiVRn 0.18.

Building this from their git release manually or with AUR was/is my final suggestion. I'm out of ideas. Unless maybe there's somehow a mismatch between what gets installed on the hmd itself (that Android driver situation) and the wivrn server that you're starting up?

Just to throw my 2c in.  I have to say the X-Plane flight model is the best in a commercial flight sim, by far.  And the flexibility it allows with changing variables is outstanding.

2 hours ago, blingthinger said:

Unless maybe there's somehow a mismatch between what gets installed on the hmd itself (that Android driver situation) and the wivrn server that you're starting up?

A version mismatch between server and Android client for both ALVR and WiVRn is immediately picked up by the client, resulting in a denied connection.

Edited August 14, 20241 yr by Bjoern

HOLY MACKEREL, I GOT IT TO WORK!

The key was to use Envision's opencomposite library for X-Plane, Envision's "openxr_wivrn.json" for the "XR_RUNTIME_JSON" environment variable and, more importantly, starting and connecting WiVRn and the headset before trying to enter X-Plane's VR "Settings" menu. Because a missing connection triggers the program hang.

So far, the connection seems more stable than SteamVR, but oddly enough, the buttons on the controllers do not work. Reghardless, this is a huge step forward in VR usability for me!
 

 

1 hour ago, Bjoern said:

The key was to use Envision's opencomposite library

Were you previously just using the compiled git artifact? All this is the big reason why I compile it all locally. Including opencomposite. Does Zink work?

 

7 hours ago, GoranM said:

Just to throw my 2c in.  I have to say the X-Plane flight model is the best in a commercial flight sim, by far.  And the flexibility it allows with changing variables is outstanding.

Seriously. Planemaker has so many options and capabilities. And the tons of datarefs sitting behind that GUI are just as deep as what you can see up front. It's mind-boggling what Austin has generated over the decades.

20 hours ago, blingthinger said:

Were you previously just using the compiled git artifact? All this is the big reason why I compile it all locally. Including opencomposite. Does Zink work?

Yep, it was the one from the opencomposite repo. But oddly enough, after some testing, even X-Plane's default libopenvr_api.so seems to work, so I think all that's actually required for OpenXR is setting the correct "XR_RUNTIME_JSON" environment variable with Monado handling the rest.

No idea regarding Zink because I haven't used it in ages and don't intend to. Despite being on AMD, I don't get any plugin flickering and I have no idea why.

18 hours ago, Bjoern said:

even X-Plane's default libopenvr_api.so seems to work

Very interesting. I wouldn't have guessed wivrn would talk through steamvr. But again, I haven't needed to dig into it at all. It sounds like they (wivrn) moved their git repo but I suppose handling things like that are precisely what Envision is for.

Full circle, then...one thing I really really really like about XP is native linux support. The above puzzle-solving/tinkering tickles my noggin. Most of the time.