Lisias

Kids nowadays. On my time, before the internet, 100 bucks was the price I had to pay for the shipping and importing taxes alone for the books I needed to carry on my job. I had to carefully weight the cost of the book with the incoming the book would provide to justify buying the thing - but most times than my bank account would like, I ended up buying the damn thing the same just because the thing was interesting. I probably was the only guy in town that really knew how to do low level programming in VGA. (or the only idiot that spent a hell of a money importing the Kim Carnes Essential CD).

TweakScale and the TweakScale Companions. Everything else stays on the game no more than 1 or 2 days. These two troublemakers are taking all my free time lately...

Move from another thread. @Dhruv, I moved the conversation here because now I'm sure it's related to a Companion. TL;DR : user installed TweakScale Companion LivingStyle, CXA and HabTech - but user is not being able to use the habtech parts. See original post. I think there's something missing on the installment. I didn't found HabTech neither HabTech2 on your GameData (module manager prints a report with what it finds). So, you installed HabTech on the wrong place, or perhaps installed something else believing it's HabTech? To make sure, the HabTech (1 and 2) Living Style supports at this moment can be downloaded from Spacedock using the links below: https://spacedock.info/mod/449/HabTech https://spacedock.info/mod/2078/HabTech2 I found CXA and Station Parts Expansion Redux on your log. From these, only CXA were patched for TweakScale - SPER is still WiP at the moment (waiting just I have some sparing time to finish it).

We had post at the very same time!

Got it. [LOG 21:57:15.715] [TweakScale] INFO: WriteDryCost Concluded : 1647 parts found ; 0 checks failed ; 0 parts with hotfixes ; 0 parts with issues overruled ; 3 Show Stoppers found; 0 Sanity Check failed; 739 unscalable parts. [LOG 21:57:15.585] [TweakScale] ERROR: **FATAL** Part KIS.Container1 (SC-62 Portable Container) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0 [LOG 21:57:15.585] [TweakScale] ERROR: **FATAL** Part KIS.Container2 (ILC-18k Container) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0 [LOG 21:57:15.585] [TweakScale] ERROR: **FATAL** Part KIS.Container3 (ISC-6K Container) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). at error:0 The three KIS Containers... Humm... Sounds familiar. [LOG 18:36:32.328] Applying update TweakScale/Deprecating/patches/KIS_TweakScale/@PART[KIS_Container1] to KIS/Parts/container1/part.cfg/PART[KIS_Container1] [LOG 18:36:33.153] Applying update TweakScale/patches/KIS_TweakScale/@PART[KIS_Container1] to KIS/Parts/container1/part.cfg/PART[KIS_Container1] Yep. You forgot to clean up the old files before installing the new release. Delete TweakScale/patches/KIS_TweakScale.cfg and everything will be ok. Cheers!

Do you have a github account? You can zip the whole thing and drag'n'drop it on a comment here.

Announce TweakScale 2.5.0.22 Beta is now available for the brave Kerbonauts that don't fear burning savegames in sacrifice to the Krakens. This is a maintenance release, fixing some annoying bugs introduced on the .21 while refactoring things to allow the missing features to be implemented on a sane way (less Code Warrior, more Engineering). Please note that TS Beta is to be used on disposable savegames only. I'm using this stunt on my own savegames, obviously, but now and then a bug passes through - but I know how to edit and fix my own savegames, and I'm a S.A.V.E. heavy user! Any reports about it (being a bug or not) should be posted on issue #42 (or I will get lost - again - on the sea of bug reports!).

If it makes you feel better, I'm trying for years already. I'm not even close. But there's a guy that is even better (in fact, Lowne says he learnt a lot from him), I suggest you spend some time watching Scott Manley's older videos. Check this playlist of him: Some (if not most) videos are from the early versions of KSP - so things will change a bit on the new ones (specially the drag, that changed a lot on 1.8.0 and newer), nut the theory it's the same. And we can always add MOAR BOOSTERS

Thanks! I'm waiting. it will be appreciated. But let's tackle down the CXA problem first, to avoiding chasing our tails on things that may be just different M.O. for the same culprit.

Ah, so it was that! I was going crazy on TweakScale Beta, because it also has some glitches on handling nodes and I was thinking this was one of them!!! (it's pretty hard to hunt a bug that doesn's exists!! ) Thanks @Commodore_32 for solving that for us (me and @neistridlar).

It has to do with the Authors. If CKAN removes or denies an entry claiming lack of consent from another copyright holder of the material, then that copyright holder is on license infringement him/herself if the material is on GPL and/or CC-SA . By using any other claim, that situation doesn't present itself. It's a two layered problem - someone could get burnt by something you claim while doing something, not by doing it.

And again, I'm not talking about the CKAN metadata, but the "need of the author to have consent when the license has already granted it". People are somewhat freakout here about a thingy called "consent", disregarding the licensing terms. As you said above: (emphasis are mine). And this is the legal problem. I'm not arguing it's better or worse if the author wants the thing to be published on CKAN, this is not a judgment of value about the policy. I'm talking about someone else willing to publish a GPL and/or CC-SA material on CKAN and you saying "no" because the author didn't consented - and the need of such consent is a direct violation of that license terms, what can render the license null and void, what by its turn potentially renders the author in copyright violation of the material he reused on his work. So, you would be triggering such problems by denying the publishing using this reason. So, use any other reason and don't mention the Author to get the dude's SAS covered on the matter. That no one on CKAN considers my theories valid it's obvious, otherwise you would be mitigating them. That's the reason I'm talking about, there's not need to talk about something that would not be happen because it's mitigated already. Of course CKAN is entitled to call me nuts, but yet, Copyright Trolling is a thing and it happens and it doesn't need your acknowledge of the problem. You don't need to be wrong to get a strike, it's enough for the claimer to have a plausible cause. Even GITHUB had to deal with this (besides not exactly the same way I think CKAN should): Source. So, it's not a bizarro legal issue. It's real and even big players are handing it somehow.

Delete GameData/BDArmory/MMPatches/BDArmory_TweakScale.cfg. I just checked the github repository for BDArmory and this file is not there. I also downloaded the latest release (at this time), and this file is not there neither. I think you updated BDArmory by unzipping the new release over the old without cleaning up, and so you ended up with an oldie lingering on the rig and playing havoc with the installment. Cheers! -- POST EDIT -- This issue ringed a bell on my head, and I did a search on this thread about BDArmory_TweakScale. And "we have a Bingo!" , I already had solved this one June this year. Note to myself: "Use the Search, Luke!" . (but at that time it didn't occurred to me the reason of the problem, so this post ended up being a more complete answer, providing the fix but also how to prevent it from happening again, i.e., cleaning up old files before updating).

Lowne is a veteran, and a skilled one. As @Streetwind said, you need to practice a lot in order to get the same resuls as him. How much you should go straight to the upper atmosphere before doing the gravity turn makes the difference beetween reaching orbit or barely getting a suborbital. Learning when to throttle down to save fuel (as too much speed on the atmosphere will make you burn fuel due drag) is another thing to be mastered. Additionally, the video has 2 years already, perhaps made on KSP 1.7.3? On 1.8.0 some changes affected drag, and so designs that worked fine before became gas guzzlers now (or vice versa). So perhaps this also could be influencing on your dificulties. Disclosure: I just manage to reach Mün using almost twice the fuel people use on Youtube.

@Dhruv, I think I found something - but related to habtech on 1.9.1. There's something on the trusses that is firing up NREs on the LateUpdate thingy, and after that started to happen, weird things happened on KSP (as aircrafts "flying" in slow motion), probably due some thread on KSP guts dying due the stunt. It may be something pretty stupid, a missing value on some module that KSP takes for granted but didn't existed when habtech was issued, and I think something related can be happening with you on Stock Alike Parts Redux. I'm really interested on this issue now, can you please try to reproduce the problem and then send me a KSP.log with the PMAs? I can use the Companion to inject a proper fix on it.

Nope. You are not understanding the problem CKAN says "In order to enter this club with this token, you need to ask permission from the previous owner of the token - however, the permission is already granted by the license and the previous owner would be in license infringement if he/she fails to say 'yes'". So there's zero need of asking any Author for consent, instead of risking putting the guy on a license infringement claiming he need to grant a permission already granted by the licensed he used. Just use any other excuse, never claim a consent is needed. Because if you drop or refuse an Add'On licensed under GPL ou CC-SA under the claim that the "original" Author opposed to it, you are saying the Author exerted an additional restriction, what's explicitly forbidden by the GPL and CC-SA. GPL goes one step beyond: it nullifies itself on the case, and so the Author would be in license violation of every third-party commit the repo have (every single commit has a copyright) - what implies in copyright violation. And since yourself said above: that this is a separated issue from the question of the author consent, when the licenses mentioned explicitly says it's not, I'm a bit sceptical by your statement above, where you says: Please note that I'm not criticising what you intent to do - I'm criticising what I think you are doing instead.

(From this thread) And where the users are going to get support, once the Author says he don't want to handle CKAN issues at all? There's a place on the netkan file where such information is available? Dude, if the policy says that the Author must violate the licensing terms of the Add'On in order to get the thing published, licensing is relevant here. Some licenses say explicitly that Authors cannot impose further restrictions without violating the licensing terms themselves. So by telling people they need to get consent of the Author to exercise a right already granted by the license, you are putting the guy between a rock and a hard place - because he just can't say "no", and failing to say "yes" may not be an acceptable excuse on a license infringement claim. Use the Trademark coin, say the thing must be published on Forum first (and let the Forum handle this mess), say anything else, but don't say the author needs to violate his own licensing terms in order to someone get the thing published on CKAN. (of course, assuming the dude is using GPL and/or CC-SA).

Besides marginally, I consider this ontopic because @neistridlar mentioned above "*in fact I don't think I can deny any one making a "CKAN edition" of NAP, and posting puting it on CKAN, given the licensing I'm using", and I'm counter arguing saying a fork is not needed, what the needs is a Packager to handle the undesired burden while he keeps focused on the Add'On itself. Of course, I may be wrong on it

Pretty comprehensive report, thank you! [ERR 11:51:57.054] ADDON BINDER: Cannot resolve assembly: KSP_Log, Culture=neutral, PublicKeyToken=null [ERR 11:51:57.054] ADDON BINDER: Cannot resolve assembly: KSP_Log, Culture=neutral, PublicKeyToken=null [WRN 11:51:57.055] The script 'DifferentialThrustMod.DifferentialThrust' could not be instantiated! [ERR 11:51:57.055] Cannot create a PartModule of typename 'DifferentialThrust' You are missing a thingy called KSP_LOG. It's a dependency for DifferentialThrustMod (apparently), and since this thing must be instantiated on one of that "special" places I mentioned, MM improperly flags it as "incompatible". I think you need to install this thing - but I failed to locate the source code on the DifferentialThrustMod where it's being used - so perhaps the DifferentialThrustMod is borking due something else that needs the KSP_LOG thingy and had borked first, and so the DifferentialThrustMod ended up taking the blame. Install the SpaceTuxLibrary and see if things work now. Cheers!

It's not how it works on the example I gave. A "packager" is not a random guy that zipped the thing, It's a guy responsible to keep the thing working on the target environment. If the guy is self nominated, if it's pinpointed by the Author, or chosen by the CKAN guys, it's a completely different history. Exactly. And the problem here is not about consent, it's about hassle. The Author already stated he doesn't object being listed on CKAN, he objects having to deal with it. He don't want to write the netkan file. He don't want to support problems related to CKAN. He's willing only to support his work directly. In other words, he wants a Packager who will maintain all the CKAN specific problems away from him: someone what would keep the netkan updated and handle the support tickets from ckan users first, filtering everything not directly related to the Add'On. Additionally, please remember that imposing additional restrictions to the licensing terms is a direct violation of the licensing terms of some Add'Ons. Avoid claiming lack of Author's consent when the thing is licensed under GPL or CC-SA style licenses, that explicitly forbids additional restrictions over the licensing terms. Say "I don't like your nose" as the reason if you want (you have not the duty to publish anything) but don't impose additional conditions explicitly forbidden by the license - you are painting the Author as a possible license infringer him/herself. Authors that object being listed on CKAN (or in any other place) should pick a license that allows them to do that. See the licensing terms discussed above. But, in a way or another, and returning to the problem at hands, we are talking about Authors that don't care about CKAN, they just don't want to support CKAN themselves. A completely different problem. Once one manage an agreement from the Author to allow the use of the Trademark on CKAN (a right the licenses I mentioned agree is not waived by the author on publishing), or adequately adapt the thing to respect it, what would be the legal/moral/whatever problem on allowing an alternate channel where Packagers would do proper support on CKAN for Add'Ons those authors just don't care (what's different from objecting) publishing on CKAN?

On the same directory where the KSP_X64.exe is. This is a complete essay on the subject.

Announce TweakScale Companion for NeistAir BETA was released, adding TweakScale /L support to (who would guess?) Neist Airliner Parts! Cheers!

Well, I just tested this Companion with TS 2.5 beta and CXA, and by coincidence, on 1.9.1. And I found not problems. So it should be something on your rig. Publish the KSP.log and I will try to find something wrong there. -- post edit -- @Dhruv, please redownload the LivingStyle (completely remove the directory you have on your rig before installing). While double checking due your report, I found some files on the wrong place. (not related to your issue, anyway).

Never, ever, leave the Engineering Team alone on duty in an extended holiday - with the keys of the warehouse and Jebediah around. Safety First! Higher resolution images and craft on my site. Or in Kerbal X.

Geez! How I could forgot this one? A pretty impressive work in progress collection of modern aircrafts!