Well, Endeavour is just arch. If you want, you can achieve the same install that has only the things you need, by removing things instead of just adding.

IMO it starts off closer to the config most people want, so it’s less work to take it the rest of the way.

Short of answering any questions about a product I ask, all of them.

If I want or need something, I will come looking. Anything beyond that is the market trying to solicit demand where none need exist.

So much waste could be eliminated if that just… Stopped.

Not even close, if you actually install barebones arch, then barebones arch is exactly that, barebones. You wont even have a DE.

Endeavour is what you want. It’s just straight up arch, but with all the stuff you’d want to set up anyway done for you.

And if you want an “app-store” style app to browse packages with, and not fiddle with the command line to manage packages, install pamac. It can be expanded with AUR and flatpak support.

That’s nice. But I think most people literally just hook up the big screen with an actual display cable.

With AUR it’s as easy as installing any other package, actually.

You just install the git version from AUR.

There were apparently several, now that I look into it. I didn’t know that.

They seem to try to mitigate other issues, like asset streaming and other general bad practices in the code of the game.

It seems there are many things wrong with how Elden Ring was coded.

I suspect most people who buy one already have another gaming device. If I’m gonna play couch co-op games, I’m just switching the video output of my desktop to the projector, not docking my deck.

I do want to add that new games can also require new packages, the way Alan Wake II did at launch. Even on Arch you had to compile the development version of Mesa for it to run.

Cinnamons compositor doesn’t turn off for games (it’s supposed to but has been bugged for years) which costs you fps.

Playing Alan Wake 2 at launch was only possible with the latest Mesa drivers compiled from the AUR due to some graphics features that it required.

Yes. But Valve didn’t do anything special. They provide pre-compiled shaders for all games on the deck and can only do so because of how directx shaders are handled on linux.

All games on linux and windows when using DX12/Vulkan must compile shaders. They should be compiled during loading screens and such, not gameplay, then cached for use later.

Elden Ring in particular, didn’t precompile shaders before gameplay, and then when it did compile them, it would discard the shaders rather than cache them. As a result the stutter would happen non-stop and never go away.

On linux, the equivalent compiled vulkan shaders are cached by VKD3D, eliminating the stutter except when a shader is used for the first time. On the deck, Valve will deliver the shaders precompiled with the game download to eliminate the need to compile them at all.

The fix of providing precompiled shaders was only possible on linux due to the use of VKD3D. And even without them, on linux the stutter would go away after a while as VKD3D will cache them even when the game doesn’t. Fromsoft had to update the game to fix it from their side on windows.

It is. In fact at launch it ran better than on high end windows PCs because linux handles directx shaders better.

Immersion, yes, but also haptics provide feedback.

Lots of games use it to tell you things, like when your health is low, when to time something, when you took damage vs blocked successfully, when you’re close to a secret…

Used right, it’s another sensory input channel in addition to sound and visuals.

One of the biggest genres that I use a controller for, because I consider KBM to be unplayable for it, is racing games. And there haptics are used to tell you TONS about what is happening in the game.

I set up !ballisticng@sopuli.xyz as I’ve seen the game mentioned all over lemmy now.

Hoping to eventually organize some online tournaments, but we’re gonna need players :D

I set up !ballisticng@sopuli.xyz as I’ve seen the game mentioned all over lemmy now.

Hoping to eventually organize some online tournaments, but we’re gonna need players :D

!ballisticng@sopuli.xyz

Hoping to organize some online tournaments. Maybe monthly? Gonna need players :D

50?

So they left out vibration so it wouldn’t be the usual 60?

Those savings don’t take the price down to “will buy” they take the featureset down to “will never buy”.

Still just on the first step, embrace.

Apparently threads didn’t support federating replies (comments) on posts until this.

And you still won’t be able to reply to the federated comments on posts, just see them.

They are really not in a hurry to properly support federating. I honestly didn’t realize Threads’ federation support was this pathetic.

Modern ADSL and VDSL can get you pretty far… But they don’t hold a candle to fibre.

Other way around. Pure and Pulse were PSP first, then PS2 and later PS3.

The PS2 port of Pulse is graphically superior, and can be run using PCSX2. HD has the same content.

Instability might be due to shader translation, should go away as more shaders are compiled and cached.

Vita3k for 2048 runs very well (with compilation stutters only at first), and you can get the HD and Fury DLC for it to access the PS3 content (though with lesser graphics).

Valve didn’t do anything in particular for Elden Ring.

The way running windows games works on Linux just meant that compiled shaders got cached, so that when they were needed again, the game wouldn’t freeze for a split second while they were recompiled.

This process is necessary on the windows side as well, when using DirectX 12 or Vulkan. Most games will do this shader compiling in advance (during a loading screen), and cache them for later so that the GPU can run full tilt generating frames during gameplay, instead of pausing to compile shaders.

Elden Ring didn’t do this. It compiled shaders as they were needed mid-gameplay, then immediately discarded them instead of caching them. This meant it was constantly freezing to compile shaders as materials that used different ones appeared on screen. And it would keep happening as it didn’t keep compiled shaders around for the next time they were needed.

Only on Linux, there was an external cache in the system that was translating the games DX12 calls to Vulkan (VKD3D), which would just go “oh I already have that, here you go” essentially making the game work as if the constant compiling could be done instantly whenever needed.

Valve did provide the cached shaders as a download, compiled in advance, as otherwise you’d still get compilation stutters each time something on screen needed a particular shader for the first time. But Valve does this for all games.