I'd really like to play (and lose) some rounds of PUBG finally.

View this comment - View article - View full comments

Quoting: GuestIn fairness, I have no doubt that these preorders are a limited run to gauge interests before they go into mass production

And they do the same trick for GPUs an PS5?

No, no matter how many they want to make, there's a supply problem.

View this comment - View article - View full comments

I'm not following it closely, but I get the impression of maturing code that will be included sooner or later (sounds like sooner to me).

View this comment - View article - View full comments

Quoting: nenoroBefore this news
EG: there's no player on linux

After this news
EG: let's support linux

What element has changed their mind ?

They finally heard of Steam Machines...! ;)

View this comment - View article - View full comments

Quoting: Liam DaweBesides, I am perfectly relaxed but I do very much like to explain how things work. Most people just don't understand the trials of SEO to get them to actually pick us up :)

I'd send a "correction" message if I'd really think there's something wrong (like I did lately for the 32/64 bits OpenGL/Vulkan thing). :)

View this comment - View article - View full comments

Quoting: Liam Dawe

Quoting: EikeThe heading got it all wrong!

... including native builds!

We knew EAC on Proton would be a thing this year, but native comes as a very pleasant surprise - at least for me!

Well, no. Native support was already there with developers already using it but now it's been bumped up in a more official and advertised way. The more exciting news for 99% of readers is Wine and Proton which is why we went for that as the headline, it's simple really. We may not work on clicks and such since no adverts but we still need to make sure headlines cover the most important bits for drawing people in.

Relax, Liam. It was said jokingly to express what I find more interesting. In general, you do too much defending.

View this comment - View article - View full comments

The heading got it all wrong!

... including native builds!

We knew EAC on Proton would be a thing this year, but native comes as a very pleasant surprise - at least for me!

View this comment - View article - View full comments

Quoting: BeamboomFor a most of those questions there were really quite obvious answers though - after all this is just a PC w/Steam client in a small casing, with all that implies. Of course they'll run the standard Proton etc.

I really wasn't sure about that for anti-cheat. I wonder how that could work, really work, on a fully open-source system without some TPM "you cannot change anything here" mechanism.

View this comment - View article - View full comments

Quoting: cip91skUhm, that post on stackexchange is from Dec '19, but there's a patch from March '20 [External Link] that seems to enable it on tune2fs, and it seems to be supported on the tune2fs man page [External Link], so maybe it doesn't need to be formatted again

Looks good!

This still will be an (if not the) FAQ: "Why doesn't it work?!?" "It works on Steam Deck, we do not support your system!" ... and the real answer is: Windows programmers were too ... (I'm not sure about the appropriate adjective here, I mean, it's automatically right if you just copy and paste!) to use the same casing for their calls as the actual files have, they don't see the problem on Windows, don't see it on Steam Deck, don't care.

View this comment - View article - View full comments

Quoting: dpanter

Quoting: EikeThere's a compatibility problem lurking here for all who are running case sensitive filesystems - which should be about everybody.

It should be fine, things that rely on case will still function the same but (in theory) Proton will no longer be afflicted. This feature has been around a good while now.

A filesystem that has the casefold [External Link] feature set is able to configure directories with chattr +F (EXT4_CASEFOLD_FL) attribute, enabling lookups to succeed in that directory in a case-insensitive fashion, i.e: match a directory entry even if the name used by userspace is not a byte per byte match with the disk name, but is an equivalent case-insensitive version of the Unicode string.

The feature is configured as an inode attribute applied to directories and inherited by its children. This attribute can only be enabled on empty directories for filesystems that support the encoding feature, thus preventing collision of file names that only differ by case.

So, if my ext4 supports this, Steam/Proton could enable it for its directories (and only for those)?
If I installed my file system many years ago, does it support it?
Can it be upgraded?

*edit* Doesn't look good for question 2 at the moment:
eike@track:~/temp$ LANG=C chattr +F CasingTestDir
Usage: chattr [-pRVf] [-+=aAcCdDeijPsStTu] [-v version] files...
*edit2* I upgraded my ext progs (thanks again, buster-backports!), but...
"Sadly, I couldn't manage to enable it on an already formatted filesystem." [External Link]

So, everything is fine... if you format your disk to support the feature.

View this comment - View article - View full comments