Lisias

As I said, a manufacturing problem, a maintenance problem or they just shouldn't be using the material as first place. That said, I'm finished with you. I handled the conversation on a polite and respectful way - I'm even tried to advise you about the increasing rust in your truck - these things appears to be slow, but the corrosion happens exponentially. In a way of another, bye kid. Don't speed up your toy, your slim tires weren't made to handle the weight on speeding,

Yes, but... Remove the paint and the primer and let the steel be in direct contact with moisture and oxygen for some months, then come back here with the results. In time, I'm seeing some rust - it's way cheaper to solve this now. Please consider a (proper) paint job as soon as you can afford it. Been there, done that - I used to drive a GM Truck from the 90s to late 2010 - in the Amazon's Rain Forest. Yeah, the same one. Learnt a lot on the process.

It's never a material problem. Or you are using it improperly, or you are maintaining it improperly. Or you just shouldn't be using it at all. What you are describing sounds like a manufacturing problem that by some reason are not respecting the material constraints. There's a simply marvelous reading about the titanium parts of the SR-71 Blackbird rusting when made in the summer, but the same parts when made in the winter didn't: https://wisconsinmetaltech.com/titanium-and-the-sr-71/ TL;DR: it was the water. On summer, the local Public Administration were using chlorine in the water reservoirs to prevent algae. On the winter, they didn't bothered. And titanium doesn't like chlorine.

Perhaps not. There's a bunch of DeLorean DMC-12 in Brazil, and they are doing fine as long you properly maintain it. Steel rusting is a maintenance problem. Steel rusts, even the Carbon Steel. Heck, even Stainless Steel rusts if you abuse the material.

It was a bit more convoluted than that, but you didn't missed the bull's eye for too much. Initially, still on the Star.Theory times, Nate convinced the boss that it would be worth the extra effort to really improve the game instead of just patching up bugs, add some visual features and launch whatever comes out of the oven as KSP2. They** bought it, the idea of having interstellar exploration, colonies and multiplayer was appealing. But then, they came with the order to use the current KSP¹ source code as basis, instead of starting from scratch - but didn't rolled back to the original idea of a minimalistically improved KSP2. So they had to shove the new ideas they brought into the table using the old codebase that was not technically sound to take this hit. And the rest, frankly, is just consequence. === == = POST EDIT = == === ** They == Star.Theory . As far as I know, TTI just didn't involved themselves on the development at all.

Hi. O noticed https://spacedock.info is down right now. I can ping it > ping spacedock.info PING spacedock.info (95.217.59.158): 56 data bytes 64 bytes from 95.217.59.158: icmp_seq=0 ttl=49 time=227.223 ms 64 bytes from 95.217.59.158: icmp_seq=1 ttl=49 time=230.501 ms 64 bytes from 95.217.59.158: icmp_seq=2 ttl=49 time=226.199 ms 64 bytes from 95.217.59.158: icmp_seq=3 ttl=49 time=226.935 ms But can't curl it: > curl https://spacedock.info ; curl http://spacedock.info curl: (7) Failed to connect to spacedock.info port 443 after 239 ms: Couldn't connect to server curl: (7) Failed to connect to spacedock.info port 80 after 237 ms: Couldn't connect to server What suggests the HTTPD is down, but not the machine!

Fun fact... A popular influencer in Brazil bought one, and it's using it on the city's suburbs! https://g1.globo.com/sp/sao-paulo/noticia/2024/06/13/influenciador-de-sp-que-comprou-tesla-cybertruck-carro-indestrutivel-de-elon-musk-tem-seguranca-para-veiculo-e-pretende-fazer-seguro.ghtml

This appeared on my timeline today, don't remember when or why. I remember watching this when they released it. Dark times, but yet I'm pretty fond on this.

It happened last Friday too. WARNING: what follows is an exercise on expeculation! I'm plain guessing! On a wild guess, perhaps someone would be beefing up the servers for the heavier load on the weekend and thr 502 we get are the cloudflare caches still pinpoint the weaker servers that where shutdown. Let's see if we get more 502 after the weekend, when I'm presuming they would shutdown the power servers and reignite the cheaper ones for the working days.

Found it! [LOG 20:17:28.671] Load(Assembly): MagicSmokeIndustries/Plugins/Scale_Redist [LOG 20:17:28.671] AssemblyLoader: Loading assembly at C:\Kerbal Space Program\GameData\MagicSmokeIndustries\Plugins\Scale_Redist.dll You have an old copy of Infernal Robotics, apparently, from the times it was safe (besides still undesirable) to have multiple copies of an Assembly in memory. Delete C:\Kerbal Space Program\GameData\MagicSmokeIndustries\Plugins\Scale_Redist.dll and you will be fine.

Send me the KSP.log - whatever is happening, it's being logged and I will be able to detect by digging on it.

Risk management: knowing Musk, he had already assessed the situation. I would not be surprised if the engines have some self-destruction mechanism - perhaps some of the engine's failures Spaceship had may due they ironing out these devices being triggered prematurely by accident. At the time of the Apollo Missions, no one (besides Jules Verne and, perhaps, the Military) had the technology to do deep ocean recoveries, but nowadays even civilians are being able (with deadly reserves) to reach huge deepness in the ocean. Exactly my point. There're adversarial players in the scene nowadays with wider backs than Bezos. You don't need to care about these details if no one will have the guts to bring them to your attention. I risk speculate that the reason we don't have footage of the engines at touch down may be related to whatever safety mechanism the engines (hypothetically) have. Assuming, of course, that the mere contact from the engine's bells with the water would not do the trick itself - I wonder what would happen if all the engines would lighten up with the bells' mouths touching the water, the pressure would be enough to tear everything apart.

The worst parts of Copyright: There're agreements (as Berne Convention and WIPO) in which a Country agrees on enforcing the rights of the other Country's citizens on its territory. So a specific Copyright Right for a USA citizen would be enforced on Europe, even by Europe not recognizing such rights for their citizens; There're legal lawsuits right now claiming copyright infringement for changing code in your computer's memory, playing havoc to a significant part of the current KSP¹ modding scene (and the whole KSP2 one). So, yeah. There's a serious risk (the lawsuit stuck, it needs to be reversed now or we will be screwed) of fixing bugs on a USA program in your own computer be considered a Copyright Infringement soon.

Please, pretty please, with a cherry on top?

This Forum is being a source of many different sentiments over the years***, and I will always be fond of the times I had here. I learnt a lot. I wish from all my heart that I could, one day, retribute the kindness and friendship I found here from the majority of the you Fellow Kerbonauts from all the different statuses and roles. You are the reason Forum was/is fabulous. ------ *** Being one of the most frequent, the frustration for being unable to do a single post without tyops!

I will be damned, you are right! Deleting is allowed! Renaming, replacing, creating, pasting and "special" are the ones not allowed! But deleting is!! https://github.com/sarbian/ModuleManager/blob/c4561925f983e7ae81d9dfd4d11356a35cb6b9b6/ModuleManager/PatchExtractor.cs#L50 Command command = CommandParser.Parse(urlConfig.type, out string name); if (command == Command.Replace) { progress.Error(urlConfig, $"Error - replace command (%) is not valid on a root node: {urlConfig.SafeUrl()}"); return null; } else if (command == Command.Create) { progress.Error(urlConfig, $"Error - create command (&) is not valid on a root node: {urlConfig.SafeUrl()}"); return null; } else if (command == Command.Rename) { progress.Error(urlConfig, $"Error - rename command (|) is not valid on a root node: {urlConfig.SafeUrl()}"); return null; } else if (command == Command.Paste) { progress.Error(urlConfig, $"Error - paste command (#) is not valid on a root node: {urlConfig.SafeUrl()}"); return null; } else if (command == Command.Special) { progress.Error(urlConfig, $"Error - special command (*) is not valid on a root node: {urlConfig.SafeUrl()}"); return null; } Good to know you are double guessing all my posts, I will rest assured that any mistakes will not pass unchecked!! Sorry for the mistake, @lBoBl! I think the age is starting to bite

You essentially answered the question yourself. See how there's a GameData inside the NSIv2.4.2 one. Remember, there can be only one! Delete this NSIv2.4.2 directory. Then fire up KSP to see if it works now. If it works, unzip the NSI package on a temporary directory, and then copy its GameData contents (and not the GameData itself) inside the KSP's GameData.

It's some time since I last posted something from these guys! Postmodern Jukebox.

You are judging him by what you think he should had did with Twitter, not by what he wants to do with it. For starters - the BoD sold Twitter to Musk. All of these problems would not be happening if they just had decided to do not sell Twitter, or to sell it to someone else. But yet, they sold it to Musk. Had you asked why? They were going to get bankrupt soon, and they didn't wanted to be responsible for the bankruptcy - that's why. They didn't found any other idiot investor to buy it at that price. And why Musk bought it? Good question, only him can answer it. But he had a plan, and if the sources I had read were right, this plan is called X-Application (the everything app). I nurture no illusions for the future of Twitter X as we know it today - it will be dismembered or absorbed. Point. Right now, I'm enjoying it the way I can for the time it's possible. And since this thing would be probably dead anyway by this time without Musk, what the hell - so be it. Again, you are judging him by what you think he should be doing, and not by his objectives. Tesla's finality was to fund Space X. Point. Musk have no other plans from it than to fund Space X and he's being pretty consistent with this. Again, all the board shareholders** had to do is to deny the bonus - but they granted it. Good for Musk, he got what he wanted. Again. If this will be good for Tesla's shareholders, time will tell - but be absolutely sure about one thing: they will get what they deserve. I hope they deserve better, for their own sake. ** the voting was made by the shareholders, not the board of directors. My bad. Fixed. You are forgetting one very important point: without Space X, we would not have Starlink. And without Starlink, USA would be in a very, very dire strait facing the challenges USA's putting themselves on (like some events happening right now on Ukraine). Do you really think the Pentagon NASA is betting hard on Space X because they found Spaceship cool? Musk is not alone on this. He have powerful people backing him. Looking on the convoluted development of Boeing's Starliner, I think the reasons are clear by now. Welcome to astropolitics - you are going to like it as much as you like geopolitics. Perhaps. But until the moment, he managed to keep some dead corpses moving, so it would still be better than what we have now. I said above Musk is ruthless. You replied saying he's merciless. We are both right on this one for sure. If Musk would fund KSP, he would do it because he found a way to use it for something, and not because he's nice. But yet, where KSP is going right now anyway?

Well, so we will need to agree on disagree. You know, Musk is not known for hiring bad engineers - it's the other way around, he fires them mercilessly if he thinks they are not up to the task. https://www.reuters.com/business/autos-transportation/inside-story-elon-musks-mass-firings-tesla-supercharger-staff-2024-05-15/ I think your argument is risking not working exactly how you intended. I'm not implying it is working like I would like neither - Musk is ruthless, after all. By Kraken's sake, are you reading this thread? No one is asking him to lead the project, but to fund it! From a personal point of view, I think that an ideal person for the job would be John Carmack.

Well, I can say that I felt exactly this way before him. So, worst case scenario, Twitter remains the same - the only change was the focus of the bias. You are being extremely naive now. Just see how much attention the last Starship flight got in the media, and you will see that he have a lot of supporters, including here. For the best, and for the worst.

I remember some guy I did support commenting that 1.10.1 were the least problematic for him. I can't vow for this information, though, as everything from 1.9.0 gave me many, many little headaches when I tried them. I think that if you start new savegames on these newer KSPs, you should be OK. But once you have a long running savegame, porting it past 1.7.3 became challenging for me (besides seeing some serious performance gains on 1.8.1!!) Exactly my greatest grief. They had years of openly published code with work around pinpointing where the problems were, all they had to do is to port the fixes on the main codebase before releasing 1.12.5. We are not even talking about performance enhancements - merely to apply properly the fixes we already had detected and worked around, deterministically evidencing the bugs and the corrections!

Please measure it. Last time we talked about performance, I had benchmarks to support my claims. On a (minimalist and naive, admittedly) measure here I could not detect any performance differences between using a monolithic mu file, and the legolized ones I'm preferring to use now. I can detect (small) measurable savings in memory, but could not detect any performance ones.

I'm still playing 1.7.3, it has the best feature/bug ratio IMHO.

How KSP does it it's really out of the scope of this. I think it could even be undesirable to know. What matters from our point of view is that everything works as you had loaded them from a single mu file. I fact, I quoted "merge" in an (apparently futile) intent to use the word as an allegory instead of the factual meaning, as I don't have any insight as how KSP really does it under the bonnet.