Lisias

TSO of my day: Waiting for Cousteau, Jean Michel Jarre.

Because a replacement is not feasible under the Copyright law. Check this post below for the rationale: TL;DR: the only shot we have to do it under the Law is by going Internet Archive style.

You see, it didn't worked well every time, see N1. Or the Nedelin catastropohe - and, more recently, even the Brazil's VLS-1 V03 in Alcântara (TL;DR: a safety circuit failed previously, so they deactivated it to prevent another mishap as the problem it aimed to prevent was seemed unlikely to happen at that moment. But the lack of that safety caused the booster to accidentally ignite during the preparations for the V03). As usual, the sweat spot appears to be somewhere in the middle of the two extremes. Ultimately, the degree of specialization needed nowadays (as well the competition for such specialized work-force) makes the lose of human lives way too costly, what prompts the American way more sustainable on the long run - the Nedelin accident seriously hindered the Soviet program, and the Alcântara accident effectively annihilated the Brazilian one (we just didn't had how to replace the dead specialists). The problem on NASA nowadays with SLS, IMHO, is the exactly same one that lead to the Space Shuttle disasters, but in the opposite extreme of the spectrum: use of the safety rules to maximize financial achievements instead of technological ones - but instead of minimizing expenditures on safeties, on SLS they maximize the earnings on the same safeties.

Just a warning - I got some HTTP 500 from Forum today, 2025-0306 approximately at 21:10 Zulu. I got it twice, then came back 15 or 20 minutes later and everything was OK again. The error I got was like this one: Until this moment (one hour later), no more errors happened to me.

I think the message had passed through, because the joke was removed in the latest release! https://github.com/Capital-Asterisk/KSP_GroundEffect/commits/v1.1.1-catalpa/ That it's about... 2 years old already? https://github.com/Capital-Asterisk/KSP_GroundEffect/releases/tag/v1.1.1-catalpa Anyway, old news. Current Ground Effects had the joke removed!

@Saybur Stuff, I installed this on my Steam Deck, and it works fine. [LOG 17:55:41.097] [KSPe] Version 2.5.5.1 /L, on KSP 1.12.5.3190 (LinuxPlayer) under Unity 2019.4.18f1 <...> [LOG 17:55:41.441] [KSPe.Light.HLAirshipsCore] Version 2.4.2.4 /L for HLAirshipsCore /L [LOG 17:55:41.442] [HLAirshipsCore] Version 7.0.1.0R3 Core /L I found absolutely no problems while doing it. On a blind guess, I would suggest to install the latest KSPe, 2.5.5.1 . But it's a wild guess, because without the logs I don't have the slightest idea about what could had happened in your rig. I installed the latest KSPe, then installed the latest HKAirships, and did the following tests: Ran KSP from Desktop Mode from the original place, ~/.local/share/Steam/steamapps/common/Kerbal Space Program . Made a symlink from that place into Desktop called KSP.root . Ran KSP from ~/Desktop/KSP.root instead of the real directory. Make a full copy of the source KSP installment into a directory called KSP-copy, also on Desktop. Ran KSP from there. Returned to Game Mode and ran KSP from Steam. And the damned thing worked fine on every instance. Are you using KSP/Windows under Proton, perhaps? ---- POST EDIT ---- In a way or another, I had forgot to set 2.5.5.1 as the latest RELEASE. (sigh). Done. Don't have the slightest idea if it will fix the problem or not, trough - probably not. ---- POST POST EDIT ---- Oukey, using the instructions on this post I forced KSP/Windows to run under Proton Experimental. Everything worked as intended, no problems detected. Evidences: https://github.com/KSP-ModularManagement/KSPe/issues/48#issuecomment-2708134368 ---- POST POST POST EDIT ------ Tried every Proton available on Steam at the present time. It worked fine every time.

On the other hand, they took 9 years - from 1972 (program kick start) to 1981 (first fight) and expend 10.9B USD (about 50B nowadays after inflation) SpaceX started to talk about this vehicle in 2012, but the first prototype (the grass hopper) took off in 2019. From there to nowadays we have 5 years already (plus 7 from the initial talks to grass hoper), but the cost is about 5B USD to this moment - 10 times less expensive. And had I mentioned they caught a 280 ton, 20 history tall monster of a rocket with two chop sticks? Twice? [Thrice]. Still looks like the way to go, if you ask me.

You see... I disagree with the Ayuso's comment. Mars is not getting more complicated, only more expensive. IMHO SpaceX is passing through some serious growing pains - they have a Process problem, not a Engineering one.... Heck, they caught a ~280 tons >20 stories building sized booster with two Godzilla styled chop sticks as this would be just routine. THIS is some serious accomplishment, perhaps second only to landing two naked monkeys on Moon and bringing them back alive, as well kicking two Romi Isetta sized space ships out of the Solar System and still being able to talk to them. SpaceX appears to be suffering some serious Quality Control problems, the fast paced development is not cutting it anymore - this is probably a silly, very stupid mistake on the assembly line.

No bingos today... @ColdJ is in the house?

Pehaps Musk should stop wasting time playing Diabo and come back to play KSP¹.

We can try to fix it, if you want!

It´s pretty weird, to tell you the true. As you said, the loading thread just halts (and catches fire!), out of the blue.... Without a Exception Dump on the log, we can only expeculte (damn, I HATE empty try...catches!), but since the last log lines I found are: [LOG 12:04:33.929] KK: [KerbalKonstructs] Awake: Stopwatch: "Object loading1" elapsed time: 00:00:00.2966335 [ERR 12:04:33.941] KK: CreateGroupCenterIfMissing: No Group Found and no position found to create a Group: FP_LaunchSitesAppended/Instances/KermansStart/S2Crawlerway208m_g2-instances.cfg [WRN 12:04:33.941] KK: [StaticInstance] Orientate: cannot load FP_LaunchSitesAppended/Instances/KermansStart/S2Crawlerway208m_g2-instances.cfg [ERR 12:04:33.942] KK: CreateGroupCenterIfMissing: No Group Found and no position found to create a Group: FP_LaunchSitesAppended/Instances/KermansStart/S2Crawlerway52m_g2-instances.cfg [WRN 12:04:33.942] KK: [StaticInstance] Orientate: cannot load FP_LaunchSitesAppended/Instances/KermansStart/S2Crawlerway52m_g2-instances.cfg [ERR 12:04:33.942] KK: CreateGroupCenterIfMissing: No Group Found and no position found to create a Group: FP_LaunchSitesAppended/Instances/KermansStart/S2CrawlerwayCorner_g2-instances.cfg [WRN 12:04:33.942] KK: [StaticInstance] Orientate: cannot load FP_LaunchSitesAppended/Instances/KermansStart/S2CrawlerwayCorner_g2-instances.cfg [WRN 12:04:33.944] KK: [KerbalKonstructs] AttachFacilities: Value cannot be null. Parameter name: value [LOG 12:04:33.953] KK: [LaunchSiteManager] RegisterLaunchSite: Registering LaunchSite: Woomerang Helipad isHidden: False it's reasonable to infer that it may be related to KerbalKonstructs. Remove temporarily FP_LaunchSitesAppended and see if the problem goes away. Frankly, If it solves the problem, open a report on the maintainer's thread asking for help. I think it's a 50%/50% chance of this ends up working, so I kept digging into KSP.log looking for anything else smelling. I found this: [EXC 12:01:57.687] NullReferenceException: Object reference not set to an instance of an object kOS.Communication.ConnectivityManager.RefreshInstance () (at <0240a4feb0b74a9bba3ba4b7e1d9711a>:0) kOS.Communication.ConnectivityManager.get_Instance () (at <0240a4feb0b74a9bba3ba4b7e1d9711a>:0) kOS.Module.kOSVesselModule.UnHookEvents () (at <0240a4feb0b74a9bba3ba4b7e1d9711a>:0) kOS.Module.kOSVesselModule.OnDestroy () (at <0240a4feb0b74a9bba3ba4b7e1d9711a>:0) UnityEngine.Object:DestroyImmediate(Object) <>c:<CompileModules>b__4_0(Type) LoadedAssembly:TypeOperation(Action`1) LoadedAssembyList:TypeOperation(Action`1) VesselModuleManager:CompileModules() <LoadObjects>d__90:MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) <CreateDatabase>d__71:MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) GameDatabase:StartLoad() <LoadSystems>d__11:MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) LoadingScreen:Start() And this happened before the KSPCF Exception handler kicking in, so since there's that pesky bug on KSP's Assembly Loader/Resolver, it may be injecting collateral effects on KSPCF - I had reports (buried somewhere, I didn't found them now) related to something borking inside the PQS thingy with KK installed that it's pretty similar to your case, and the memory leakage only happened with KSPCF installed. DISCLAIMER: KSPCF was misbehaving after the problem had happened, so it was not the troublemaker, only something that got hit with its pants down by it. So if the first attempt (FP_LaunchSitesAppended) didn't worked, remove kOS and see what happens. If it solves the problem, check if you had installed the latest kOS. If yes, open a report on the maintainer's thread asking for help. Perhaps downgrading it to a previous version would help? If you still have the problem after removing kOS, then send another KSP.log so we can dig on the problem on the new configuration - this is going to degenerate into a fishing expedition, I'm afraid. And do what you do, do not load any valuable savegame until the problem is really fixed (i.e. no weird exceptions on the KSP.log), as this may screw up the savegame beyound salvation. It may be a good idea to fully backup your savegames right now, just in case.

Sleeping appears to be bad for my health. I spent most of the this 4 days holidays we have here (Carnival) sleeping. Literally. Today is Work Day, and I'm ssssssloooooowwwww as hell. Got up from the chair at least 2 times (that I can remember at least) to make some coffee, but in the way to the kitchen I remembered something else to be done, did it, and come back without the coffee - and then I sometime after I almost hit the keyboard with my nose, remembered I need some coffee, Rinse, Repeat. You know you are getting old when you remember your grandpa and think "hummm... now I understand the old guy..."

In the body, but the spirit's download is stuck at 99% since this dawn... (it was Carnival around here, and I slept most of the holidays - apparently, sleeping is bad for my health...) It's some days since last time I had see @Eclipse 32 around here. How do you do, dude?

Had anyone hailed the probe this year yet? Not? HAIL THE PROBE! https://www.orbiter-forum.com/threads/gathering-design-ideas-for-a-spaceship-builder.19974/ Now we had!!

And you are not alone. Recently, VALVe released all the source code for Team Fortress to the Source mod tools! https://www.gamesradar.com/games/fps/valve-adds-all-the-team-fortress-2-client-and-server-game-code-to-its-source-mod-tools-letting-modders-build-completely-new-games-based-on-tf2-and-publish-them-on-steam/ Essentially, anyone can use the Team Fortress 2 Source Code to write new games. Or to port TF2 to any other platform natively, as ARM or RISC-V. Interesting enough, even Electronic Arts is jumping in - the first 4 Command & Conquer games are now officially Open Source too: https://kotaku.com/command-conquer-ea-source-code-red-alert-generals-1851767009 Opening the Source of games is becoming a trend, finally. Things are getting very exciting nowadays - not a single day too soon, given that ID is doing it for 25 years already! I think we still can hope for KSP¹ going Open Source, eventually!

Search and Destroy for all directories called @thumbs. As the name says, these directories holds a ton os small images used for icons and other thingies in the UI. KSP has a bug the crashed the loading thread if one of these images is corrupt - but if you deleted them, KSP will just regenerate them and everything will be OK. If even after it, the game still halts on loading, send us the full KSP.log using Dropbox or something and we will give it a peek.

"Hi Sandy, hope you’re doing well"

Yes and no. If the decision is already made, so yeah - if they are going to shut it down, then shutdown this thing will be. If they decided to keep it alive, so alive it will linger. BUT... If they had not decided yet, the arguing is a two edged sword: it may tip the scale in a way or another, depending on how we argue! Enough people demonstrating care and wish to cooperate on keeping this alive, and they will probably consider keeping this alive as this is a good tool to keep the Franchise alive. On the other hand, we reveal ourselves a toxic, demanding and narcissistic group of people, they will probably kill this, as the potential for trouble and losses would be bigger than any gain this Forum could provide them. This Forum is a tool: it can be used to help them, or to screw them. "What is steel compared to the hand that wields it?" Thulsa Doom.

Bingo!!! Yes, I have. Check https://ksp.lisias.net/ Where in the World Kerbin is @Mr. Kerbin?

Well, it works for me: Send me your full KSP.log and the craft file so I can see what's happening. However, I don't use FAR, so there's a good chance FAR may be the problem. ---- POST EDIT --- In time... What's the A+ version you are using? -------- Soon™. I'm starting to be confident that my work is fixing things without screwing anything - I'm spending some time playing with it again and somehow I'm being able to detect and even diagnose some problems that I weren't before! https://github.com/net-lisias-ksp/AirplanePlus/issues/3#issuecomment-2699983820

Please send me your full KSP.log . Whatever is happening, it's logged there and it will allow me to diagnose the problem!

If you don't mind really old graphics, with really really limited gameplay, you can wet your feet on KSP using the initial free versions of KSP. You will find them here: They are really old, some of these versions are so different that sometimes you think it's a different game with Kerbals. But I decided to buy KSP after playing with them, so they still are useful.

Attach the RCS to some other part, then translate it with the translate tool with shiftt pressed to override the limits. The translation tool is one of the little buttons on the top left of the editing area in Editor.