Could be a prod ready engineering sample. They get around more than you may think.

suse is neat 🥰

habibi I’m afraid I’ve not had good experiences with manjaro, I may need to defer to someone else in this thread. tumbleweed is cool as heck though.

I’d personally stick to fedora?

This may be at odds with stability somewhat being rolling release, but you may want to check out SUSE tumbleweed or EndeavourOS. You already have a solid pick based on your established requirements.

Couldn’t hurt to poke around other offerings in a VM, though

aye she’s a lil pumpkin

big paws are for big adventures! 😊

such a beautiful pup 🥰

fair enough, it’s still in stark contrast to all of eternal’s exposition, which was pretty hard to watch (the Colosseum scenes especially).

That’s not to say the story isn’t good or interesting,

2016 had the perfect balance between story and gameplay to me, in that the player character expressed flagrant disregard for any narrative elements. This was doom 1 af.

Just keep moving and turn the bad guys into chunks. Need nothing more.

I fucking hated the loop in eternal. I get that the developers wanted you to play in a specific way, they partially achieved this through arbitrary mechanics like ammo scarcity. I can appreciate that it’s a good game, but I didn’t get on with it.

The art style went full Hollywood horror, and the exposition was kinda dialed up to eleven by contrast to its direct predecessor. Very much disliked that you couldn’t crouch (definitely more of a me issue, though I think sliding is a missed opportunity in Eternal’s movement repertoire).

2016’s PvP was imperfect but still fun and much appreciated. Snapmap was super underrated and has many sick community made levels.

The later games are a phenomenal technical showcase; the absolute posterchild for the Vulkan gfx API, but it’s not very ‘doom’ in spirit to me any more

well, at least they provided some rationale for switching browsers. still, it’s good thing we have bazzite.

I feel that, I just wanted to set your expectations. I prefer and will continue to use CalyxOS but I have no expectation that they will deliver the same level of protections/mitigations at the OS side as Graphene given their project scope is different.

CalyxOS aims for a private, yet simple (attainable) Android experience, and I align more closely with their ideology on having a FOSS replacement for Google Play Services in MicroG.

I suppose one thing you could levarage is work profiles on Calyx to “jail” apps you do not trust, though I’m not sure that meaningfully builds upon Android 15s own application sandboxing.

Perhaps as a long term goal you could look into making a custom fork of CalyxOS for your device and incorporating parts of Graphene’s hardening but this will be a lot of work.

As a calyxOS user, if your key concerns are security and device hardening, I’d recommend you just make a seedvault backup and switch to graphene.

The two projects have somewhat different scopes and I don’t think you’ll achieve the same degree of sw security on calyx.

I’m aligned on this. Server side ought to be the way.

Also fuck cheaters.

Yeah like, as a keen advocate for Linux desktop use, this is a wildly dishonest take / headline to run with.

Yup. It’s a cat and mouse game until server side can become enconomial enough to broadly deploy (computational & network constraints).

I mean it’s kind if good that both WU on Windows and LVFS/fwupd on Linux seamlessly deliver and install SBIOS updates.

Chances are it was worth installing, if a little inconvenient at the time.

There’s so much wasted potential in infinite, yet the core mechanics are pretty nailed down.

I’m astounded they released this multiplayer focused game with no betrayal booting or any form of in-game player reporting.

I don’t believe FPO was expanded to >2 displays, though having identical panels would eliminate VBI complexities. Will be interested in understanding how this behaves with rdna 4.

Huh interesting. Are these displays all the exact same model?

There’s a relatively new feature in the amd gfx display abstraction layer called freesync power optimisation. This feature leverages panel VRR to help mclk idle low at the desktop. This was introduced for single display use with RDNA 2, and expanded to dual display along with RDNA3s MALL advancements. I’m not sure if this is expanded further with RDNA 4 but I can try to find out.

This isn’t true for Vega 10 and 20 due to their use of HBM2. In general what you’re describing is a comparative weakness of GDDR as a technology. I don’t think there’s anything to suggest there’s an inherent issue with idle power on older gen asics at >60 Hz save from the typical limitations with VBI compatibility in an array of panels or display bandwidth thresholds. In the case of VBI compact issues, modifying EDIDs can indeed help.