Quoting: GuestSpeculating on the fact that the open and the closed ones are causing the aame issues and given that the userspace part of the driver "should" not crash the kernel by its own, maybe there is common code between the open and the closed drivers.

That's not speculation. Nvidia said as much from the beginning.

Though the kernel modules in the two flavors are different, they are based on the same underlying source code. [External Link]

The open drivers just have any code removed that they could not relicense to MIT/GPL, such functions were rewritten or ported to the GSP.

View this comment - View article - View full comments

Quoting: sonic2kk

Quoting: toru9999just upgraded, the flatpak and kernel version remain unchanged...so much for "security".

Is the kernel entirely unchanged? Valve will keep the same kernel version but they will backport lots of patches, the Preview channel changes it reasonably regularly. EDIT: I should've clarified, the version string may be mostly the same, but there will be an updated hash.

I wonder if maybe some other Arch packages were changed?

On the other hand, maybe they're referring to Steam Client security changes. Since many SteamOS updates are actually just Steam Client updates, except when they specifically note changes to drivers, the Arch snapshot, etc.

Valve lists OS and Client release notes entirely separately. Whatever the updates were here, they were definitely in the OS.

View this comment - View article - View full comments

Just tried it out in KDE Wayland (wish mutter had DRM leasing support...), it's *finally* in a state where I could recommend it for beta users. Performance was great, async reprojection worked fine with Nvidia 535 drivers and I played more than an hour of Vertigo 2 without any issues.

It's still a little rough around the edges for general use though. No firmware updates in Linux, no automatic Lighthouse power management or audio device configuration. Had a crash when playing around too much in the Steam menus. Once in game though everything was smooth and played very well, so the basics are finally there!

View this comment - View article - View full comments

I'm a huge fan of VR but unfortunately it's also one of my ties to Windows. I have an Index also but between the Nvidia drivers not supporting core functionality needed for async reprojection plus a number of smaller issues that all add up it's just a huge struggle for me to use in Linux, despite basically all traditional pancake games running like butter for me on it. Not sure if external links are a problem but since the list is long and changes sometimes I put together a list of Linux VR complaints a while back that I'm mostly still waiting on fixes for:

Linux VR Missing/Broken Feature List [External Link]

View this comment - View article - View full comments

To anyone having issues with the client's game controller not working you may want to check to make sure you aren't using systemd 243. There was a udev update that broke Steam's xinput emulation devices which could very likely cause this.

View this comment - View article - View full comments

Quoting: aejsmithThe AO change is described as lower quality in the article but in practice running it at half res makes virtually no noticeable difference to the quality.

I agree that it's a smart optimization, but would it be possible to include the original options when available for testing, or for people who can power through it regardless?

View this comment - View article - View full comments

Quoting: 14Are you the Vash6318 from the Battlefield 1942 days that's on my Steam friends list? :huh: Fancy seeing you here!

Yep, that would be me.

Quoting: HoutwormI run Kernel 5.3.0 and Systemd 243.0, My controllers are all working just fine with Steam and anywhere else actually. I use Xbox One S controllers and Dualshock 4 controllers I use them all using Bluetooth.

You can connect a DS4 via Bluetooth on kernel 5.3? That's interesting, are you sure you've tested that specifically since updating? As for the systemd issue it only impacts XInput emulation for games that don't support generic (non-X360) gamepads.

View this comment - View article - View full comments

Quoting: 14

Quoting: FaalhaasEven after that, some games did not detect my buttons, so I even reinstalled the OS. Now it's working with modprobe.

Reinstalled! :O Yikes!

I guess I haven't used my controller for over a month. I've been on systemd 243 for quite a while now.

Which OS distributed linux 5.3 already? Arch is pushing out 5.2.14 at the moment.

No idea if any OSes have distributed it to their core repos but I'm on Arch and I tested it a few hours after it released by compiling my own build.

View this comment - View article - View full comments

Quoting: beniwtv

Quoting: Sil_el_moti don't think so. there are a lot of good games, that are well made for vr and are a lot of fun. that you can't do games the same way like 2d should be known.
i put more than 200h in Beatsaber, would never tell anyone this isn't a good game.
i played onward a very lot, because the mechanics are good and it is a lot of fun.

i don't know what you hope to play, but games like CoD xx wouldn't work in vr. and it would be to much for nowadays gpus.

I think you misunderstood me there :)

My point wasn't that there are no good VR games, far from it. Just that there aren't very many of them (still, there are more than I have time to play currently).

Beat Saber is an AMAZING game to me, it hooked me instantly. And it's beautiful for VR.

Right now my list of favourites are (with some upcoming ones):
- Arizona Sunshine
- Beat Saber
- Boneworks (will hopefully be good when it comes out, so I'll include it here)
- Budget Cuts (this SEEMS good, doesn't currently run for me tho)
- Elite: Dangerous
- Everspace
- No Man's Sky (will also hopefully be good when VR update comes out)
- Serious Sam VR games
- Star Citizen (if they ever finish adding Vulkan and VR)
- Star Trek: Bridge Crew
- Talos Principle
- The Gallery series
- The Solus Project

I'd love to know what everyone's favourite VR games are, maybe we can discover some hidden gems people are playing :)

You're missing Hotdogs, Horseshoes and Hand Grenades which is one of my favorites, as well as To The Top. I'd also throw Duck Season on the list, it's short but a really great and replayable experience.

View this comment - View article - View full comments

Quoting: beniwtv#2 shouldn't really impact you, PulseAudio should remember the output for each game you set it to, at least does for me.

#3 would be nice to have but I solved that with home automation :P

#4 To be honest never noticed anything like that, I don't even know what's missing :S:

#5 Never used them, so have no need, but I guess it would be nice for Valve to fix that

#2 absolutely impacts me, are you sure it doesn't for you? What VR headset have you tested this with? Steam adds and removes the device when you open and close SteamVR which wipes pulse's defaults away from it on my system. Maybe it's because I switch my entire default output to the HMD instead of per-faucet, but having to switch every single game on first run is still really annoying.
#3 is an expensive and inelegant workaround compared to Steam just handling power management itself, and really not suitable for a consumer product IMO unless Valve ships the remote outlets with the kit
#4 Specifically a lot of the remapping options and even the 'Exit VR' button from within VR were disabled. This may be fixed with the new beta, or at least probably soon will be as you can enable them with a variable but it was disabled to prevent crashes.

In other news, Nvidia support gave me a way to force off gsync (since it was removed from the nvidia-settings gui) and that resolved my tearing issue:
nvidia-settings -a CurrentMetaMode="DPY-3: 2560x1440_144 @2560x1440 +0+0 {ViewPortIn=2560x1440, ViewPortOut=2560x1440+0+0, AllowGSYNC=off}"

Substitute your MetaModes from nvidia-settings -q CurrentMetaMode and just add in the AllowGSYNC block if you're impacted, it's confirmed to fix the tearing/stutter issues for me and makes games actually playable.

View this comment - View article - View full comments