Remnant 2. Gotta finish Cyberpunk 2077 (again) first though. The damn DLC adding extra achievements has thrown everything off!
Remnant 2. Gotta finish Cyberpunk 2077 (again) first though. The damn DLC adding extra achievements has thrown everything off!
Isn’t AMD’s HEVC/265 still decent, specifically? I feel like I read that somewhere years back. 264 has always been a weak spot for them, however.
Software-wise, it seems that the relatively fast adoption of flatpaks and other containerized formats somewhat solves the typical dependency hell that was so common in Linux just a few years back (and to some extent still is an issue today depending on your distro and use case). The hardware support side is a little harder. That’s going to be up to vendors to play nice with the Kernel team and/or introduce reasonable userland software that doesn’t break the golden rule. Until Linux gets more market share the latter isn’t likely to happen. A nice side benefit of the emergence of immutable and/or atomic distros is that users can play around and try things with much lower risk of bricking their systems, so I’d also consider that a step closer in the “it just works” department.
Very true. But brute force checking through tons of different settings for each camera you need to configure is not fun. I couldn’t seem to find any kind of “known working configs” database or anything either. Every camera seems to be different in what it expects, outputs, authenticates, etc. Once it’s set up, I agree, maintaining the config is easier. Having all your cameras match in model and firmware version probably makes the whole endeavor MUCH easier.
AmCrest and Frigate together are SO good. Integrating Frigate with Home Assistant was also insanely easy for quick viewing and notifications. That initial Frigate config is a bit of a bear- but once you’re past that I cannot speak more highly of it.
hunter2
My friends and I all LOVED the pick-up nature of SG1. We’re all adults with busy lives, so hopping into a ~5 minute casual match was just so easy. And the casual nature made it feel like we could have success without “grinding” the game. I guess that is explicitly not the intent of SG2.
The shift from “we’re making a fun and relatively casual arena shooter with a neat gimmick and extremely rewarding fundamentals” to “we’re making a generic e sport shooter” was swift and, frankly, uncalled for.
Even with nvme drives which supposedly “don’t need” to use BFQ, I STILL always swap it since it maintains responsiveness across the system during heavy IO loads. I used to have similar full system freezes when downloading steam games which notoriously overload your IO in Linux. BFQ was the solution every single time.
Edit Try following the instructions detailed in this post to add a systemd rule to set the scheduler: https://stackoverflow.com/questions/1009577/selecting-a-linux-i-o-scheduler
The second answer that shows an actual rules.d file example has always worked for me. If using nvme or old school spinning rust you’ll need to change it up a bit. Instead of “noop” set it to “BFQ”.
Try swapping to BFQ io scheduler and see if that makes a difference.
Anyone who ritualistically buys Dell. I believe Intel is on the record as having called Dell “the best friend money can buy.”
Are you on Gnome, KDE, or some other desktop environment? I know KDE Wayland and Nvidia do NOT play nice (presently).
Are you running it through Lutris? Steam with Proton? That error seems decidedly like a Wine specific problem, which Proton should have ironed out at this stage for this particular game.
*Unless you’re trying to play on hardware with incomplete Vulkan support. Then it’s a hardware support problem that is unlikely to be fixed in a reasonable timeframe.
I’m going to assume it’s not Universal Blue… But parts of your description reminded me of it.
I have personal experience with BTRFS and Windows. And that experience is that it’s roughly as stable/complete as NTFS is for Linux. 6 of one and a half dozen the other. I can’t recommend either situation for guaranteed stability long term between systems if one really needs to swap between the OS’s frequently while accessing all the same files.
Weird! I’m running Bazzite kde (so fedora based, like Nobara but with different tweaks and it’s atomic), and gamescope gives me zero problems. Might be some weird combination of software versions between gamescope and kde in your system. Or just a general kde config problem. I love kde, but all that customization can absolutely come at the price of stability at times.
Might be worth trying gamescope on another known working game too. Would help narrow down if it’s gamescope itself or the game you’re trying to use it on.
Interesting. I haven’t had any issues with gamescope for a long time… Back when it was new I definitely had issues running things with it… But it’s been a long time since that’s been the case. I can recommend running steam from a terminal and viewing the output after trying to run the game with gamescope. It might point you in the right direction.
Should be something like - “gamescope -W 1920 -H 1080 -f %command%” I will also note that mine tends to crash/not launch if I don’t put Mangohud arguments BEFORE gamescope. The w and h arguments are just width and height resolution, so set those to match your monitor. The “-f” is for full screen.
Possibly dumb question: why not use an Authentik outpost with a reverse proxy to enforce SSO? It wouldn’t be “baked in” so to speak, but it would be fully OIDC and as long as you’re just running it through a web browser. Biggest downside is you’d need 2 logins (one for the outpost and one for the app). I’d assume the sso is specifically for the extra security though, so that shouldn’t be a problem outside of it being a little hassle.