Lisias

"Please re-image your device."

And the unavoidable conclusion for the problem is... "Please attempt re-imaging your Steam Deck". They didn't even cared about getting some logs before the reimaging so someone could try to identify exactly what gone wrong, they just plain don't care. They have a latent point of failure in their Stack and they don't care, so they will keep building more software, stacking it over the latent failures while introducing new ones and making things worse and worse until they condemn the product. The future for SteamOS is not bright - not because they didn't fixed my rig, but because they just didn't care to even try to understand what happened, what means that this bug will persist forever - or until something else kills the Product for good. And what I'm expected to do? To behave like a Sheep and allow these guys to keep selling me goods that will be encrapified in a couple years due reasons no one have the slightest idea why (or they know and are hiding). And exactly how they expect me to buy the next generation? (sigh) So be it. Apparently it's up to me do at least try to understand what happened and then alert other people - at the same time exposing VALVe's (lack of) support. https://steamcommunity.com/app/1675200/eventcomments/597396873172542241/?ctp=3#c509577661714011958

From the first Amiga Mod I ever heard to... "Robot Band Plays 'Axel F'". Cutie.

Yes. A couple hours ago, on the (current) default theme, the KSP was missing and the text "Kerbal Space Program Forum" was being shown instead. Since this is fixed now, it's obvious that they are trying to "normalize" the asset's location so they could migrate the Forum into Invision's servers - where almost surely everything should follows some guidelines or it will just not work. Assuming, of course, that we are not there yet (I'm not checking anything this week - Murphy attacked on DayJob©) and this happened exactly due that. Software is essentially a Castle of Cards, all it's needed for everything falling down spectacularly is removing a single one of that cards - all we can do is to try to code really sturdy cards as we are near the Castle's foundations, but they will still be cards, sturdy or not. ---- POST EDIT ---- Nope, we aren't there yet. We are still using an AWS IP, the same one since January 24th when Forum came back from the darkness.

Someone recreated the 78' BattleStar Galactica "CGI" using (almost) the same hardware!

And I will probably do it for a long time. Steam's Support is stalling me - no way a Support ticket about updating the Deck could be misunderstood as a connection problem while playing games. That, or whatever is the automated sorting mechanism they are using is a complete crap, because - DAMN - no one cares to read the data on the Ticket anymore? Really, I'm concluding that VALVe fired some people they shouldn't in the last spending cut (and not only on R&D). DAMN.

One bingo is an accident, two a coincidence. Three bingos is a conspiration!!! It's some tome since I don't see @Spaceman.Spiff around here. Ping?

No, you are not. It's something on newer KSPs that need to be worked around. Can you reproduce the problem, then quit KSP, then send me KSP.log, Player.log and the craft file you used? If you have a github account, you can used this issue: https://github.com/net-lisias-ksp/BonVoyage/issues/5

Oukey, LEGO may not be the most popular toy around here nowadays but this video is pretty good!!

It can try...

I second that. In the end, it boils down to Pain Management. Where you are willing to take the pain and for how long. Doing things in house usually is a frequent source of small and quick pains, while relying on 3rd parties where you are merely just one small part of the their incoming will most of the time give you very rare but really huge [and long standing] pains, one of them will eventually kill you. --- POST EDIT ---

I don't know about where you live, but here we have the option to pay insurance for our Credit Card transactions. If something goes wrong, the Bank will take the hit for you. It's kinda cheap, about the equivalent of 3 USD a month per CC (even taking in account the exchange for a weak local currency), but there're caveats - there're some rules you need to follow to avoid losing the "premium". The very interesting bit is that since I decided to pay for this thing, I was never scammed again - they have a pretty effective algorithm to detect smelly transcations, and when in doubt, they enter in contact somehow asking if the transaction is legit. Never lost a penny since then. One would argue that this kind of security should be standard for every CC, as every legislation I'm aware of make clear the CC operator is responsible to keep things secure but... Since the day that I could had been scammed by 1.5 times my monthly income (gross), I gave up fighting this fight and I'm paying insurance for my CCs (I have one for local transactions, and other exclusive for international ones - this makes things way easier to follow up).

UUUhhhh... We have a bingo..... I was wondering... Would @Caerfinon be on the house?

If the data I got from the last borkage worths something, it's a hell of a closet inside an AWS datacenter!

I'm complaining about the Steam Deck updates for months. VALVe botched something very serious, and this is starting to screw more people besides me. Well... Apparently, we have more than one problem to cope with and, obviously, my cheeks was bitten by all of them. But I least I solved one of the problems. It's related to BTRFS and how as time goes by your real available space can be way less than the used volume space subtracted from the volume size - something due fragmentation of the chucks used to store the files. So a process relying on the intuitive process of total - used will eventually think there's way more space available then it really are, and then this process will die due out of space. Balancing the free space using a special command defrags the chunks and reclaim the space back, solving the problem. But... Since the damned update process is 100% opaque, I never knew exactly why the Updating process was dying in the middle of the process until I had a hunch, balanced my volume and now the Updating finishes successfully - or near it, becasue now when it reaches 100%, the word "Checking" is printed on the screen and then a Error Message saying the update had failed is shown. (sigh) But at least now the process finishes, instead of hanging forever forcing me to reboot the rig. If at least the updating process would be being logged, so we can audit it and see what's happening, not? At least the disk space program I would had solved two months ago. What leads to the rant of the semester: why in freaking hell companies go to the extra mile to make things so hard to diagnose? I could had solve at least part of the problem months ago if I could find the freaking log. And if I had access to it now, I'm almost surely would know what's screwing with the process now. ---- Link for future reference.