Just tracking trended data in general would be sufficient to defeat a LARGE number of common cheats. One of the very few use cases “AI” might actually work for in a positive way. But that puts the burden on the developers and server hosters, and it’s much easier to just burden the players directly instead.
It’s in the appendices. It tells us the authentic Westron names of all the main Hobbits we follow.
If we wanna be pedantic (and I usually do), Pippin’s Real Name is Razanur.
You seem to be arguing it’s all about the implementation of the phoning home itself- I’m arguing that running the entire executable/binary through a virtual environment likely has far more drastic performance implications than a phone home, regardless of frequency. It probably IS mostly an implementation problem, but I’m more inclined to believe that the implementation of the Denuvo virtual environment is at fault, not just a server call and response delay. **EDIT: Apologies, forgot to include a link- see HERE. Looks like a substantial/measurable difference. Not massive, as measured here, but certainly enough that if your hardware is just barely able to run a game it could easily make or break the entire experience.
Regarding performance implications: I believe Denuvo DRM runs through a type of virtual machine environment. While this theoretically should be relatively transparent, there are definitely documented instances of it negatively impacting performance, sometimes severely. Maybe the VM it runs in is just bad with certain instructions/calls on certain CPU’s or api’s, hard to tell for sure. But it’s not nothing.
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.
Remnant 2. Gotta finish Cyberpunk 2077 (again) first though. The damn DLC adding extra achievements has thrown everything off!
Adding repos can just be done inside a Toolbox, or even as Overlays. Grub can also be edited and changes applied to immutable OS’s like Bazzite/Kinoite. I’d definitely say give it a shot on a non-daily driver machine and see how you like it. Having the option to mess with the underpinnings can be nice- but not having to has a lot of value as well.
I know, right? It’s so hard to “really” mess something up and Toolboxes are very cool for things not served by Flatpaks or Overlays.
Regarding your not wanting to go with an immutable distro: what configs are you thinking you’ll need to mess with that makes an immutable distro a bad idea exactly? I was previously on the fence about it as well but Bazzite has absolutely served my needs and requires way less fiddling than my previous Nobara install did after major updates. I have yet to find any day to day configurations that I haven’t been able to overcome with OSTree overlaying. Aside from being immutable, Bazzite literally checks every other box you’ve got listed.
I believe it’s more a “the PS3 CPU architecture was an absolute nightmare and emulating it is difficult/slow” more than it had anything to do with the graphics rendering portion- which is typically where phones would have made the most substantial advancements. There are specific instruction sets that need to be supported by any CPU emulating PS3 to run anywhere near native speed… And I don’t believe much work has been done for ARM cpu’s to support the needed instructions in mobile devices.
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.
I might recommend fileflows over tdarr- but either way some kind of similar solution is almost mandatory with the grab bag of arbitrary encodings you find out there.
Atomic OS’s (especially Fedora based) with Nvidia are going to be a bit of a pain. Did you follow all the instructions found Here ? I personally gave up on silverblue/kinoite after I tried Bazzite. Similar bases, but the Bazzite devs paid special attention to GPU and accessory drivers/implementations that are otherwise much more painful in Fedora Atomics. You can always do a clean rebase then re-run the steps above (only the OSTree section).
Xbox controllers (Xbox One and newer) have been absolutely solid for me with the xone driver + xpadneo, regardless of distro. Bazzite has everything I need baked in, so it was completely plug and play. Not a very interesting answer, I know. But it still blows me away that it “just works.”
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.
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.