Depending on how you make the game some launchers can make sense. You can set display options before launching the game. Back in ye olden times some games would launch by default in a set resolution which often made changing that in-game difficult as it would be off screen. Also makes your first time launching it a better experience than some low-res garbage. Also, without a platform like steam they can handle updates.
That being said, I don't think most modern games need those functions. Graphics engines are pretty good at getting screen resolution from your os (not perfect). And platforms handle patches and updates.
Now they're mostly there to gather metrics and shove ads in your face, and enforce drm.
Set up syncthing on your phone and whatever other device (laptop/pc/another phone at home/etc). Point it to your photos/videos folder and sync to your device at home(or friend's house). If your phone is confiscated and they manage to get it deleted from the cloud, you'll have a copy on your device. Make sure you enable settings like trashcan or versioning so the files deleted on your phone aren't auto deleted on the device.
You interested in home improvement? Buy the shitty flat, slowly fix it up the way you like, and if you ever decide to sell, it'll likely be worth a little more.
These two were the top two favs of my wife and I last year. Played it takes two on our steam decks, and split fiction on our PCs. One of them is older and handled it great. Both pcs run linux.
Bluetooth es muy bueno o malo con Linux. Depende con que tarjeta tiene. Probablemente esta usando la en su mobo. Muchas tienen esta problema. Usualmente compran una USB bluetooth dongle barata de amazon que dica que sierva con linux.
No es algo incorrecte con bazzite, son las drivers en la kernel. Si fue otro linux pudiera tratar a ambiarlas, pero no con bazzite.
perdona mi espanol basura. Me han pasado viente anos desde fue bueno.
Fixed it on one buddie's computer, he installed the snap version. We fixed it by removing that one and installing Steam via apt. Which version do you have?
I will admit to enjoying splatting zombies as I drive through them. If they brought the parquor/fighting challenges back, I'd probably seek out the driving/splatting challenge.
I agree with the truck mechanic. The map would have been too big without them. I also would have been cool with a fast travel mechanic from one unlocked safe zone to another.
My biggest complaint was arrow retrieval. It's not just me, but it's either bugged or only working worse than DL1. Arrow retrieval for me is 1 in 20. I loved DL1 bow/arrows. I'd run around and gather a big group, jump up somewhere high and rain down headshots, and retrieve most if my spent arrows.
Yep, I think the only thing github actions has over jenkins is built in versioning. I wish in jenkins I could edit a pipeline and easily roll it back. Or even better have tags so if I break something the team can just use the previous tag while I figure it out.
You can install the github actions runner locally and use it, however all that does is eat your cpu cycles and prevent them from charging you. It doesn't help you debug that blackbox at all.
Not saying it's perfect, but every job I've been at they're migrating away from Jenkins. And they never have a reason to do so other than shiny new toy. Jenkins has it's own problems, but I personally think it's litterally decades ahead of github actions.
I do like runners better than the default jenkins run baremetal on the server, however the runners are too blackbox. I wish there was a debug toggle on runners. Pause at step, then provide a console into the runner. Some runs litterally take hours, so adding some debug output, and rerunning makes troubleshooting tedious.
Huh, I was expecting more. There's so much to hate with github actions!
Sometimes you can pass a list, or boolean, but for composite actions you can only pass strings.
Open bugs that github actions just doesn't care to fix (I've run across about 3). Most recently, concurrency flag cancel_in_progress doesn't work, and they aren't fixing it.
variables often not accessable until next step.
API is slow to update. Running jobs querying themselves won't see themselves as running 50% of the time
Inability to easily pass vars from one job to another. (output in step, output from job, needs, call) it's 4 lines of code to get a single var accessable in another job.
UI doesn't show startup errors. Depending on the error if you make a dumb syntax error in the workflow file, the UI will just say failed to startup. Won't tell you what happened, won't even link it to your PR which kicked it off, you have to go hunting for it.
Workflow Dispatch is a joke. Can't run it in a branch, no dynamic inputs, no banners.
Can't run schedules in branches.
Inconsistent Event Data labels and locations across triggers. Want to get the head sha? It's in a different place for each trigger, same for so many things.
Merge Queues have the worst Event Data. They run off a autogenerated branch, and so they fill everything in with actor=mergequeuebot and garbage that is unhelpful. Good luck trying to get the head sha and look up the real info like say the branch name you're merging in. You have to parse it out from a head_ref's description or some junk.
No dynamic run names. Well, you can, but you have to call the api and update it. It's a hassle. Why not just let me toss in an @actor, or @branch in the run name? That way when a dev is looking for their instance of "Build Job" from a massive list, they can actually find theirs.
garbage documentation
I could go on. I do CI/CD for work and gha is the tool they are having us use. I have no say in the matter.
If he didn't read your message, he likely didn't read messages from others. If his account is gone, it sounds like he deleted it like so many people are getting fed up with social media.
Just search the model#, amazon and others will pop up.