• 0 Posts
  • 23 Comments
Joined 9 months ago
cake
Cake day: October 2nd, 2023

help-circle
  • Um dawg I couldn’t even get into a game with a friend when we tried the other day because of the ‘OnCreateSessionComplete Delegate bWasSuccessful == False’ errors. I’m sure it’ll be fixed in time.

    Very true, I had heard that one popping up but for the live streams I saw it seemed to go away with time or at random.

    Fair enough to temper expectations, it is after all an early access title. They still seem to be handling things better than the ARK devs is all I was getting at. I literally have not been able to play it once, since purchase, outside of joining random public servers and having a uh… “Rust” ^(cough turboracism cough) type of experience if that makes sense.


  • You’d have a point, if the comparison wasn’t between a decade plus old game and one that released in the last week, as early access. ARK is genuinely one of the single worst experiences to try and get into, and has multi year long bugs that haven’t been touched.

    I haven’t bought Palworld, but you can actually launch the game, and join your friends in a few minutes tops. I have attempted to play with friends on ARK. Repeatedly. I have yet to actually do so, even after self hosting my own server on a couple occasions. IMO, this makes ARK as a title and game to play, completely worthless.







  • I can promise the number of people backing up their Xbox/SNES/Sony/whatever games at the time/era of release, are a rounding error number of people who purchased at all. And even if that was the case, how are you gonna do that for the discs that have DRM? Obviously it can be cracked, but how does that help you in that specific time of need (referencing the house fire), when the tech to crack that DRM didn’t even exist?

    Nobody is arguing with “physical copies have better security” (digital storefronts closing, keys being revoked, etc), they’re only arguing with you for pretending everyone is seemingly clairvoyant, with pools of money and compute hardware, to make backups of these things. There is no way you can possibly think that all one needed to do was “copy da files dumbass” when even the hardware to do that, didn’t exist (for the public or at all), or was itself prohibitevly expensive.




  • Not that you didn’t make the right call, but many of the longer software update “confirmations” (obviously they’re only worth something if they commit to that) happened around that time. Almost any android phone didn’t have more than a couple years of support, until very recently. Naturally, no brand is going to backtrack that far, especially for a completely new phone concept that they knew was going to have issues.

    Something can be said about that on its own, but first gen devices always carry first gen issues, and the news (both people and articles) of the time was very vocal about such. Personally I’m on the side of providing long software support, but not extending to hardware (in niche cases).


  • Worse, if power goes out, you can’t use solar to stay electrified because electricity would leak out and potentially electrocute nearby line men.

    Has this… really ever been true? We’ve had gas powered generators people can plug into their homes for a rather long time now, and they would be doing the exact same thing as solar installations.

    It depends on where you are mainly, but I do believe the kit that prevents what you describe, is functionally mandatory to have for solar. Not certain on that, and it definitely still depends on locale, but I haven’t seen any without that lockout in a loooonging time.





  • But the problem is not AOSP, but Google? This reference and forking could be done to any code or math out there, why is it somehow “not ok” only when AOSP comes into play? I personally cannot think of anything that would be a specific halting factor exclusively because it’s AOSP. If your issue is with Google, then find a trustworthy fork that you like. You definitely ain’t alone in hating Google, especially compared to the people developing these alternate OS’s.

    All that to say, why are you “flipping it on me” to “prove they no longer pull code from AOSP”, when that wasn’t even the target to hit, or the question.

    If your issue is with Google, take issue with Google. Likewise, if your issue is somehow “literally everything Google has ever touched, even if they have no part in it today, or ever again.” Then I got nothing. If you’re that horny on main to burn Google to the ground, start writing your own mobile phone OS I guess, I simply don’t see any other way you’re going to hit that mark.





  • And the people driving them are still learning the quirks for specific circumstances. Many drivers know you need to let a fuel car warm up more or to give it extra gas in XYZ scenario, but those same people won’t always know what to do when switching to electric. Or they might instead do something that helped on a fuel vehicle, but actively harms on an electric, especially with the many manufacturer specific options that have no consistent naming. Hopefully we get some naming consistency soon, if for nothing else than ease of use.