Did the game not have some sort of internal, not Steam account before for crossplay? I'd assume it did, so what's a PSN account going to do here?

"protecting our players and upholding the values of safety and security"
Huh?

Conversely, what's the downside to making a PSN account? I don't think this means any extra step other than that one time account creation step, no launchers or anything no? what's so bad about this move other than 4 extra minutes of setup?

View this comment - View article - View full comments

Quoting: Rui_CastroI've tried uninstalling but always get a error. I know I've done this before for Proton 7. Just don't remember what I did. Any help?

What the others said, and to make fixing this easier, you can use something like ProtonUp-Qt [External Link] which will show you a nice interface that lists all your installed games and what Proton version they're forced to use, if applicable.

View this comment - View article - View full comments

[/quote]

Quoting: pleasereadthemanuala trustworthy option might be the Open Build Service RPM package provided by cryptomilk, who is a Fedora Proven Packager and contributor to Signal.

Thanks for the super thorough response! I think I'll settle for the cryptomilk RPM package, and this is the first time I hear about this Open Build Service, sounds really cool, I'm glad OpenSUSE is also RPM which is something I just found out about now too, many lessons learned, thanks again.

View this comment - View article - View full comments

Quoting: legluondunetWhat about Fedora? I would be interested in your feedback.

I'll go a little deep here and talk about my experience with also Linux in general as someone who I wouldn't call myself technical but got tired of Microsoft's shit so here it goes:

I'm a month old Linux user and Fedora has been basically perfect, I don't want to hear about it that Fedora or KDE are too bleeding edge, unstable, unreliable, not gaming ready or whatever else I saw going around before doing the switch. It was too stable I got bored and learned how to install stuff like fsync-kernel and latest mesa drivers through copr repos, if a dumbass like me can do systemwide changes within a couple of weeks of using the os, while being on exams period so I didn't necessarily have lots of free time, then everyone can do it as well.

And I like package managers and DNF, while I'm exclusively a GUI person naturally, I now prefer package managers because I find them way more informative and easy to follow, this was the case for me for the last two years with winget on windows, and DNF is like a couple of generations ahead of that.

I would probably be considered a power user by now, but I don't feel like that's the case, I don't feel like I became a computer hacker or anything at all, this past month of "learning" how to use linux was smooth sailing, pretty much every problem or something that was simply new to me, just looking it up and I can easily follow along, it all feels very natural and things just make sense why they're the way they are, if they don't I just copy paste the commands. I think the concept of Linux being too difficult right now is just a consequence of my generation becoming too tech illiterate, everyone just uses their phones nowadays and have no clue how computers work, another thing is the social aspect which I also don't understand, if you use anything that even slightly deviates from the norm, people will think you're a nerd/hacker/strange person etc, or you're trying to be special and stand out, it's so weird.

The only thing I'm missing right now is proper VRR working, even on AMD, this is in fact a big bummer: for some reason whenever VRR kicks in, brightness flickering occurs, it depends on how bad the frame fluctuates but it's mostly not as annoying as you'd think, it's a Wayland thing I think I'm not sure, from what I learned this is something KDE will need to work on and it affects everybody? Correct me if I'm wrong I'd be happy to fix this.

Quoting: pleasereadthemanualNo official Signal Desktop package. Where do you get it? From the unverified Flatpak? From openSUSE's OBS, which is maintained by a Fedora packager? From the COPR? Do you compile it yourself?

So the flatpak is not verified? I never realised that! is this worthy of concern? I don't know how this works, can one like check how the flatpak is built or whatever so one can be sure there were no modifications? What do you use to get Signal then if not the flatpak?

View this comment - View article - View full comments

What have you been playing recently?

Just started Touhou Luna Nights [External Link], great start so far, I think there's some lore I'm missing on but it doesn't seem to matter. I'm also playing Mirror's Edge and it's really fun, should be short too which I prefer so I should be close to finishing it. No one on the game's ProtonDB page seemed to have bothered to fix some of the technical issues so I'll try not to forget to do my part and share how I fixed those and post to the ProtonDB page. Before those two I was playing Alan Wake and found the game to be too boring so I flushed it, a shame as I do love Remedy's games.

View this comment - View article - View full comments

Quoting: Liam DaweAt least with Proton, being open source (and based on Wine), the maintained version can continue to be improved upon using it.

True. So in a sense, there's a potential for better longevity with Proton vs Native, actually. Being open source should mean there's always those who are passionate and skilled who can work to make a game continue to work, that and, you know, Valve, being obligated to keep ensuring whatever they sold on the Steam Deck continues to work.

Quoting: CalinouThere are a few practical issues with WINE/Proton that are more or less unsolvable by design:

- Slower startup times (compare `wine simple_program.exe` with `./simple_program` of a native Linux binary). This is especially the case if the WINE prefix needs to be updated following a WINE update, in which case it can take 10+ seconds.
- Larger file size – a WINE prefix isn't small, especially if you use one prefix per game.

Great points. I never realised that going with Proton means a slower startup, I think it's because it is pretty fast already, but obviously native should launch even faster.

The large file size is definitely an issue, and I suspect it'll become even more prominent over time as I keep downlaoding different version of Proton/Wine. Though I imagine in the future we should reach a point where only one Proton version is needed for virtually everything on Steam. And a select few for edge cases outside of Steam. I wonder if it's also possible to reduce Proton/Wine prefix's filesize too.

Quoting: PyreticHonestly not much

Yeah, I've just been thinking about it and thought it was interesting. "Okay, we're stuck with this "hack" to play our games, what could actually be so bad about it if that's the case?" And so far it doesn't look too bad, which is reassuring.

View this comment - View article - View full comments

Quoting: Ehvis

Quoting: PyrateRealistically speaking, what could be so bad if Proton became the de-facto Linux support method for all games, including games that would've had Native Linux support if the developers were generous enough?

Because in practice, proton "support" often means ignore it and let Valve deal with any issues. I think I can count the number of devs that actually fixed something to get it running better (or at all) on proton on one hand.

I see, though I think that can also be applied to Linux Native ports too, no? whenever they get broken, fixes are usually rare from what I read, I'm asking here because like I said, I'm new and I wouldn't know how native ports went, what I hear nowadays is that the majority of the native builds are broken/worse than if with Proton.

So let me reiterate my question: From what I see, the work required to maintain 2 different versions of a game is generally too great for most dev teams, when taking into account the financial cost behind this. Call it laziness or whatever. Native Linux ports are a rarity, and so, Proton appears to be the reality we're going to have to accept, for better or worse. So, what is worse here? Bearing in mind that the only scenario where we start getting properly supported ports is if the market shifts to Linux (never).

I think the number of devs who'd fix something in Proton is the same number of whom would bother to make a native build anyways. And if Proton is easier to deal with, what could be the downsides? this is basically asking my original question again but better.

View this comment - View article - View full comments

Realistically speaking, what could be so bad if Proton became the de-facto Linux support method for all games, including games that would've had Native Linux support if the developers were generous enough? I'm a new Linux user and I've been thinking about this.

Asking for native ports is chasing a wild goose, to fix this issue you'd have to go to the source of it: user market share, until Linux becomes figuratively mainstream, that's when asking for native ports becomes logical and feasible, in my opinion.

View this comment - View article - View full comments