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.
Alright, where's my replacement once my current Fitbit dies? What company makes a watch that tracks steps, heart rate, sleep, spO2, notifications, is generally water resistant (light swimming) and has a battery that lasts ~5+ days? Bonus points for open firmware/hardware that doesn't require me to design my own apps/systems for each of those items. I don't even use most of what my Versa 3 can do, but I know it won't last forever and I'd at least like an idea of where to go if/when it breaks down.
No stuttering for me on Linux... Runs as good as it ever has but the visuals are even that much better due to the engine upgrades. Not a fan of the new UI, but the old UI was clunky too, so I can't really say it's even a step backwards.
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.
On windows the article mentioned being a microcode patch via Windows update. Linux would be similar- but via a kernel update most likely. I'd assume that a general BIOS update would also do the trick, but then you're relying on motherboard vendors and it's unlikely many would provide such an update to older hardware, even if it's still widely used.
I've had good luck with AsRock as well. Before this most recent generation I was Sapphire all the way. But they charge a good premium now that I don't feel is worthwhile if you're in the ~7600xt range or lower.
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.
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".
He retains the "Cold Take" name and property- so here's hoping he continues it, whether that's under some new media company or even just as a solo content creator.
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.
Ooooh okay. Yeah, I avoided the playstore version. I'm pretty sure I had read somewhere early on that the Playstore version would lack features or otherwise be behind in some ways due to complying with certain Google specific requirements to be allowed on the storefront. Kind of like KDEConnect.
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.