Now that SteamVR 2.0 is officially out, Valve has continued to push out Beta releases with other improvements and the Linux situation with SteamVR seems better now too.
In the SteamVR Beta 2.0.10 release Valve noted these improvements:
SteamVR
- A fix for IVRVirtualDisplay interface.
- Fixed binding UI crashing when saving a binding.
Linux
- Fix 'Shared IPC Compositor Init Failed' error reported by the Steam client on startup.
- Fix Room Setup not launching on some systems.
And thankfully, testing my Valve Index on Kubuntu 23.10 today the new UI does finally show up and the annoying 303 error has also gone as well. So we're a big step closer. Some issues still remain like the colours being flipped (it's very brown) and the Steam Store section was just a blank page but it's getting there now.
Pictured - SteamVR 2.0.10 on Linux
Hopefully it won't be long until the other issues are fixed now it's mostly working. Great stuff to see!
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
Mohandevir Nov 1, 2023
I'm wondering if it's not the biggest missing link for the SteamOS 3.5 release and the Sephiroth official reveal. **Fingers crossed**
Last edited by Mohandevir on 1 November 2023 at 1:17 pm UTC
Last edited by Mohandevir on 1 November 2023 at 1:17 pm UTC
0 Likes
Quoting: MohandevirI'm wondering if it's not the biggest missing link for the SteamOS 3.5 release and the Sephiroth official reveal. **Fingers crossed**I think if it was for Deckard then it would have a much higher priority than it has seen. I imagine how it's being rendered is different, especially since from the previous leaks we saw it would have a standalone mode.
Last edited by Liam Dawe on 1 November 2023 at 1:25 pm UTC
2 Likes, Who?
Mohandevir Nov 1, 2023
Quoting: Liam DaweQuoting: MohandevirI'm wondering if it's not the biggest missing link for the SteamOS 3.5 release and the Sephiroth official reveal. **Fingers crossed**I think if it was for Deckard then it would have a much higher priority than it has seen. I imagine how it's being rendered is different, especially since from the previous leaks we saw it would have a standalone mode.
I'm not going to argue about that; you are in a much better position to know... It's just that all these leaks about Sephiroth and SteamOS 3.5 that's taking ages to reach stable... What is holding them back? What roadblock Valve met? It might just be coincidence, then.
0 Likes
Quoting: Liam DaweQuoting: MohandevirI'm wondering if it's not the biggest missing link for the SteamOS 3.5 release and the Sephiroth official reveal. **Fingers crossed**I think if it was for Deckard then it would have a much higher priority than it has seen. I imagine how it's being rendered is different, especially since from the previous leaks we saw it would have a standalone mode.
I dunno, linuz VR had been pretty much abandoned for years and suddenly there are lots of improvements being rolled out continuously very fast. I, for one, am very excited for what this could mean ^^
1 Likes, Who?
Quoting: MohandevirI have no info other than what’s already public. SteamOS 3.5 is taking time just because of how much it’s adding in and they clearly want to keep pushing HDR which has taken a lot of work :)Quoting: Liam DaweQuoting: MohandevirI'm wondering if it's not the biggest missing link for the SteamOS 3.5 release and the Sephiroth official reveal. **Fingers crossed**I think if it was for Deckard then it would have a much higher priority than it has seen. I imagine how it's being rendered is different, especially since from the previous leaks we saw it would have a standalone mode.
I'm not going to argue about that; you are in a much better position to know... It's just that all these leaks about Sephiroth and SteamOS 3.5 that's taking ages to reach stable... What is holding them back? What roadblock Valve met? It might just be coincidence, then.
2 Likes, Who?
Quoting: MohandevirSteamOS 3.5 that's taking ages to reach stable... What is holding them back?
SteamOS 3.5 is the first time that the underlying OS got updated. I suspect they were expecting to just take another Arch snapshot, apply their patches, and then move onto other things - after all, Steam works on every distro already, and a lot of Valve's stuff has been upstreamed. Easy. But... that's not what happened. People testing 3.5 said that it was very broken, and it remained very broken for quite some time. And while Valve are busy putting out fires for that snapshot the Arch hosepipe has kept on going, meaning that Valve also need to come up with a sane way to keep rebasing on Arch snapshots much more easily than this time, to keep doing it for the next 10 years or so without just being distro maintainers that never get anything else done.
5 Likes, Who?
Mohandevir Nov 1, 2023
Quoting: CatKillerQuoting: MohandevirSteamOS 3.5 that's taking ages to reach stable... What is holding them back?
SteamOS 3.5 is the first time that the underlying OS got updated. I suspect they were expecting to just take another Arch snapshot, apply their patches, and then move onto other things - after all, Steam works on every distro already, and a lot of Valve's stuff has been upstreamed. Easy. But... that's not what happened. People testing 3.5 said that it was very broken, and it remained very broken for quite some time. And while Valve are busy putting out fires for that snapshot the Arch hosepipe has kept on going, meaning that Valve also need to come up with a sane way to keep rebasing on Arch snapshots much more easily than this time, to keep doing it for the next 10 years or so without just being distro maintainers that never get anything else done.
Thanks for your input. I knew 3.5 was buggier at launch, but I didn't know it was that bad. I tought the major roadblocks had been sorted out a while ago.
Edit: This said, Arch being buggy and, like Liam said, HDR development, it might explain a lot of the actual delay.
Last edited by Mohandevir on 1 November 2023 at 2:57 pm UTC
0 Likes
The color issue again? 🤣
Isn’t this the third or fourth time this bug occurred?
Isn’t this the third or fourth time this bug occurred?
0 Likes
For me 2.0.10 gives error 497: "Failed to connect to window manager"
"Stable" 2.0.8 still works though.
"Stable" 2.0.8 still works though.
0 Likes
Quoting: CorbenFor me 2.0.10 gives error 497: "Failed to connect to window manager"
"Stable" 2.0.8 still works though.
I solved that issue by installing the OVR advanced settings.
I'm on Mint 21.2
0 Likes
Patreon
PayPal
See more from me