Anyone else having issues with Apex Legends the last few weeks?

Apex has been running smooth as butter (well, as smooth as apex can run :) ) for the last year or so on my PopOS machine. I haven’t had to log into windows to game in about 18 months.

I noticed a few months ago that I would get errors / crashes, seeimingly randomly where ‘pak’ files wouldn’t load. I’d get a wine-looking pop up with the message. I could fix it by Validating Game Files. Inevitably it would find corrupt or invalid files and redownload them and it would work again.

Something happened about ~4 weeks ago where it became much more frequent to the point where its now unplayable on PopOS.

I’ve done everything I can think of:

completely removed steam and all my games from my system and retried with the deb package in the store. (no luck)
completely removed that and my games and tried with the flatpak (same issues)
I even, thinking my ssd might be failing, bought a new one, cloned my stuff over to that, etc (no luck, same issues).
I just uninstalled the game again and am trying to redownload as I am typing this and it gets to the end, fails (corrupt update files), then puts me in a loop of validating, downloading, pausing download, etc.

All of my other games seem to work fine and update fine.

Apex works on my steamdeck. Apex works fine on this same machine on Windows 10.

I used inotify-tools to see if something was editing the files in between gaming sessions when it worked and when it didn’t and nothing seems to be accessing let alone updating/writing to those files. So the corruption or whatever happens during use.

I have tried Proton experimental and literally every version back until it wouldn’t even make sense to run. I tried the last 5 or so ProtonGE versions as well.

The thing is: Is this a Pop issue? Is it an Apex issues? Is it a proton issue? Is it a steam issue?

I don’t even know where to post this ‘issue’ too.

For what its worth, I am happy to try and run this down and provide whatever logs may help. I could learn some auditd!

HALP!

Community Rules

Follow the Code of Conduct

All posts on pop_os must adhere to the Pop!_OS community Code of Conduct. https://github.com/pop-os/code-of-conduct

Be helpful

Posts to pop_os must be helpful. When responding to a user asking for help, do not provide tongue-in-cheek responses like “RTM” or links to LMGTFY. Linking to direct sources that answer the asker’s question is fine, but it’s advised to provide some explanation as to how you got to that source.

Critique should be constructive

We within the Pop!_OS community welcome helpful criticism or ideas on ways to improve. However, basic “It’s bad” or other simple negative comments don’t help anyone fix anything. When voicing a complaint about something, try to point out ways the complaint could be improved or worked around, so that we can make a better product for it.

This rule applies to both Pop!_OS and its projects as well as other products available from third-parties.

Don’t post malicious “advice”

It can be funny to joke about malicious commands, however this is not the venue for it. Do not advise users to run commands which will lock up their systems, steal their data, or erase their drive. Examples of this include (but are not limited to) fork bombs, rm, etc.

Posts violating this rule will be removed, even if the post is clearly in jest. Repeated offences may lead to a ban. You may understand that the command isn’t serious, but a new user might not.

No personal attacks

Posts making a personal attack on any user will not be tolerated.

No hate speech

Hate speech of any kind will not be tolerated. Any violations will be removed, and are grounds for a ban.