

Ah, I’m not sure how well that’d work via yuzu and ryujinx forks. Perhaps if the executable is added through the steam client so you could delegate the functionality via steam input? Sounds messy as heck though.
grow a plant, hug your dog, lift heavy, eat healthy, be a nerd, play a game and help each other out
Ah, I’m not sure how well that’d work via yuzu and ryujinx forks. Perhaps if the executable is added through the steam client so you could delegate the functionality via steam input? Sounds messy as heck though.
If you don’t use them to relax your grip in specific types of games (delegating common functions to them and away from thumbs) you might like to use them for DVR capability like instant replay?
If your controller has a gyroscope, you may use them to toggle engagement? Gyro aim can be surprisingly effective once you’re accustomed to it.
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
As some commentators have mentioned, that was mostly fine at the time of Ellesmere (2016ish?) where games wouldn’t so frequently shoot past that limit. In today’s environment, we find that a much higher proportion of games will want more than 8 GiB of VRAM, even at lower resolutions.
Notably, the most recent predecessor in this sort of segment (RX 7600 series) used the XT suffix to denote a different SKU to customers, though it’s worth mentioning that the XT was introduced quite a bit later in the RDNA3 product cycle.
I can agree that the tweet was completely unnecessary, and the naming is extremely unfair given both variants have the exact same brand name. Even their direct predecessor does not do this.
The statement that AMD could easily sell the 16 GiB variant for 50 dollars less and that $300 gives “plenty of room” is wildly misleading, and from that I can tell they’ve not factored in BOM at all.
They blanketly state that GDDR6 is cheap and I’m not sure how they figure.
didn’t realise people were calling the next witcher game woke because of this, but it’s 2025 and there’s no bar too low.
detractors probably never realised you could play parts of TW3 as Ciri because of skill issue
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.
yeah at this point it’s just skill issue
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.
good to know it can work!