As others have said, it might be the new steam recording feature being a touch buggy still. You could also try running the game through gamescope. I’ve had that resolve weird stuttering when game frame pacing wasn’t matching up with the refresh rate of the monitor or compositor properly.
Epic generally works fine through Heroic launcher. Though I’ve had some occasional problems with Heroic and in those cases Lutris running the Windows Epic Game Store Launcher solved every time. Steam and Proton are still the easiest plug n play though.
I can vouch for Bazzite and always will as long as they keep up the solid work. Running on a laptop (gnome variant for easier fingerprint login) and desktop (KDE, cuz I just prefer KDE day to day). It just works™️.
1000% on the money here. You want encode, decode, calculation, acceleration? They got it. Rock solid, beautiful and simple. You want that shit to actually SHOW UP ON SCREEN? Get the fuck outta here. What do you think nVidia is, a GRAPHICS CARD company!?
Rehabilitated HP z440 workstation, checking in! Popped in a used $20 e5-2620v4 xeon CPU and 64gb of RAM and it sails for my use cases. TrueNAS as the base OS and a TalOS k8’s cluster in a VM to handle apps. Old but gold.
In my experience, Seagate exos are only “loud/clicky” when under HEAVY write loads. Mostly they’re pretty quiet with a very low drone at worst. In any decent case it’ll be pretty negligible. With headphones on doubly so.
Absolutely this. Relatively quick and clean, no messing with installation or reconfiguration. That is, assuming your data isn’t completely corrupted and the old drive doesn’t just outright fail during transfer… But if that happens you were screwed to begin with.
Compatibility is unlikely to be very different. The key is immutability (easy to update, hard to brick your system) and some baked in nice to haves for gaming like some specific drivers/patches and controller support out of the box.
If you’re gaming you might as well just jump on Bazzite if you’re already interested in Kinoite. Very similar base, but Bazzite has some extras Kinoite doesn’t and it makes a transition into an immutable distro easier.
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.
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
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.
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.
The answer is toolbox or similar container systems. It runs a sandboxed version of another OS inside your Bazzite install with minimal performance overhead. Not quite the same thing as virtualization, but thinking in those terms can be helpful for those new to the concept. It won’t let you run and install everything, but it sure will handle a lot!