Quoting: Eike

Quoting: rustybroomhandle

Quoting: DebianUser

Quoting: jordicomaUnsupported? This has more sense than on spanish "No compatibles" (no compatible), as many of these games works on my linux, even some are native.

Maybe unsupported only means that you do not have any support from the publisher ?
I agree not compatible is terrible.
The problem is that in this list, you have both : not compatibles, and compatibles but unsupported.

Unsupported reasons generally the following:

1. "Valve is still working on adding support for this game on Steam Deck" - When you see this it usually refers to Proton features being worked on. In most cases this refers to mfplat support. There's a good chance these will work eventually.

2. "This game's anti-cheat is not configured to support Steam Deck" - Not Valve's problem, fire ze missiles at the dev/publisher.

3. "This game is unsupported on Steam Deck due to use of an unsupported anti-cheat" - Don't expect these to work any time soon.

4. "Steam Deck does not support VR games" - I mean, you can in theory get VR working on the deck, but the experience will be terrible.

5. Games that fail to start at all. Tried to find an actual example of this, but gave up.

I would agree, but why is Outlast, which I played through natively, appearing on my "unsupported" list?

Native (and even "Platinum on ProtonDB/AppDB") does not equate verified for the Deck.

I doubt many games were made with a 7"-9" screen and controller only support in mind. In fact, I'd imagine some simply will never work by design, regardless of Linux compatibility.

View this comment - View article - View full comments

Quoting: anewsonkind of amazing how many problems HOTAS systems have relative to how expensive they are.. I had a Saitek x52 for Elite Dangerous and it had countless problems with not a ton of use.

Not gonna lie, the best stick I've owned is a Logitech Extreme 3D Pro joystick. Despite being a cheap retail stick (you can tell because they added "Extreme" and "Pro" to the name, lol)

Mines 17+ years old. Not perfect, but gets the job done.

View this comment - View article - View full comments

Quoting: elmapul

Quoting: denyasis

Quoting: elmapul

Quoting: denyasisI guess it's another win for Valve and Open source successes. I guess I feel slightly conflicted about it. While I appreciate Feral's work, I'm also glad that open source tools like Wine/Proton have finally taken over in a meaningful way.

I guess it's both a loss and a gain.

it is a loss.
on one hand, its good that an general purpose solution like wine/proton is better than porting, but that says more about the porting process and quality than about wine.
the ideal solution is linux geting enough marketshare to be threated like an first class citizen and open apis like vulkan becoming the standard.
its almost like if we were living the flash era vs html5 era, flash was multiplatform but had an crap support for linux, where html5 would be the "native" solution, using open standards.
while wine is gpl, directX isnt.

Is it? I'm under the impression most of these porting companies use wrappers, don't they? It's not like they all rewrote the binary and renderer into openGL. Maybe some did, but Valve has toGL, I forget what Aspry's wrapper was, etc. I'd bet some of these older ports looked a lot like a windows game under the hood, and the proprietary porting tech worked a lot like wine in some cases. Heck, there are even projects using DXVK as a wrapper for porting. I believe there are a number of Linux releases on GOG that are essentially wrapped with Wine.

I guess what I'm trying to say is that, in a sense, we've put the power to "port" into our own hands, at a level simple users like me can leverage. And if a "native" port is just using its own wrappers and layers under the hood, is there really a huge moral difference there?

take a look at this conference, where the company who ported dying light to linux comment about the porting process:
https://www.gamingonlinux.com/2015/04/techland-presentation-on-porting-dying-light-to-linux/

TL:DR, it was impossible to rewrite the code writen by 200 employees with only 2~3 employees, especially considering that the game was still under development and as a result the code was changing all the time, so they had to seek for paterns and make an translator or layer or soomething akin to that.
but if they relied only on this layers, the performance would tank and no computer in the world would be able to play the game in an acceptable framerate even on minimal setings, so they had to manually optimize any bootnecks.

i think that is how you port anything, write an general purpose code converter, then look at the profilers to see what is kiling the performance and optimize by hand.

as for anyone who want to complain that 'this or that company' is lazy, then go port something, there are plenty of open source projects on github that are windows only.
in the mean time, try to turn this ports of you into an sustainable business model, and if you can, you can complain about feral all you want.

Thanks! I'll try to check it out on my lunch break. I think it totally make sense that a porter would use a layer/translation tool/wrapper, especially if it is a business trying to maximize efficiency. I wasn't trying to imply the porters are lazy or anything, my apologies if it came off that way.

View this comment - View article - View full comments

Quoting: GuestThe only appeal they have now is to offer DRM free games

I think GOG kinda lost it's way when DRM-free stopped being a thing customers cared about.

When they started, it was a good play. There were a lot more stores and the number of stores was decreasing, so people could be concerned about losing their library if a store closed.

Today, I think people are not worried that a store like Steam will close, or are that worried about DRM in general asuch as they were in the past. I think GOG as a store didn't really figure out how to react to that in a meaningful way and still haven't.

View this comment - View article - View full comments

Quoting: elmapul

Quoting: fagnerlnI love Feral and I respect a lot their work, they are amazing. But yeah, fragmentation IS a issue, and Linux do a little to support older softwares (which is comprehensive) while Windows has a system bloated to just works™.

As their ports doesn't runs in a container, sooner or later it will stop working.

good point, as an reminder, we CANT blame feral for only supporting one distro, its the fragmentation fault that things wich work on one might not work on others to begin with, not feral fault.

I'd expect the contract to port to be very specific with regards to what they are porting to, probably down to a specific distro/version. Imagine if you were told to port a game to "every Linux distro"; it would be impossible! Maybe some people here who do porting or freelance work have better insight, but it seems sensible to me to be very specific on the deliverables as a protection from client abuse/allegations.

View this comment - View article - View full comments

Quoting: elmapul

Quoting: denyasisI guess it's another win for Valve and Open source successes. I guess I feel slightly conflicted about it. While I appreciate Feral's work, I'm also glad that open source tools like Wine/Proton have finally taken over in a meaningful way.

I guess it's both a loss and a gain.

it is a loss.
on one hand, its good that an general purpose solution like wine/proton is better than porting, but that says more about the porting process and quality than about wine.
the ideal solution is linux geting enough marketshare to be threated like an first class citizen and open apis like vulkan becoming the standard.
its almost like if we were living the flash era vs html5 era, flash was multiplatform but had an crap support for linux, where html5 would be the "native" solution, using open standards.
while wine is gpl, directX isnt.

Is it? I'm under the impression most of these porting companies use wrappers, don't they? It's not like they all rewrote the binary and renderer into openGL. Maybe some did, but Valve has toGL, I forget what Aspry's wrapper was, etc. I'd bet some of these older ports looked a lot like a windows game under the hood, and the proprietary porting tech worked a lot like wine in some cases. Heck, there are even projects using DXVK as a wrapper for porting. I believe there are a number of Linux releases on GOG that are essentially wrapped with Wine.

I guess what I'm trying to say is that, in a sense, we've put the power to "port" into our own hands, at a level simple users like me can leverage. And if a "native" port is just using its own wrappers and layers under the hood, is there really a huge moral difference there?

View this comment - View article - View full comments

I guess it's another win for Valve and Open source successes. I guess I feel slightly conflicted about it. While I appreciate Feral's work, I'm also glad that open source tools like Wine/Proton have finally taken over in a meaningful way.

I guess it's both a loss and a gain.

View this comment - View article - View full comments

This game is awesome. Literally saved my sanity during work travel with no signal.

My first play, I think I got infected/turned into a mushroom? And maybe I shot spores at people, I'm not totally sure, because then I died, probably horrifically. I was very confused, lol. Awesome.

Hopefully someone used my mushroom corpse in a fancy meal.

View this comment - View article - View full comments

Quoting: pete910

Quoting: denyasis

Quoting: pete910

Quoting: Frawo

Quoting: slaapliedjeHuh, Dying Light ran awesome natively for me. Granted I don't know if running under Proton makes it run better, as I had no reason to test it.

It definitely does run better in Proton, see Liams and Xpanders videos on youtube:

https://www.youtube.com/watch?v=11dZ0iuzH-M [External Link]

https://www.youtube.com/watch?v=kKdT3RuL9jQ [External Link]

Even if the game runs "good enough" with the native version, I think they still will prefer Proton as it seems to be more efficient and should draw less power from the battery.

It could also be because of the controller support. I don't know about Dying Light, but controller support in the native version of Trine is pretty much broken, while in Proton it works as expected.

IIRC liam has a 2080ti in the first vid ?

Here is a rx5700 non xt running dying light on a AMD R3 3300 CPU compared to windows .

https://www.youtube.com/watch?v=6j7LXbD0IN8 [External Link]

As you can see on AMD windows is only slightly better and this was 2 years ago, Mesa has improved a great deal since then!

If that is Liams rig in the first vid it is looking a bit pants compared to a lowly 5700 GPU. How much was a 2080ti, 1200ish?

Coincidentally, I tried Dying Light for the first time tonight. Native. Didn't work, got screen distortion and the splash screen videos would only do audio (codec issue?). Switched to proton and it worked just fine.

I'm sure the solution to make native run was probably something simple that I could research. Or I could spend the 15 min and let it redownload for proton...

I can't speak for all of us, but sometimes I just want to play instead of tinkering.

Whilst most of us just want to game, some things on a particulars computer can mess up at times which is annoying for the individual.

It may well have been a simple fix unfortunately you wont know.
It may have been a missing lib from a package of your distro of choice for example, Easily rectified via a bug report thus helping the rest of users on that distro. This is how Linux works, No?

Not saying that is the issue it's just an example.

Yet on the other hand I bet you've hunted for fixes on other games in the past that had issues in wine, Witcher 3 for example ?

If you did, Why not install windows and just game rather than tinker ?

I'm implying several things in my post, that upon reading, are likely not very clear. I'm commenting on the advantage Proton can offer, especially with aging native games, using Dying Light as a personal example. Obviously it's not a blanket advantage or that it is superior to all native ports, just that it has a very useful place in the Linux game ecosystem.

I'm also implying that we are not always in the mood to debug our system at any given time. Sometimes I may not be in the mood to debug or tinker. I'm also implying this "mood", if you will, may be more common with a typical Deck user that is expecting a more console-like experience. Obviously, that's not universal among all users or any user all the time. But either way, Proton can help.

You are correct that my example was a simple fix and I know what it is: Use Proton. There's more than one way to fix things. That's how Linux works.

You are also correct, I have tested, tinkered, even filled bug reports while trying to get games to work in Wine (and native). I don't recall if Witcher 3 was one having only played it for the first time several months ago and I don't recall having any issues at all, but I can definitely say so for others.

I'm simply trying to point out there is difference between sitting down at your PC and saying "I wonder if can get this game to run?" and sitting down at your PC and trying to play a game that you believe should run fine, both in terms of expectations and level of frustration when things don't work I'm also trying to point out that Proton can help in both cases (but especially the second in terms of easing frustration).

If you want to know why I use Linux instead of Windows, I recall there being a thread or two on this site about that. If you are keen on some simple research, I'm sure my response would be easy
to find. If you can't, feel free to post, but I fear that might be veering a little off topic. (Or at least more than we already are).

View this comment - View article - View full comments

Quoting: pete910

Quoting: Frawo

Quoting: slaapliedjeHuh, Dying Light ran awesome natively for me. Granted I don't know if running under Proton makes it run better, as I had no reason to test it.

It definitely does run better in Proton, see Liams and Xpanders videos on youtube:

https://www.youtube.com/watch?v=11dZ0iuzH-M [External Link]

https://www.youtube.com/watch?v=kKdT3RuL9jQ [External Link]

Even if the game runs "good enough" with the native version, I think they still will prefer Proton as it seems to be more efficient and should draw less power from the battery.

It could also be because of the controller support. I don't know about Dying Light, but controller support in the native version of Trine is pretty much broken, while in Proton it works as expected.

IIRC liam has a 2080ti in the first vid ?

Here is a rx5700 non xt running dying light on a AMD R3 3300 CPU compared to windows .

https://www.youtube.com/watch?v=6j7LXbD0IN8 [External Link]

As you can see on AMD windows is only slightly better and this was 2 years ago, Mesa has improved a great deal since then!

If that is Liams rig in the first vid it is looking a bit pants compared to a lowly 5700 GPU. How much was a 2080ti, 1200ish?

Coincidentally, I tried Dying Light for the first time tonight. Native. Didn't work, got screen distortion and the splash screen videos would only do audio (codec issue?). Switched to proton and it worked just fine.

I'm sure the solution to make native run was probably something simple that I could research. Or I could spend the 15 min and let it redownload for proton...

I can't speak for all of us, but sometimes I just want to play instead of tinkering.

View this comment - View article - View full comments