Happy birthday GOL! :grin::grin:

View this comment - View article - View full comments

Quoting: ArehandoroFor the Linux build, the title will change to Hero.sh, right?

Came to say exactly this (except maybe I would have capitalized the SH)... you won this time

View this comment - View article - View full comments

Quoting: Eike

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.

Uhm, 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

View this comment - View article - View full comments

I'm entering to win a copy! I spent countless hours on the first one :woot:

View this comment - View article - View full comments

Happy birthday!! :woot::woot:

View this comment - View article - View full comments

Thanks for the heads up! However I remember reading that the infinity fabric's speed is dependent on RAM frequency, and that at ~3200+ mhz games weren't affected so much, so can you tell us what configuration are you using? And, if possible, can you try again at higher RAM frequency?

View this comment - View article - View full comments

They mention Nvidia We've just asked Epic about any news and apparently there aren't any and they're contacting Nvidia again
I wonder it this is a problem with OpenGL in general or just with Nvidia's implementation :huh:, did someone try the demo they shared on AMD hardware?

View this comment - View article - View full comments

Did the laptop have 2x4gb or 1x8gb? AMD APUs tend to perform worse [External Link] with only one dimm

View this comment - View article - View full comments

Got key 2, thanks :)

View this comment - View article - View full comments

"Code already redeemed" for all of them, thanks anyway!

View this comment - View article - View full comments