nvidia-vaapi-driver VS Proton

For anyone wondering, I got hardware acceleration working (NVIDIA 1660 Super: h264, vp8, vp9, don't know why I can't get HEVC support currently) using the nvidia-driver-545 using the steps from nvidia-vaapi-driver to build from source (version: 0.0.11)

I don't think it's your fault and I don't think you're using the wrong browser.

> I should be working out the dependency story and compiling some driver from Github myself.

no, nvidia _should_ make it easier for people using the 3rd most popular desktop OS to use their hardware. It would make them more competitive against AMD and Intel, which both support hardware video decoding.

That's probably not going to happen, so the next best option is to install a package from the package manager [0]. There might be some kind of compilation needed, but in my experience that's rarely an issue (aside from time), especially if it's coming out of the package manager for a popular distribution.

> It's just not a real option for maybe 99% of PC users.

well, 99% of PC users with Nvidia hardware. It's an important distinction since this problem is specific to Nvidia. If the solution is to installing a package from the package manager, it's only as difficult as installing the browser in the first place.

I do agree there's some extra questions that may make things difficult, or unfamiliar for the vast majority of people, though. Like how is someone supposed to know they need the nvidia-vaapi-driver package anyway?

[0] - https://github.com/elFarto/nvidia-vaapi-driver#package-manag...

to be honest, pop os solved most of my problems except the hardware acceleration problem which seems like an issue with Nvidia. I am planning to try this soon. https://github.com/elFarto/nvidia-vaapi-driver/ as mentioned in the comments

RpmFusion only has v0.0.9 of nvidia-vaapi-driver although release v0.0.10 adds support for Nvidia drivers v535. https://github.com/elFarto/nvidia-vaapi-driver/releases/tag/v0.0.10

I do have one machine with the Firefox PPA rather than the snap, and that's because I've got an NVIDIA card in it and want to use an experimental library.

Note that as an nvidia gpu owner you need to do some extra backflips to make firefox use hardware decoding such as installing a custom vaapi-to-nvdec translation driver: https://github.com/elFarto/nvidia-vaapi-driver

General VDPAU vs VA-API video acceleration pains. Needing a community driver for imperfect VA-API support, that nvidia updates have broken multiple times.

Don't use VDPAU, this driver is much better: https://github.com/elFarto/nvidia-vaapi-driver

The "Metaverse" is a complete joke, and among gamers, Valve has a way better reputation than Meta. Why would they want to dilute that brand?

They already have their own platform (Steam), OS (SteamOS), VR headset (Index), their own Windows translation layer (Proton, https://github.com/ValveSoftware/Proton), their own partnership with cloud gaming (Steam Cloud Play using GeForce Now , https://partner.steamgames.com/doc/features/cloudgaming), etc.

IMO: As someone with thousands of games on Steam, there's no way in hell I'd want that linked to Facebook. I think they eventually removed the requirement to have a FB account to use a Quest, but they still require a Meta account. Yuck.

This reeks of Facebook recognizing the Metaverse as the failure that it was and opening it up because it's no longer relevant...

Or Valve's Proton[0], a tool for playing Windows games on Linux.

https://github.com/ValveSoftware/Proton

Did you mount it with the correct flags?

there is a hack to try and use your existing windows game install from an NTFS drive, but i don't recommend it as steam will try to save file names that are not allowed on NTFS...plus ext4 is faster.

From a quick search, here's what I found. It looks like you're encountering some common issues that can occur with games running on Linux through Proton, especially with the recent updates to games like Satisfactory that might affect compatibility. The log entries you're seeing related to D3DCompile2 failing to compile shader and the issues with Ternary operator and LinearToSrgbBranching not being defined, suggest that there's a problem with shader compilation. This can often be related to the version of Proton or the graphics drivers you are using. Some users have reported that the game does launch with the -vulkan option but with graphical glitches and lower performance, which indicates that the Vulkan renderer is working but possibly not optimally on your setup. From the discussions in the community, users have suggested ensuring that the latest drivers for your graphics card are installed and, if using an Intel GPU, that the Mesa drivers are up to date since Intel XeSS references were found in the logs. If you're using NVIDIA graphics, make sure you have the latest drivers and possibly set the PROTON_ENABLE_NVAPI=1 %command% to enable DLSS if you're under Vulkan. If you're using an Optimus laptop with both Intel and NVIDIA GPUs, make sure your Optimus setup is correctly configured. Some users have found success by specifying DXVK_FILTER_DEVICE_NAMES=GeForce to force the game to use the NVIDIA GPU. It's also worth noting that if you're encountering issues with DirectX 11, you might want to try forcing the game to use DirectX 10 if possible or look into DXVK configurations that could resolve compatibility issues. Lastly, if none of these solutions work, you could try running a trace with apitrace to gather more detailed logs that might point to the specific issue. If you're still stuck, it would be a good idea to report the issue to the Proton GitHub page or seek further assistance in the game's community forums where others might have encountered and solved similar issues. For more information and to find others who might have resolved similar issues, check out the community discussions on GitHub​​, Steam Community​​, and the DXVK GitHub page​​.