We do often include affiliate links to earn us some pennies. See more here.

Every now and then, the people behind ProtonDB release data dumps from user generated reports of games tested in Steam Play.

What is ProtonDB? It's an unofficial statistics website, where you can note how good or bad various games run on Steam when played with Steam Play. It's a fun one to track, so with a new data dump I thought it might be interesting to try my hand at getting something out of the data for anyone curious.

The latest data dump is available here, which shows a total of 29,823 reports so it's getting rather massive. It goes to show just how many people are testing a wide variety of games!

First up, here's a look at how many reports are going in monthly:

Clearly less reports going into it as time goes on, which is quite interesting. Now, it doesn't mean Steam Play is suddenly any less popular of course, we do have to remember this is an unofficial website and given how many games have a lot of reports already, some may now just look to see existing reports.

Specific to this month, there were 3,119 reports. Here's a breakdown of those reports (one didn't seem to have a status set correctly):

As for the actual games being reported, here's the top 15 most reported games on ProtonDB through January:

Quite an interesting and varied selection there, with Yakuza 0 being no surprise since it was part of last month's Humble Monthly.

It's also nice to see so many people trying out (and enjoying) The Witcher 3, with it being the second most popular game. I'm not entirely surprised here, as I imagine a number of people purchased it originally when a big announcement was made about it coming to SteamOS/Linux which never actually happened in the end. It's another reason why Steam Play is such a great idea, for the times we are sadly let down and for those who don't care about port arguments who just want to play great games.

Here's a look at some more details like Linux Distributions. This one is a close-enough approximation, as the list of distributions is quite varied and messy on the naming, as it's gathered from Steam's system information output:

Note: Some distributions only come up as "Linux 4.x". For those, we're verifying using the Kernel string for both Arch, Fedora and Gentoo. Still looking over ways to do the same for others. All other distributions are bundled into "Other".

Next, here's a look at what types of GPU people are using when attempting to play games with Steam Play:

And again here with what CPU people are using:

Additionally, most reports (1,757 of them) were made using the latest available Proton Beta 3.16-6.

Hopefully I will take another look when they do their next database dump, if people find it interesting enough of course.

Article taken from GamingOnLinux.com.
Tags: Proton, Misc
37 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly.
See more from me
The comments on this article are closed.
67 comments
Page: «6/7»
  Go to:

Liam Dawe Feb 5, 2019
Quoting: axredneck
Quoting: liamdawe... it's now verifying with the Kernel string too as Arch 99% of the time has arch in the Kernel version...
Antergos has "arch" in it too
Antergos properly identifies itself as Antergos though, as far as I am aware.
axredneck Feb 5, 2019
Quoting: TheRiddick...As for AMD GPU ... if you can enable screen tearing options similar to nvidia's fullscreenpipeline stuff...
AMD doesn't need such option because vsync "just works" there
tuubi Feb 5, 2019
View PC info
  • Supporter Plus
Quoting: axredneck
Quoting: TheRiddick...As for AMD GPU ... if you can enable screen tearing options similar to nvidia's fullscreenpipeline stuff...
AMD doesn't need such option because vsync "just works" there
The point of Nvidia's full compositor pipeline setting is that it'll prevent tearing even if you disable v-sync. I think AMD's TearFree option has a similar effect.
Shmerl Feb 5, 2019
Quoting: tuubiThe point of Nvidia's full compositor pipeline setting is that it'll prevent tearing even if you disable v-sync. I think AMD's TearFree option has a similar effect.

The point of that "forced pipeline" is really because normal vsync is broken on Nvidia, unlike on AMD. That's why it's plagued with tearing on Linux. The reason is that they aren't using proper kernel interfaces for it. That "forced compositing pipeline" is a crude workaround, not a proper solution.


Last edited by Shmerl on 5 February 2019 at 10:20 pm UTC
tuubi Feb 6, 2019
View PC info
  • Supporter Plus
Quoting: Shmerl
Quoting: tuubiThe point of Nvidia's full compositor pipeline setting is that it'll prevent tearing even if you disable v-sync. I think AMD's TearFree option has a similar effect.

The point of that "forced pipeline" is really because normal vsync is broken on Nvidia, unlike on AMD. That's why it's plagued with tearing on Linux.
That doesn't really match my experience, but I guess I'll take your word for it.
Shmerl Feb 6, 2019
Quoting: tuubiThat doesn't really match my experience, but I guess I'll take your word for it.

You mean you didn't have any tearing issues even without using that "forced pipeline" setting? When I was using Nvidia, I constantly had them. vsync plainly didn't work at all.


Last edited by Shmerl on 6 February 2019 at 6:58 pm UTC
tuubi Feb 6, 2019
View PC info
  • Supporter Plus
Quoting: Shmerl
Quoting: tuubiThat doesn't really match my experience, but I guess I'll take your word for it.

You mean you didn't have any tearing issues even without using that "forced pipeline" setting? When I was using Nvidia, I constantly had them. vsync plainly didn't work at all.
I wouldn't say I didn't have any issues, but (opengl/vulkan) v-sync mostly just worked. I remember I used to have tearing with video playback before all the players supported hardware acceleration (vdpau), but it's been a while.

I only recently switched (back) to AMD, and immediately had to enable TearFree to fix tearing issues so the difference isn't as dramatic as you make it seem. When it comes to this particular issue that is. Of course there are other things AMD and even Intel do better than Nvidia, even if you ignore the ideology. But this is getting a bit off topic so I'll leave it there.
Brisse Feb 6, 2019
Quoting: tuubiI only recently switched (back) to AMD, and immediately had to enable TearFree to fix tearing issues so the difference isn't as dramatic as you make it seem.

I see you are using xfce and I'm not surprised. TearFree is enabled out of the box on most sane mainstream DE's like Gnome and KDE. I'm not saying xfce is bad because it certainly has it's place, but the issue in your case isn't with AMD, it's with xfce's bad defaults.
wvstolzing Feb 6, 2019
Quoting: BrisseI see you are using xfce and I'm not surprised. TearFree is enabled out of the box on most sane mainstream DE's like Gnome and KDE. I'm not saying xfce is bad because it certainly has it's place, but the issue in your case isn't with AMD, it's with xfce's bad defaults.

I get screen tearing even on intel integrated, with XFCE (compositor on).
Brisse Feb 6, 2019
Quoting: wvstolzing
Quoting: BrisseI see you are using xfce and I'm not surprised. TearFree is enabled out of the box on most sane mainstream DE's like Gnome and KDE. I'm not saying xfce is bad because it certainly has it's place, but the issue in your case isn't with AMD, it's with xfce's bad defaults.

I get screen tearing even on intel integrated, with XFCE (compositor on).

Yep. If someone is complaining over screen tearing on Intel or AMD graphics, it's pretty safe to assume they are using xfce.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.