Quoting: liamdawe

Quoting: Vash63I'm really glad to see such a large amount of fixes in a single release, but I still can't really recommend people buy VR if they don't want to use it in Windows. Here's a list I made a week or so ago of ongoing issues I've had for years with the Vive and now persisting with the Index:

1. Asynchronous reprojection doesn't work for any Nvidia users (major comfort issue unless you _never_ drop frames)
2. Audio input/output switching doesn't work so you have to screw with pulse every time you boot or quit SteamVR (Windows auto-sets this and back)
3. Bluetooth power management doesn't work so you have to manually unplug and plug in the lighthouses every time (there's no switch because Windows boots them on demand)
4. Parts of it are completely disabled right now because it was crashing left and right a month ago (basically most of the menus are disabled unless you boot with an env variable, you can't even quit VR from within VR)
5. The front facing cameras don't work so no mixed reality
6. For my system at least, the recomposition pipeline is totally broken so every frame drop causes tearing. This has been going on since at least Nvidia 396 and still on the very latest 418.52.16 dev drivers and 430 drivers.

Ouch if it's that rough, it's not really surprising Valve haven't replied about getting us an Index for review.

It's that rough for Nvidia users at least (though I think #6 is some weird conflict with nvidia's modesetting driver with a gsync display plugged in).

On the plus side, #1 doesn't impact AMD users and #4 is probably going to be fixed soon (was intentionally disabled due to crashing but had been implemented).

So if they re-enable the stuff in #4 and you're testing on Mesa drivers you'll just have to deal with #2, 3 and 5

Edit: Oh, also Motion Smoothing doesn't work on Linux at all right now and the error message says you're on "an older version of Windows"

View this comment - View article - View full comments

I'm really glad to see such a large amount of fixes in a single release, but I still can't really recommend people buy VR if they don't want to use it in Windows. Here's a list I made a week or so ago of ongoing issues I've had for years with the Vive and now persisting with the Index:

1. Asynchronous reprojection doesn't work for any Nvidia users (major comfort issue unless you _never_ drop frames)
2. Audio input/output switching doesn't work so you have to screw with pulse every time you boot or quit SteamVR (Windows auto-sets this and back)
3. Bluetooth power management doesn't work so you have to manually unplug and plug in the lighthouses every time (there's no switch because Windows boots them on demand)
4. Parts of it are completely disabled right now because it was crashing left and right a month ago (basically most of the menus are disabled unless you boot with an env variable, you can't even quit VR from within VR)
5. The front facing cameras don't work so no mixed reality
6. For my system at least, the recomposition pipeline is totally broken so every frame drop causes tearing. This has been going on since at least Nvidia 396 and still on the very latest 418.52.16 dev drivers and 430 drivers.

View this comment - View article - View full comments

Really cool project, wish they had a prebuilt option though as that dependency list has a _ton_ of stuff that is too old to be shipped by Arch. Most of them are on AUR but still a hassle to build.

View this comment - View article - View full comments

This is super shitty of them to not offer refunds and to announce this so late. There's no way that whenever they decided to include whatever middleware they're referring to that they didn't know they were releasing on Linux. No excuse.

Also as someone else mentioned this is against Kickstarter's TOS. KS itself won't refund you obviously but still worth reporting them, a TOS violation may prevent them from taking anyone else's money in the future on KS.

View this comment - View article - View full comments

Quoting: cprnDoes any of the "NVIDIA slows down old cards" shenanigans concern Linux users / drivers?

Yeah, it just as bad as it is on Windows. By that, I mean not at all as they don't slow down old cards, that's just part of the anti-NV circlejerk.

Unrelated: @liam you may want to warn people away from this driver - it breaks all Unity games in Proton and seems to have some issues with Wine in general.

View this comment - View article - View full comments

I think they need to ship two runtimes - a historical one to honor their promise of old games working indefinitely and a new one for new games and Proton. New one should be based on 18.04.

View this comment - View article - View full comments

Purchased, thanks Feral!

View this comment - View article - View full comments

Does anyone know if PoE II has any graphical downgrades on Linux? I was disappointed that the original didn't have the cloth capes. Not sure if any other effects were missing but I hate getting an inferior version.

View this comment - View article - View full comments

Awesome results! These Vulkan ports are getting better and better. Any benchmarks on a Pascal GPU? I know the Maxwell architecture was always considered to be weaker on Vulkan (less competitive with OGL in DOOM and DX11 in other games) than Pascal. I'm curious if that gap between Windows and Linux would get closed even further.

View this comment - View article - View full comments

I don't know about crashing during gameplay but it's completely broken for me at this point. Even the very first screen at launch is broken - all of the models are black and I get a message saying it's out of memory and to lower texture settings. I have an 8GB GTX 1080 and 16G of system RAM, neither of which show as being low on resources when the error pops up... so I think they've got an issue somewhere. I'm not lowering settings for a Source 1 engine game on a GTX 1080.

View this comment - View article - View full comments