draecas

Rapidly swapping loadouts apparently could crash lobbies, sending everyone back to orbit.

The & is the html escape code for an ampersand (&) symbol, which is used to separate query params in a url -- it appears like this has been re-encoded so the single & in the URL becomes & by something breaking the link. If you change all of the &s to $ it works. it's not really an "amp" link in the "Google Amp" meaning.

Also after posting this comment, it appears to be Lenny's url encoding, I think I've fixed it but if not, remove the amp; from the 3 sections of the url you see it and it'll work

Sure, they obviously are dropping the ball here, just trying to explain what they might mean by "thoroughly tested" and why it's not succeeding

This is all assumption from me, but I think a lot of testing would likely be diagnostic machines and specialized testing -- not actually playing games. I would assume it's something like plugging in, confirming the parts all meet spec after whatever the refurb is. That spec is probably more around frequencies, power use, temperatures.

Obviously that's not good enough if they're sending out these clearly broken refurbs.

Maybe, but unless we're in there, it's hard to say for sure. Battleye supports it but given the clusterfuck that is the Tiger engine, they might be using an old or heavily modified version. Especially given how easily cheaters are getting past it atm, I would not assume they're keeping up to date on it without some evidence.

Stadia limits the player's control of the system substantially and might not have even needed the anticheat, or the same anticheat, given it's closer to a console in terms of user's ability to run programs alongside the game to modify memory.

The Deck is designed for SteamOS and SteamOS is pretty much designed for the Deck. They're chocolate and peanut butter.

I feel Valve's Windows support is not great -- it's a custom APU for them so you're getting your drivers through Valve, not directly from AMD's Adrenalin. The APU drivers are from March, I'm not sure if we've seen any Linux improvements since then on the APU side but months without GPU driver updates to address game compat issues doesn't encourage me.

They don't officially support dual booting AFAICT, and given the size of modern games + Windows, I wouldn't want to dual boot on any of the offered SSDs tbh.

If you've got a deck and really want a Windows-only game, it works. But given the easy availability of the Ally, and the upcoming non-extreme Ally, I can't imagine recommending anyone who wants to primarily play a Windows-only game get a Deck.

I've done it so it's definitely possible, though I can't remember if I used Steam link or Moonlight to do it. It was also pre-Lightfall, so they definitely could've changed it.

estiny has some anti-overlay stuff enabled that limits what can pop up on top of it, which might also be affecting some form of streaming?

Unless something has changed very recently, Destiny 2 does not work under Proton because the Anti-cheat isn't compatible. Windows is an option, but I'd really recommend a dedicated Windows handheld for that instead of the Deck.

I haven't tried Windows on the Deck itself, but based on 6800u performance, you're looking at maybe getting a solid 30fps on lowest settings. Destiny 2 is not a very well optimized game atm, and even the Ally at 20w can have trouble holding good performance in Neomuna or the Tower.

All just my opinion/feelings on this shit.

The problems have been building since last year. Plunder and Seraph were less stable and more buggy. Plunder was kinda panned as a bad season by some, but between a Showcase promising us features we'd been wanting for years (in-game Loadouts, in-game LFG, a renewed focus on the ritual playlists, probably more I'm forgetting) and Seraph's awesome story and (imo) fun missions, some hype came back for a lot of us.

Lightfall itself was a mixed bag, but they eventually made progress on the stability issues (credit where it's due, shit is a lot more stable for me). It had story issues, but they weren't WORSE than previous story issues imo, just a regression. It wasn't a GREAT place, but if they fixed stability it would be ok.

Then the SotG comes out, which says (loosely translated) "Stop asking us to make more PVP/Gambit maps, we're never gonna do it like you want because it wouldn't make us enough money. Also no more free armor, because y'all didn't appreciate our basic ass armor sets as much as the ones that make you into a fucking t-rex, just pay up piggies"

If they had not said anything, it would've been better than posting a "We, a company purchased for billions of dollars, can't do the #1 thing our fanbase is asking for because it wouldn't make us enough money".

There is some good news in there, I guess. Favoriting shaders is the kinda basic QoL stuff we should've seen years ago when they redid shaders, but better late than never.

The obvious:

1. Stop airing a single women's match every show. IMO the TV titles show be getting defended every other week each, and it shouldn't count as the women's match when the TBS champ has a match.
2. Give them more build than one woman giving an interview and another showing up to randomly challenge her. The slowest improvement on the planet here.
3. Don't stall 1 of the 2 belts for a year waiting for a single person to come back from injury, no matter how good she is.

The more controversial:

1. Firm up some larger factions and brew up a big ol faction war. It's a great way to restart/kickstart the division imo, since so much is completely uninvolved. TFM TK keeps toying with something like this and then chickening out
2. Push this into giving the women one of the marquee matches, Blood n Guts or Anarchy in the Arena or Casino Battle Royale or something that gets the big name on the posters and all the photo slots. Actually let them headline some shit
3. Don't bother with any more belts atm, there's already 2 we rarely see.

As long as tools to unclip the shell aren't consider specialized, I think almost all existing handhelds are gonna meet the actual requirements here - they just have to be user replaceable, not use swappable, without the use of specialized tools or thermal energy. If you can unscrew it, disconnect the old battery and connect the new one, it complies. It's really only an issue in waterproof devices, where they have to glue everything to seal it.

Imagine you have a household with 2 adults and 2 kids, and you've setup some level of presence tracking. You want to use automations to turn off everything if nobody is home, turn on some things if only kids are home, turn on other things if only adults are home, and turn on everything if kids and adults are home. You could build this logic into every automation you have, but it's a lot of repeated logic to put in every time you wanna add something cool.

Blueprints mean you don't have to write it out in every automation. But I've never found them to be especially convenient for updating. And they still have the automation doing all of the heavy lifting.

You could have a home State sensor that you depend on automations to manually update. But this is only as up to date as you make it, either running every so often (stale data) or using automations based on a change in presence tracking to update a sensor (buggy maybe? have not tried it but sounds prone to race conditions and misfires to me). Closer, but unideal IMO.

Or you could pull this logic into a service that returns 1 of 4 possible states - full, empty, kids, adults. Your automation no longer has any logic to figure out what the state is or who's home, it just asks what set of rules are in effect and can apply them. This lets the automation focus on a smaller area, which means less shit that needs updating if you change something, less chance for bugs.

There's not a ton new you can do now that you couldn't accomplish before, but you can do it in smarter, more maintainable ways.