That’s why you shouldn’t drive a 1969 Mustang project car immediately after getting your licence. You figure it out on a 2003 Honda Civic, then move on to bigger things when you have both the basic knowledge and the willingness and ability to advance your knowledge.

You claim that installing with btrfs failed. Did you look into what the error messages meant? You claim to not know what Flatpak is. Did you look it up?

RTFM is not just a thought-terminating cliché used by elitist wankers. It’s a philosophy you have to live by if you want to play with powerful toys. Look at manuals, the Arch Wiki, Stackoverflow, or ask a clanker. If that’s beyond your abilities at this time, you’ll either have to improve yourself, or surrender for the time and try a more beginner-friendly OS.

The 10.0 is Wine’s version that the Proton release is based on, the -4 is the version of Valve’s patches on top of Wine. Steam doesn’t keep individual patch versions around, only the latest available patch for each major version.

I know. I was responding to the comment, not the video.

it’s still hard to set up Nvidia GPUs on Linux, even on Bazzite

No it isn’t. Wade specifically admitted that he didn’t do any “setup” beyond installing and updating the system. If he had done a minimum amount of superficial research, like googling “how do I install driver”, the numbers wouldn’t have been held back by NVK or llvmpipe. The video is not representative of Linux gaming, or Bazzite even. He half-assed his way to some kind of result.

I know, I was talking about the state of Vortex as of today.

My experience says: don’t. Vortex uses some weird-ass GUI toolkit that doesn’t like running on Wine. Mouse-related events (hover, click, drag) sometimes don’t fire. If MO works for you, Vortex is probably not worth the effort.

I’ve played all three games. Arch on PC, Lutris, some GE-Proton 9 version. If the camera acts up in ME2, try Gamescope with relative mouse.

EA App didn’t come up. If it causes issues, try an alternatively sourced copy.

Look at this: https://github.com/ChthonVII/guildwarslinuxinstallguide?tab=readme-ov-file#part-11-toolbox

“Run EXE inside Wine prefix”

It might not work, though. I’ve tried to use a similar tool with Snowrunner, it found the process, but didn’t actually work.

One of these might help: https://steamcommunity.com/app/275850/discussions/0/601902145259725017/

Although I wouldn’t be surprised if it was caused by NMS’s own network backend. When the Corvette update was launched, multiplayer was fine on my work computer, but did not work on my home PC. It’s a constant dumpster fire.

If you have Steam installed, try putting them in ~/.local/share/Steam/compatilitytools.d.

He can’t, he had to re-run a benchmark.

The option doesn’t have a value. You just need to specify that the option should be present, e.g. defaults,noatime,windows_names,uid=1000,gid=1000 in fstab, or mount.ntfs -o noatime,windows_names,uid=1000,gid=1000 for manual mounts.

This comment on the UDisks github page elaborates on why the ntfs-3g driver does not automatically restrict the usable characters.

UDisks itself does mount NTFS volumes with the windows_names option, and the last comment in the same thread explains why enforcing that restriction with no way to opt out is a breaking change for some users.

uid=1000,gid=1000,dmask=022,fmask=133

You can very easily fuck up your NTFS filesystem and make it unmountable in Windows. Would anyone be surprised to learn that not even Windows is fully compliant with the NTFS specifications? Some characters, like :, are valid for NTFS filenames, but illegal in Windows, and if you create such a file (e.g. in a wineprefix’s dosdevices), Windows will refuse to mount it. Ask me how I know.

The solution is to specify the windows_names option every time you mount the filesystem, both in fstab and when using mount.ntfs.

Then why are you complaining about not getting a Gamers Nexus video that benchmarks game performance spelled out to you when it isn’t even relevant to your use case?

Being able to use anything other than Windows without any significant loss in performance is a pretty fucking big advantage.

My main concern about that is that using AA and AAA form factors promotes the use of disposable dry cell batteries, even if nickel or lithium cells are just as widely available. And, realistically, not even the closest Li-ion form factor is fully compatible with AA, and Ni-MH sucks balls.

The controller is also filled to the gills with hardware. Doesn’t look like there’s enough volume left for AA or AAA receptacles without giving it an underbelly to rival the Xbox Duke.

Week one, somebody’s going to release a CAD file for a 3D-printable shell with a removable battery cover.

Try Onlyoffice. It’s designed to look and feel like MS Office.

The first time I saw that guy turn around, I damn near pissed myself.