Lisias

Well… Concurrent players and active add'on authors usually are a good metric. Yes, interest in games comes and goes, and when it happens with a decade long behemoth as KSP¹, it's not a surprise that this movement ends up with way more attention than common games. KSP¹ is not merely a game. It's a cultural phenomena, like Doom - but beyond, because we have a whole new generation of highly skilled professionals crediting KSP¹ for their decision on pursuing such career. Not even Doom managed to get this. You are failing to address exactly one of the main reasons KSP¹ managed to get such traction - long standing communities. This new model of discardable communities driven by Discord et all just doesn't works for long standing cultural phenomenas, because Culture implies in memory, remembrances, and social media like Discords thrives on the exact opposite. Quick paced, short living communities like Discord are good for marketing, no doubt. As a matter of fact, they are perfect for this. But you don't do a success career on gaming only with marketing. You need to gather people around you that would add value to your content. I don't see people with marvellous histories about rockets being mistakenly launched at "lunch time", or about how they knew someone that knew someone that was the driver for Armstrong and Aldrin on the pre Apollo times on Discord. Pursuing only instant gratification, discardable communication channels may work for kids, but not for the people that made KSP¹ great in the past. You need good content to thrive - so your choices are to have a huge budget to pay for such content, or to form a Community that will create such content for you. And you don't find good content creators on discardable communities with little to no memory. — — POST EDIT — — As a matter of fact… I connect to Dsicord about twice a month at best, being the last time about 10 days ago. And I found a Community with 9908 members that created about 94 new posts about KSP2 in that time, and 55 about KSP1. Really, the numbers for this old fashioned Forum looks way brighter, IMHO: we surpass these numbers here on a single hour on a good day.

It's not my place to fingerpoint people, so I will not give you any concrete examples. But… There's a thing called Reverse Engineering that it's a way to analyse the binary code in order to reproduce the source code. It's also known as decompiling. This practice is expressly not allowed by Forum Rules (see legal boundaries), as well the EULA. Now, this is not exactly illegal - but it's subject to legal complications in some cases, as well being illegal for sure in a few countries. That said, it's blatantly clear that a lot of authors around here are relying on such practices. No ill intended, I'm absolutely sure, but this had set a precedent where a few authors decided to monetize the results of such practices (what I think may cause legal implications even on USA). What the Devs can do about is to talk to their legal counsellors. The pertinent legislation is tricky enough to push me away from commenting about. Baby steps. They already won a round, let's see what happens. Some youtubers are probing using Juno instead of KSP, and this is already another round won. KSP¹ online players on Steam Charts are half from what it was early this year. SpaceDock total downloads ditto. CurseForge too. All the metrics I have strongly suggest that, right now, there're half (or even less) players on KSP¹ than we had earlier this year, eroding a user base that was growing strongly since at least March, 2022. Please note that such metrics are unable to give you the absolute number of players - we can only evaluate the numbers qualitatively, not quantitatively - i.e., I know for sure that we have half or less users than early this year, but I don't have the slightest idea about exactly how many they are or were. — — POST EDIT — — Not all Reverse Engineering techniques are considered shady. One of such techniques is called Clean Room, and this one is legal on every place I had looked at. And it's what I do on KSP-Recall, if you go to its github you will see inumeorus issues full of experimentations trying to figure out how things behaved that way.

Time is the best teacher and, also, the harsher - as I had said before by the way. KSP add'on are being ported to the competition; known youtubers replaced KSP to it on their videos; people are making money and getting hired accessing their source code in EULA's and Forum Rule's violation. We have a saying here on Brazil : Água mole em pedra dura, tanto bate até que fura. (by some reason, Forum is refusing to embed this video!) Erosion. We are witnessing the franchise's erosion.

The problem most people fail to realise is that they already had lost this one. There're people on the wild applying shading practices to access the source code and earning money from it. There're people even getting jobs by accessing the source code in EULA's and Forum's rules violation. This battle is over, the Genie is out of the bottle. Anyone is able to make some dimes at their expense now - the precedent has been set. What we are proposing is that they formalise the current status quo in a way in which they can profit from it too - before things get yet more out of control and beyound hope of being salvaged. Are you aware that KSP's add'ons are already being ported to the competition? People are already moving on, lefting them behind. After using their source code to leverage their add'ons, that it's now feeding the competition. Had they started to considering our proposition 6 months ago, chances are that they would be in a way better position - what's exactly what I had predicted it would happen. Unless they are intentionally skimming the franchise, I think it's time to start to think seriously on a change of strategy. Whatever they are doing now, it's not working for the game.

I love these typos. On a side note, I recently noted that the number or typos and "miswords" I do increases exponentially with the size of the swap file on my rig. I'm suspecting that I'm not that bad on typing, it looks like something failing on handling the keystrokes events on my rig. (right now, not a single typo happened on the last two sentences) You will love this history so! (look for "Don Morris' Australian Balloon 9825 Story) Fantastic history!

A 747 with afterburners as a first stage launch vehicle. A Space Shuttle used to carry and launch a smaller Space Shuttle. A C-5 as a launching platform for yet another Space Shuttle. Oh, dear…. What magnificent concepts for a KSP career game!!

As the kerbol breaks, above the ground An old kerbal stands on his chair As the engines warms, to the first rays of light A click song shatters the still!!

ANNOUNCE Impossible Innovations V0.8.10.0 is on the wild! 2023-1021: 0.8.10.0 (Lisias) for KSP >= 1.3.1 The KSP 1.6.0 patch to allow bulkheadless parts to be used was moved to KSP-Recall It’s not needed anymore, anyway Updating models from the archaic DAE to the standard mu format. II-hydrogenIsotopeConverter II-hydrogenTank Also fixes the jumping when launching crafts with these parts! Adds missing data on all parts Fixes the plumes for II-TDRCS-Lin II-TDRCS-Block Updated to use the latest KSPe Removes annoying messages about not able to create config from some files. Closes issues: #8 Normalise formatting and added missing info on all parts #2 Some engines are exhausting the wrong way! Revise the engines. #1 Some parts are triggering the damned jump from the Krakens on launch Download on the OP. Cheers!

@DZ885, @AtomicTech I just released the latest TweakScale Companion ÜbetPaket. It will add some new and improved patches, but also will get rid of that pesky "Cannot create config from file" messages, preventing further misunderstandings! Cheers!

Announce! New release 2023.10.21.0 for the TweakScale Companion ÜberPaket with everything (and the kitchen's sink) included for the lazy installers !! Updates the Companions: Aircrafts to 0.2 Frameworks to 0.4.0.2 Firespitter to 1.3.0.1 KIAS to 1.1 Multipass to 0.1 OPT to 0.0.1.1 Rockets to 0.0.2 SMCE to 0.0.2 See the project's main page to details. Your attention please Completely remove all the previous contents in the GameData/TweakScaleCompanion directory, or you will trigger some FATALities on TweakScale's Sanity Checks! This thingy needs TweakScale v2.4.7 or superior to work Download here or in the OP. Sooner also available on CurseForge and SpaceDock.

That "flats" are missing data on the metrics. Now and them something happens and data is not fed to steamchats and so, instead of interpolating the data, steamcharts just plots a zero and call it a day. On 2023-1016, 16:00 (unsure about the timezone), steamcharts plotted 0 concurrent players on KSP¹. But at 15:00 it plotted 1869 and at 17:00, 1946 concurrent players - so, that zero is obviously a glitch on the metrics gathering.

You can't bully people into caring - hitting everybody with the idea will just make people fed up about the subject. IMHO, the best line of action is to talk about only when pertinent - "Look, I know of a Closed Source that had this endemic problem, and they managed to get it tight after open sourcing it" is nice when you find someone complaining about a problem peskying them and that it's never fixed (as long you are telling the true - never do fanfic on Open Source, you will not make friends on both sides of the equation!). Open Source is a tool. A way to solve problems. It's not the solution for all of the problem in the World, however - we always need to consider that perhaps it may not be the right tool for this job and, so, we should always propose the use of the Open Source at the same time being open to alternative ideas (like the Shared Source model I mentioned some pages ago). Of course I would prefer OSI, but the objective is not promoting OSI, the objective is to fix problems, being OSI the best way I'm aware of. Videos about how KSP¹ was fabulous in the past, and how it can be great again (could not help myself hehehe) with the help of the Open Source is good, as long the content is interesting and it doesn't look like someone trying to evangelize you about something. It gets boring fast, and - again - ends up getting people fed-up and, so, counter-productive. About KSP2, IMHO just don't touch the subject. KSP¹ and Open Source are strong enough ideas by themselves, you don't need to belittle something else in comparison to make them look good. Just don't touch the subject - remember, "We may be wrong" - they manage to deliver KSP2 in a couple years, and it will make you look bad. On the other hand, if KSP2 fails anyway, what's the gain on repeating it again and again? There's no use on beating dead horses. Exactly, The thing must be good (i.e. profitable) for both sides, otherwise they would just not do it. I wouldn't, this is still Capitalism. Oukey, let's consider for a moment that they are really dying. Exactly by being in the imminence of death, they won't need us anymore - they need us when they are healthy and good, because it's our money that bring them such healthiness. If they are dying, we are irrelevant - because what they would be seeking instead is someone to buy the bankruptcy estate, and this includes the Source Code. Opening the Source will only make sense if: They will be "alive" to reap the benefits There're people around still willing to spend some money on the thing There's no better way to fix the mess we are now A huge amount of problems that plagued KSP¹ were due ego and arrogance. Will we improve the situation by repeating their mistakes?

Not by that. These Cannot Create Config messages from TweakScale Companion are annoying, but harmless. In a way or another, I had fixed these. I will check if these fixes are published and if not, will do it in this weekend. But, and again, these pesky messages are only annoyances. Whatever is affecting the user's rig, it's something else. — — POST EDIT — — The fixes were published on the individual packages, but I didn't published the updated ÜberPacket yet. Will do on the WeekEnd. In time, @DZ885, I think I found the trigger of the crash you described: BreakStuff False True (Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35) Uploading Crash Report NullReferenceException: Object reference not set to an instance of an object at KerbalRenamer.VeteranRenamer.Start () [0x00061] in <c0228513e9ce49ab8d3eca95c04c6e55>:0 UnityEngine.DebugLogHandler:Internal_LogException(Exception, Object) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Logger:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) Something is breaking GPP_Renamer: Load(Assembly): GPP/GPP_Renamer/KerbalRenamer (Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35) I don't have the slightest idea about what's this KerbalRenamer thing, but since it's form GPP, you will need to get further help from the GPP guys!

Landing that second stage on a boat would require a hell of a big one. I doubt even something twice as big as CVN-78 would withhold such a monster! It was the second thing I though (after "I need to do this on KSP!") You need a hell of a thrust to accelerate the compound to takeoff speed (they are on water, after all!), and after the thing takes off, the extra hardware will be just dead weight - having more thrust than you need for reaching orbit is pure waste. Not to mention that a good part of the fuselage would be wasted by carrying the fuel just to break the whole compound inertia (and water induced drag), again wasting internal space that could be used to something useful - as allowing more cargo to be shoved on the third stage by using the (now extra) internal fuel to do more orbital work for it. A Ground Effect vehicle as the Caspian Sea Monster appears to be a more plausible solution, I agree.

Absolutely atrocious! Ludicrous! Insane! I LOVED IT!!! - one of the best KSP projects I will ever do!! Hydrofoil Albatros Rocket. Can't find a use for it except by the military, however. The second stage (as the first stage is the boat!!!) need to land somewhere, after all, denying a large area of the Globe as civilian launching places.

Not yet. Real Life™ hijacked me from the ongoing task, and I didn't managed to get back to it yet. It's being developed on https://github.com/TweakScale/Companion_FuelSwitches if you want to follow it.

"Just a little push…"

What by the Kraken's name is this?? Kamov Ka-26

Well, I do when the thing is forced on me after I had paid for an ads free product.

One thing that was puzzling me for some time is how the infamous PD Launcher was shoved down our throats (or up the counter part). The things it could do for us were bluntly ignored, providing useless services instead - this don't look as something a developer would do, we know that we need to give the user something back if we need to convince them to use something new. Thinking a bit more, and considering what you had said, PD Launcher appears to be something conceived by an ads company - it's they job to force you to something in order to allow you do get what you want. You know, I'm considering that PD Launcher will be an Advertising Vehicle in the near future...

Hi. There's a way to temporarily unlock a thread to allow editing a post to remove unwanted words? It came to my attention recently that two words that I were using more or less usually is not acceptable by this Forum standards, and so I come back to my old posts to remove it too. However a bunch of them are locked on closed threads, preventing me from editing it. There's a way to fix them?

Old fart here, I think it's about 20 years since someone could call me "lad" without a smirk. But I'm willing to give you my 16 cents (0.02USD corrected by the inflation of the period!! ): The problem is not who is "talking", but who is "listening". Words are like poison - you need to ingest it to be affected by it. Whatever is happening around, it's happening by many, many different reasons - and very few of them are edifying. There're a lot of disgruntled franchise fans, no doubt - and everybody passes trough the 5 stages of acceptance (or grief) at their own pace - but this pace can be manhandled by 3rd parties to achieve some goal, and this is exactly what I think it's happening. The Game Industry is on a terrible disarray, and things are not going to get better in the near future - and I'm betting some snacks that a lot of people are promoting this drama as a way to try to push away the public attention from the real problems and, so, save their face and even their job. And there're also the ones that are actively working on an attempt to… humm… how to say… "hijack" perhaps? the attention of the public trying to get themselves a job that currently is secured by someone else. "Farinha pouca, meu pirão primeiro" - as it's said in Brazil (and, yeah, the successive economical crisis on my country made me an expert on this area). So, nope. This is not going to stop - money talks, and empty pockets hurt. Noisy combination. Really, the only way to push back this drama is by not listening to it. Let them talk to themselves, without audience, and the problem will be solved by itself. Remember what I said above: the most letal of the poisons is harmless if you decided not to ingest it. Whoever is spreading drama and smear, just ignore. Don't react, don't follow, don't like neither dislike and, most of all, do not spread it yourself. Just walk from them - and the problem will just vanish in the thin air.

Interesting... can you do us a favor? Install it back, reproduce the problem, quit KSP and publish the KSP.log? It can be some interaction with another add'on instead of being something on it! Cheers!

Long story made short, in the past the Scene was used to with some pretty nasty practices as having tons of copies of the same DLL to avoid having to handle dependencies. With many and many copies of the same DLL on the system, the C# runtime ended up creating a thingy called APP Domain for each new one - it's like a partition inside the VM, shielded from the other ones. And so calls for these APP Domains were made using a thingy called Serialization, that it's something like a thousand times slower than calling the code inside the same App Domain. Then they tried to fix that recently, short-circuiting any duplicated DLL to pinpoint the first one found - but by then they created another problem, since the firstly loaded DLL usually was the older (we name the files using the version, and KSP loads things ordered by ASCII), leading to a worst problem - broken dependencies due deprecated versions intalled on the rig besides the correct one being there too. Then they tried to fix this other problem, but some DLLs hadn't the version information they needed - and then KSP halted the loading, effectively fixing a problem by creating another even worse. Right now I don't know anymore how KSP is handling the problem, because I got fed up and wrote a thingy called Module Manager Watch Dog that monitors the system and barks when something (knowingly) bad is detected on the system preventing the user from getting screwed. (It would not help you on this exact problem, because MMWD doesn't sniffs into other authors' work without a reason - but I'm considering a Watch Dog for Firespitter now, as it's evident that it may screw things when installed wrongly). Cheers!

Impressive. I suspect he was arrested exactly by winning all the cases he represented!