Lisias

Would be a waste of I/O, the needed info is already available somewhere else! Nope. I would had diagnosed this thing more than an year ago if MM was catching such a mishap. Well, I don't know enough (yet) about GameDatabase to be absolutely sure that a node's name should not be null or empty (""), but at least a warning I will implement on my personal fork to see how things develop from here. But it would help a lot the maintainers to diagnose the problem, not to mention the developer in detecting it before making a release. In a way or another, once a warning or error is logged on KSP.log, the MM's Config Cache has a dump for the affected part - and this helps on diagnosing the thing. Once we know what's happening, is way easier to find where it happened.

METAR I finally found at least one reason for the infamous parts failed being checked! (do not misunderstand it to parts failing the check itself) Some borked patches are injecting NULLs on the node's name, and since every single node needs a name in order to understand what's inside, this is a bug - at least for TweakScale. The first case with a successful diagnose (and fix) is on the spoiler. People getting the Warning above is advised to reach me here posting the KSP.log on dropbox, google drive or something. Now I know what to look for!

hi. I found some errors on your patches (thanks TweakScale's paranoid on checking parts and logging any weirdness!). On GameData/TURD/TU_Standardised_Switching/173_Standardised_Switching.cfg , I found: @PART[adapterLargeSmallBi,adapterLargeSmallQuad,adapterLargeSmallTri]:FOR[000_Standardised_Switching]:NEEDS[TexturesUnlimited] { @MODULE[ModulePartVariants] { @VARIANT[Dark] { !TEXTURE,*{} EXTRA_INFO { textureSet = Stock_Default_stackAdapters_Dark } } @VARIANT[White] { !TEXTURE,*{} { textureSet = Stock_Default_stackAdapters_White } } Note the missing EXTRA_INFO for the White. This patch should be: @PART[adapterLargeSmallBi,adapterLargeSmallQuad,adapterLargeSmallTri]:FOR[000_Standardised_Switching]:NEEDS[TexturesUnlimited] { @MODULE[ModulePartVariants] { @VARIANT[Dark] { !TEXTURE,*{} EXTRA_INFO { textureSet = Stock_Default_stackAdapters_Dark } } @VARIANT[White] { !TEXTURE,*{} EXTRA_INFO // HERE, a patched patch! { textureSet = Stock_Default_stackAdapters_White } } This just not restored the intended feature, but also prevented problems on third-party Add'Ons that were borking due a node without a name (TweakScale was getting a NRE on this). Cheers!

(emphasis is mine). So there's no real subtracting - it's only adding with additive inverse with a fancy name.

To tell the true, there are no gas reverse. Only Kinect energy being converted into heat. Additions, additions, additions everywhere! My God... It's full of additions....

There're not such thing as subtractions, they had lied to you at school. What's exists is adding negative numbers. Since 0 has no sigh, 0 exposed the lie! So 1 - 1 = 0 // Lie 1 + -1 = 0 // The only True

See my post above. Use MM3 or an alternative fork for MM4 with the glitch fixed.

I knew some of them before becoming Moderators. Simple answer: NO. (I'm kidding... I think...)

Yes, it is. The problem is Module Manager 4. Use Module Manager 3, or some alternative fork that have this glitch fixed.

I think you've got a local issue there. I haven't noticed any drag changes recently, all the planes that I built back in the day still function fine right now. I have some problems on 1.8.x too, one of them are the drag courses - but on my case, there're less drag than on previous versions. My spaceplanes gone kaput on reentry due... lack of drag. But at least for this contest incarnation this should be not a problem for while: And I starting to like this rule.

Hi. I found a bug while running Spectra on a case sensitive file system (MacOS and Linux). The configs are trying to load some assets from GameData/Spectra/Spectra_Scatterer , but on the zipfile the dir is named GameData/Spectra/Spectra_scatterer . On Windows machines this doesn't matter, but on Linux and MacOS (with case sensitiveness turned on for the filesystems), you end up with weird images on the screen. I checked the config files, and every one is using Spectra_Scatterer , so the easiest way out for me was to rename the directory to Spectra_Scatterer. Cheers -- post edit -- It's the exactly behaviour described by @Yeet_TheDinosaur . Yeet, do as I said on this post and check if it fixes the issue for you.

Given that it's said that every time someone asks for a release date, the release is pushed 2 weeks ahead, I expect KSP2 to go live on the second semester of 2061. With David Bowman hired as Community Manager and HAL 9000 acting as the Space.Theory's version of Clippy. The Monoliths are already there, HAL will feel as it's home. Having the Monoliths sending high pitch messages to Moon now and then will be an annoyance, however.

I had tweaked some contracts for regular flights long time ago, using Contract Configurator and KerbinSide. None of them really worked well enough to be published, but it was fun nevertheless. I was trying to figure out a way to use Civilian Population on such stunts, but then TweakScale happened.

I use Add Kerbal for Tourists. It's a waste of Kerbal Resources to fly big, comercial crafts using engineers and scientists. Not to mention the insurance premium, way more cheap for tourists.

It's something on third-party modules (one of them from Squad) that TweakScale needs to learn how to cope with it. This is a new. Parts using FSbuoyancy are triggering some weird side-effects on the part's mass, and I withdrew TweakScale support for parts using it to prevent Krakens (not sure if they were involved on the mess last year, but since I have no more reports of Krakens with this Sanity Check activated, the sad true is that I'm afraid of trying my luck by lifting the block). I know for sure that SXT uses Firespitter's DLL, so obviously the parts that use FSbuoyancy will not scale. Doing a quick check, found these ones: If the parts you are mentioning is one of that ones, we have a really huge problem - they shouldn't be giving you scaling problems because they shouldn't being scaled at all! Please publish your KSP.log.

On the Kerbal way - since 1896. For more: https://designyoutrust.com/2020/02/riding-giant-mechanical-tricycles-in-1896/

Well, Copyright Laws are, indeed, terribly ridiculous. And most (if not all) of the problems we discussed here were triggered by such laws. I think we pushed the limits a bit, but the problems are deeply related, IMHO. But the tittle can be improved, indeed. Unfortunately, there is no real solution to these problems, but at least we can mitigate them by exposing as little surface as possible to possible attacks. I understand. However, we are not talking about the things moderators do right. The arguments are about what we think it's being done... in a legally unadequate way..

Impolite it's an understatement. And shoving likes into a harassment (including from moderators, damnit!) doesn't make it less of a harassment. And a close look on GPL and CC licenses will reveal the conditions in which the licence can be terminated for the current licensor and all of them lead to serious copyright infringement - with Forum having active role on the infringement (even that unintentionally). (unless the dude is the owner of the IP, not a licensee himself - what, really, it's far from the most common use case here - and no, "blessings" are not recognised by a Court of Law as a proper cession of IP rights, it's essentially placebo wording). Copyright Trolls are a thing. They work hard and effectively to earn they money, Forum doesn't needs to help them on making their living. @R-T-B had already warned, more than once, and I warn too: it's not what the moderators think is harassment or infringement that matters. What really matters is what a lawyer (and, ultimately a Court of Law) think it's a problem. In special, I think this is a pretty good signal of what I'm saying:

What the rules say about publicly harassment of people that follows Forum rules, but failed to comply to a culture not enforced by the Forum?

it's not exactly how things works on real World. Google for Misprision of Felony. Copyright Infringement can be a misdemeanour but also a felony, by the way. But it's good to know such a culture is not enforced, besides implying that the harassment that people got due this is tolerated. I will take this statement as an Official Forum statement.

You missed the point. On both cases (R.T.B. and now steve_v) the maintainers were (temporarily or not) unreachable. These guys were trying to help users with problems when the current maintainers weren't able to do so. And being impolite is not grounds to be unlawfully treated. We live in a way bigger society than this Forum, and this forum's notion of politeness would render you fired or even under litigation where I work. What we do here affect our reputations. The whole point is that if that guy was reachable, users would not be asking someone else for help. We need to reach some compromise not only to the Add'On maintainers and authors, but also to the users - they are KSP source of incoming, after all. Someone has to pay for this party. And as I'm afraid KSP is risking to find out, this reputation spreads and have real consequences on people's lives. Failing to fully comply with FOSS licenses is the best way to be vetted while applying for jobs on some companies. You don't like FOSS culture? It's ok. But then don't use their licenses. Great. Now tell me how many people is moving to Iran in order to make a living and develop that beautiful country. (I recommend avoid airplanes there, by the way). If Forum is willing to keep and indulge such "culture", be prepared to clash with bigger cultures that see this as an offense, some of them a legal offense. I remember a company that on late 90's also developed an internal culture on the use of FOSS IP. Their name is TiVo. I would recommend to avoid following their steps. If the FOSS culture is not suitable for KSP culture, a suggest stating that clearly to avoid future conflicts. As well a official recommendation for avoid FOSS licenses for KSP Add'Ons.

Moved from KSPIE Thread. These 9 parts failing Sanity Checks are parts that are using some modules that TweakScale needs to get support updated in order to avoid unleashing the Kraken on your savegame. It's a long history, but TL;DR is that as KSP evolved, some Modules got leaved behind or changed and stop behaving the way TweakScale expected. These 9 parts use a few Modules I didn't get time to fix yet. These parts are good to be used, and they didn't failed to be loaded. They failed the sanity checks TweakScale does in each part to detect known issues that could lead to some nasty bugs. They just would not be scaled. The only really bad news from TweakScale are shown in Red Messages ("Houston, we have a problem"). Yellow messages are informing you about something that can annoy you - besides ending up being an annoyance themselves. There's a Module Manager patch to suppress this Warning, if you want. But by installing new Add'Ons with affected parts, the Warning will come back for such parts. Let me known if you want it.

I beg to differ. See the thread on the spoiler. If creating a separated thread is the best way, could you please openly and clearly state that on Forum Guidelines? The current Modus Operandi here is incredibly "Made Man" style. You need to ask for permission to do anything already granted by the license (or risking being harassed even outside this Forum). Until you get such a permission, any attempt to help a user can face open hostility. But if that guy were reachable, there would not be a need for someone to provide such a help, right? So, back to creating a new thread for ... may we call it "alternative releases"? Assuming this is really the best way to proceed, may I suggest a new Forum Topic called "Voluntary and/or Unofficial Support for Stalled Add'Ons" or something? Perhaps on the "GAMEPLAY AND TECHNICAL SUPPORT" chapter, to make it clear it is not a properly "adopted" Add'On? Mainly because this site is not attended only by kids - there're also CTOs, Seniors in many fields, Journalists, people with connections on governments, you name it, and the treatment given to R.T.B. (a retired journalist, by the way) reflects badly not only on Forum , but also on TTI as they are now the owners of this thing. As far as I know, Elon Musk can have an anonymous login here, he's was known to play this game in the past (and he's hiring, by the way).

Sure thing. https://github.com/net-lisias-ksp/TweakScale/issues/93 https://github.com/net-lisias-ksp/TweakScale/issues/94 May I ask you to explain in #93 the new feature/use case in question, so I can look into it? Cheers!

It's a bug or something else I can help? I'm a OPT user, I will be glad to fix it!