mox

Rather than guessing at whether it's swapping, why not check your swap usage? Running free -h in a shell will give you a brief overview of memory usage. Various GUI system monitors will graph it.

You can also find out what process is hitting your storage so hard with a tool like iotop.

Can you save replay videos yet? Overwatch 2 broke it, but I haven't gone back to check recently.

Why?

[email protected]

Do note that if you intend to use Debian for gaming, you'll probably want to enable Backports for access to newer kernel and firmware packages.

What fascists are ruining OSS?

Their metric for "older" is two years or more.

Glad you got it working!

BTW, in case you're not aware of it, you might find the shellcheck command useful when writing scripts.

I can't tell from that error message whether the inner quotes are being discarded when the command is run, or just hidden when the error message is displayed.

Too bad it doesn't tell you what part of the command is causing the syntax error. Have you checked for more info in the output of journalctl --boot _UID=1000? (Assuming your user id is 1000 and you use systemd.)

Re-reading the spec page that I linked above, I see reference to both a general escape rule and a quoting rule. That could be complicating things with the quotes and backslashes, and maybe even the dollar signs and semicolons, which apparently are reserved. In case it helps, I don't think those semicolons are needed at all.

Before diving deeper into escaping rules, though, I would consider whether it's time to move the whole command line into a script, and simply pass %f to the script in your Exec= line. That would avoid the need for nested escaping/quoting, and allow you to write debug information to a temporary file when the script runs.

You're using single quotes in your Exec lines, which is not legal .desktop file syntax.

I suggest replacing your single quotes with double quotes, and replacing your double quotes with backslash-escaped double quotes.

https://web.archive.org/web/20241130225327/https://specifications.freedesktop.org/desktop-entry-spec/latest/exec-variables.html

TIL 7 is a "massive amount".

Good point. I forgot about that possibility because I don't spend much time playing in Open mode.

The same thing tends to happen on stronghold carriers in Solo mode, I suspect because Frontier programmed the game to spawn a bunch of NPC ships eager to dock with those carriers when a mini-instance is created. You can be the only player within light years, and still have to wait several minutes for all those NPCs to leave before you can dock.

*facepalm*