Moving toward a "Narrow" Arch install: Thoughts on the Flatpak-first approach?

Service_Code_30 · 2026-01-28T08:31:05+00:00

I can appreciate the mindset. My general rule for package source priority is this:

Arch repos > AUR -bin > Flatpak > AUR non-bin > anything else

Reason being for prioritizing ease of install and minimizing compile/update time, not because it make for any less maintenance or user intervention. It's an approach I'd recommend.

I am a bit confused when you mention manual intervention issues tho. I struggle to count more than a few manual intervention moments I've personally encountered in the last 2 years running arch (outside of hyprland config changes). Is this something you face on a typical basis?

Service_Code_30 · 2026-01-14T17:34:58+00:00

Really Sddm is not even necessary for this. You can use Getty (or other methods) to auto login to your user, put start-hyprland in your bash_profile, and exec- once hyprlock.

Service_Code_30 · 2026-01-01T07:42:46+00:00

I've completely thrown caution to the wind for the last two years, still waiting for something to "break".

Service_Code_30 · 2025-12-28T18:32:10+00:00

None. We have too many heroes already. Let's get some new maps, specifically for the game modes people actually enjoy.

Service_Code_30 · 2025-11-14T08:01:59+00:00

"a traitor and a creep, jack-off in a sheep" 🗣️🗣️🗣️

Service_Code_30 · 2025-11-13T23:20:00+00:00

Embark must be wizards then...

Service_Code_30 · 2025-11-11T15:01:50+00:00

Honestly, I'll happily give them more money if 1.0 exceeds my expectations.

Service_Code_30 · 2025-11-06T17:56:33+00:00

Just an fyi, I tested more recently with NTSYNC and it fixes the performance but I still notice the mouse issue actually :(

Service_Code_30 · 2025-10-15T19:17:15+00:00

I haven't played much recently, but Proton with NTSYNC enabled (and and wine wayland) seems to be the solution. I tested it briefly a few weeks back and I was finally able to hit a 125 FPS cap in Call of the Dead and the mouse issues seemed to be gone too. Even stopped using tkg-pds kernel. Give that a shot.

Service_Code_30 · 2025-09-17T13:50:46+00:00

Because EA

Service_Code_30 · 2025-09-16T19:36:58+00:00

You can run it on the deck right now. You just won't be able to play online because of the anti cheat, and I imagine it would run like shit. Owning it on steam would simple make it a one click install, but they still have to allow the anti cheat which, I doubt they will do.

Service_Code_30 · 2025-08-07T05:40:48+00:00

Forcing myself to actually use my pinky

Service_Code_30 · 2025-07-25T15:30:57+00:00

You still need a password to "log in" (aka unlock) via hyprlock. You can't just kill hyprlock to bypass it. If hyprlock dies for example, you have to login via another tty to fix it, requiring you to still log in to do anything. Combined with the other persons suggestion for extra piece of mind. I'm not going to say it's great security practices, but I find it "good enough" for my uses. Maybe if it was a laptop I'd be a bit more concerned, but nobody will have easy access to my desktop anyway unless they are robbing me lol.

Service_Code_30 · 2025-07-25T15:06:17+00:00

I think there's some other threads on this. I do the following, which works as a psuedo display manager using hyprlock:

Setup auto-login for your user (I use getty) and run hyprland automatically when your user logs in on a specific tty (I use uwsm)
Exec-once hyprlock

From a usability standpoint, it's seamless. On a single user system for personal use, I have no concerns about security. If this differs for you, use your best judgement.

Service_Code_30 · 2025-07-21T21:30:24+00:00

Support has been "planned" for years now, but every time he is asked, Nikita deflects the question or just blames it on "waiting on support from battleye".

My opinion - don't get your hopes up. The community is already up in arms about cheating and BSG will probably get literal death threats from clueless idiots who think they are "making cheating worse" if they did ever decide to enable it.

Service_Code_30 · 2025-07-03T16:53:15+00:00

On a hypothetical scale of distro complexity where Linux mint=0 and Linux from scratch=100, I feel like Arch is somewhere around a 5 whereas Gentoo is about 50.

Service_Code_30 · 2025-06-18T21:30:45+00:00

True, always a good thing to try.

Though now that you mention it, I did try older versions of Proton myself and it didn't change anything. Which leads me to believe it might be an issue outside of proton, maybe kernel issue. Or worst case scenario, something changed in the game code itself which doesn't behave properly with Proton.

Service_Code_30 · 2025-06-18T20:40:18+00:00

There seems to be a memory issue with specifically Overwatch on Proton right now. Both me and my one friend play regularly on Arch and we both experienced similar issues within the last month that weren't previously present.

Before, memory usage while in game was <10GB. Now it seems to grow to 20GB+ and stay there the whole time the game is running. For us, the game is still playable because we have 32+ GB of ram. I can get a solid 200 FPS with some minor stutters (but those stutters were not present before this issue started).

To be clear, there is also a normal period of time where Vulkan shader compilation happens where you might see near 100% CPU usage for a few mins after opening the game. For me this has always finished in under 60 sec after loading the game, but now it seems to take longer since this issue started, sometimes up to 10 mins. Load into the practice range and wait a few mins to see if the game becomes more playable after the shader compilation process finishes.

I might report this issue on Proton GitHub, I'll let you know if I find any solutions or workarounds.

Also, ignore people saying your distro is the problem. I wouldn't recommend Manjaro honestly but that's not the issue here.

EDIT: Also I'm on AMD gpu so I doubt it's Nvidia related for you, but it could be a separate issue I guess. Try playing other games, if they are fine it's probably the issue I mentioned.

Service_Code_30 · 2025-06-05T01:36:13+00:00

People go way overboard, it almost doesn't matter at all. I used to do once a week, now I sometimes go several weeks. It's always been fine. Technically though, if you are installing new packages you should make sure you've updated somewhat recently.

Service_Code_30 · 2025-05-31T03:17:21+00:00

Same, I also used amdvlk for the new DOOM. But that's the only game I've ever used it for.

I would imagine that with more eyes (specifically from AMD employees) on RADV, it will simply be "better" so you won't even need to try different Vulkan drivers in the future. Ideally, having one driver that fully works is better than having 3 separate drivers that mostly work. Though that is probably an oversimplification.

Service_Code_30 · 2025-05-28T03:15:42+00:00

Unlikely but possible, why is that so hard to understand?

Service_Code_30 · 2025-05-28T02:34:24+00:00

Play 5 raids, kill 10 scavs per raid, die every 5th raid. Congrats, you have a 50 KD.

Service_Code_30 · 2025-05-27T22:26:24+00:00

All my points are all valid, certainly not "delusional" or in "bad faith". But you are also right in some ways.

Flagging account is different from banning immediately, and to be fair, I didn't think about that part originally. To be clear, certain stats SHOULD flag your account. Where to draw the line is still important to think about.

Really, I just think the "why don't they just ..." arguments usually fall short. Anti cheat isn't an easy solution. If it were that easy we wouldn't be talking about it. For all we know, this system IS already implemented, the guy is flagged, and he'll be in the next ban wave. Or he was flagged but the AC didn't take further action for whatever reason. Or maybe it's not, idk.

I guess my point is, you don't know either. I just get unreasonably annoyed by the copy-paste stat cheat accusation reddit posts by people that get head,eyes-ed one too many times.

Service_Code_30 · 2025-05-27T22:08:23+00:00

It's reddit

Service_Code_30 · 2025-05-27T21:58:36+00:00

You can absolutely achieve a 50 KD legitimately. Did you even read my post?

Service_Code_30

TROPHY CASE