Source-1-Games VS mpv

You shouldn't need to mess with selinux.. Check if your issue is mentioned here otherwise create a ticket: https://github.com/ValveSoftware/Source-1-Games/issues

Found a Github post from 2016 that mentions the issue exists in other Source games as well, including Apex Legends and Team Fortress 2.

Sadly an old known Valve issue. https://github.com/ValveSoftware/Source-1-Games/issues/3729

At first, I thought the CPU was overheating, and thus turning itself off, alongside the graphics card (intel HD 4000), so I went ahead and cleaned it. it was filthy. because of that I was optimistic that I've solved the problem, but, nah, it still happens, even though the laptop isn't even hot at all. I've found nothing about It online, besides a somewhat similar problem to mine from 10 years ago, found here: https://github.com/ValveSoftware/Source-1-Games/issues/1943

oh and something else, on linux if you are using wayland and nvidia tf2 just wont work. https://github.com/ValveSoftware/Source-1-Games/issues/4553 i will not stay with old and insecure protocols like X, so much caveats with this game, so much problems just let it die...

https://mpv.io/ has yt-dlp support, if yt-dlp is installed you just need to throw the URL at it and it plays the video (without download).

See https://github.com/mpv-player/mpv/issues/9053

I apologise for not following procedure. I am in the middle of building mpv 0.37 from source. Irrespective of the outcome I will document what I had to do in addition to the instructions on mpv.io and if the problem perststs, where it happens and where not with kernel version, mpv version taken from the screen, and the terminal output.

Use MPV. Partticularily shinchiro's builds. Extract the folder where you want its installation directory to be, if you decide to install it. Otherwise, just drag and drop files on top of its window or executable.

Author of ripgrep here.

Like automatic encoding detection and transparently searching UTF-16?

Or simple ways for composing character classes, e.g., `[\pL&&\p{Greek}]` for all codepoints in the Greek script that are letters. Another favorite of mine is `\P{ascii}`, which will search for any codepoint that isn't in the ASCII subset.

Or more sophisticated filtering features that let you automatically respect things like gitignore rules.

Those are all things that ripgrep does that grep does not. So I do not favor this explanation personally.

ripgrep has just about all of the functionality that GNU grep does. I would say the two biggest missing pieces at this point are:

* POSIX locale support. (But this might be a feature[1].)

* Support for "basic" regexes or some equivalent that flips the escaping rules around. i.e., You need to write `\+` to match 1 or more things, where as `+` will just match `+ literally.

Otherwise, ripgrep has unfortunately grown just about as many flags as GNU grep.

[1]: https://github.com/mpv-player/mpv/commit/1e70e82baa9193f6f02...

- https://github.com/mpv-player/mpv/issues/8692

https://mpv.io played it without fuss.