Lisias

That was Unity's output_log.txt. I need the KSP.log that you can find in GameData/KSP.log .

Can you publish the KSP.log? I need to check the patching.

All of this is just wild speculation. It's meant to be confused, it's an open sky public brainstorming. TL;DR: who can talk, doesn't really knows. Who knows, can't really talk. So we ended up making educated guesses based (or biased) on what we think we know, getting new bits of information and then makind new re-educated guesses. There's a lot to learn on this things. It happens that you can't foresee what you are going to learn.

Delete GameData/TweakScale/patches/M2X_Tweakscale.cfg . This patch is kaput, and SuicidalInsanity's patches are way better anyway. I'm deprecating this patch from the distribution, it will not be a problem anymore on the next Release [of TweakScale]. You got a "Houston", and yes, this can be harmful. it means that the patching is not deterministic and there're different patches trying to do something with TweakScale on a part. When this happens, the patch that "wins" is used to rule the scaling. The nasty problem is that by adding or deleting an Add'On, the order in which the patches are applied can change, and then another rule will "win" and be used to scale everything using that part, including the flying crafts. It was a riot on my savegame when I was hit by that. Unfortunately I can't say you had zero issues before. You had zero detected issues before. Now they are being detected. I'm fixing every problem that is reported on the TweakScale thread (the "ok" button from the "Houston" send you directly to there!). Feel free to post there every time you think TweakScale can be bitting you. Cheers!

It's not how things work. A Company cannot forbid someone to exercise a fundamental right (the right to work) just because they don't like it. They must take a previous agreement from you. Written agreement. Then they have such options. That agreement is the non compete clause on the contract you sign when is hired. Even to "ask" without that agreement can be a legal liability - you risk a denounce by extortion depending on how you "ask". In the very end, it's on the Contract you signed. It's not something that you are forced by law to accept. Check the Contract and follow what's agreed there. These information can be easily found on Goggle (or by chatting to a friend laywer), so may I ask to prevent derailing (yet more) this thread, please? create a new one or hit me in a message for links if you want.

Too soon to know. KSP2 is being developed by another company, so there will no overlap on marketing efforts - other than using TTI's infrastructure. I expect Squad to defend their castle. KSP1 will endure as long it's profitable and/or useful. And always there's the chance that something goes wrong on KSP2 , so from a business perspective is premature to start to phase out KSP1 now. Not to mention keeping their feet on a niche they may not want to risk KSP2 yet, as Linux and MacOS. I'm seeing a lot of new Unity games claiming they cannot, yet, guarantee decent support for these platforms. KSP1, right now, is already there (even that with some issues). So, yeah. It's too soon to know.

Not so fast. These things happen since the Pong era. Magnavox sued Atari due the Pong game. Later, Atari sued Magnavox due Pac Man. There are plenty of cases in History about this. Some with happy ends, some not that much. http://mentalfloss.com/article/55078/11-times-video-games-led-lawsuits It does. https://www.cheapassgamer.com/topic/59051-ea-calls-ubisoft-on-forcing-non-compete-clauses-on-workers-in-letter/

Non compete clausules. The same thing that prevents HarvesteR to make a Curupira Space Program or something. * Curupira is a local folklore characterer.

Now I get it! I used the filename too, but only directories count!

It was my understanding that it would work. Well, I was wrong. I will check the MM documentation again. Thanks for the tip, I just fixed the file o github!

While getting a free copy is hardly something I would dislike , I have an alternative suggestion: a content stripped early access version where Add'On authors can test and develop the Add'Ons before Release. A planet, a moon, a Sun, a bunch of parts of every type - not necessarily from the main game (could be adapted versions from the KSP1?), KSP 1.0 demo style. Not sure if this is feasible from the strategic point of view (releasing a pre-production version, where people would add content for free can impair the selling later), but from the tactical point of view, would solve the problem under our noses.

Well.. It was a guess, now I'm sure. It's the exact same problem. [LOG 2019-08-19 16:49:31.017] Applying update TweakScale/patches/Squad/Squad_Util/@PART[batteryBankMini] to Squad/Parts/Electrical/z-200Battery/z-200Battery.cfg/PART [LOG 2019-08-19 16:50:07.840] Applying update RealismOverhaul/RO_SuggestedMods/Squad/RO_Squad_Electrical/@PART[batteryBankMini]:FOR[RealismOverhaul] to Squad/Parts/Electrical/z-200Battery/z-200Battery.cfg/PART Well, I don't think we can manage to apply a fix, as I was told that TweakScale is not supported by them (besides they providing TweakScale patches - but whatever). So I will cook a hot-fix for you. @Buflak, this may interest you too - at that time, I didn't had the Hot-Fix idea yet, but perhaps this can help you as you update your Add'Ons. Download the file below (it will be featured on the next minor release - sooner or later :P) Extras/TweakScale/HotFixes/RO-Stock_Electrical.cfg (click the Raw button) and save it into your GameData. I strongly advise to use the following directory (create it if needed): So the patches will survive updates and will be easily found when the time to delete them come. I don't have a Realism Overhaul testbed, so I didn't tested it. Could you please advise if this stunt manages to work? Additionally, @RealTimeShepherd, I found an awful amount of Exceptions from TweakScale while trying to inspect a lot of parts. I'm on the dark on that Exceptions. Could you please publish your GameData/ModuleManager.ConfigCache ? This can help me to diagnose that.

<unintentional hijacking of the thread. moved to private. my apologies>

The lesser problematic version for me was 1.4.3 . But my problems were all related to Add'Ons, not the game itself (it has some glitches, but they didn't bite me so hard as it did to others). The 1.4 series was a game (engine ) changer, we took the whole year to learn to cope with the changes. Interesting enough, now and then I fire up my 1.4.3 installments with the Add'Ons fixed (most of them, interim versions), and that version holds it very well for most of the time. It's surely a bit faster than 1.7, what's on a potato like my current machine, it's something. From my experience, there's few to almost none differences between 1.4.5 and 1.5.1 - I have the feeling that 1.4.4 should be the 1.5.0, with 1.4.x series ending with 1.4.3, and 1.5.x series ending with 1.5.3 (and not the 1.5.1). It looks silly, but Versioning for Add'Ons would be hugely easier to keep track this way.

Hold my beer. (you can keep it if I fail!)

This post was post, originally, to answer this post on Kerbal Construction Time thread. And quickly I realized I derailed the thread, so I created this one instead to declutter that one. —— I'm not exactly disappointed. it's exactly what I was expecting to say the true. (it's unity, after all) KSP 2.0 was an open secret after all. I even think that the original 2.0 hype was "planted" by someone from Star.Theory staff to gather "intelligence". I'm pretty sure we were being closely monitored all this time. Anyway. I remember the promo video for KSP 1.0. And I played a bit with KSP 1.0 later, and IMHO, the KSP tradition is being maintained. I expect a lot of learnt lessons to be applied, a somewhat elitized eco system at the first (due the higher pricing and legacy fan fase sticking for sometime on KSP 1), but on the long run, we will end up all here, complaining about KSP as we ever did. We will complain about new problems, but we will complain. I'm pretty sure some of us will complain about missing the good and faithful old problems. For me? I will keep going normally. KSP 2 is still way ahead (I expect it to launch in Xmas 2020, as the North Hemisphere's summertime is usually low on selling games - most people are enjoying the Sun out here!). I'm reaching a somewhat successful way of keeping my code KSP version independent (I have code running from 1.2.2 to 1.7.3, relying on specialized libraries to handle any difference), it's not impossible that I could manage to support KSP2 too. It's still Unity (for the best and for the worst), so it's feasible.

I derailed the thread. sorry. i moved it to this one:

É uma espécie de "banco de dados' para código, com histórico e uma pancada de features para facilitar trabalho em equipe. Dá uma olhada num deles. Então, ao invés de usar a reencarnação do protocolo DPLDPC (Disquete Pra Lá, Disquete Pra Cá - só que agora é dropbox!!!), você "comitta" e "sobe" o savegame para o github. Isso não só garante sincronia, como permite consertar os savegames se algo der errado. Também vai dar pra brincar de "what if" - vc pega o savegame que foi comitado no passado, cria um "branch" à partir dele, e começa à brincar daquele ponto. E por aí vai. Savegames são um tipo de código no frigir dos ovos. Então GIT funciona de boa com eles também. O que eu tentei fazer no FdS, mas fiquei sem tempo foi bolar uma forma de simplificar o processo para essa tarefa. Bom, tem o próximo FdS. Vamo ver se consigo.

Welcome back! (kinda of :-P). Sorry for that. If you are not aware, that Pesky, Scaring Message means that there're some Add'Ons on a toe stomping fest. Sometimes TweakScale can fix the mess by itself, or at least mitigate the problem. You will see Yellow warnings and advises when something not dangerous are in need of your attention. However, there're some other problems that would corrupt your savegames, cannot be fixed automatically, and can happen at anytime you install an Add'On. These as the fatal ones, and besides now and then a not letal glitch ends up mixed on the basket, a single one of the nasties can ruin your day. Check the Issue #34 to see what can happen (not only on VAB/SPH but also on the flying crafts!). Fixing the mess by hand is not for the faint of heart! Enough chitchat. Let's crack that nut. Follow the FATAlLities on your installment: I think you got lucky. I recognized the first of them, and the bluedog ones are the screaming victim. The perpetrator is CxAerospace. You will need to apply a hot-fix, as this Add'On is currently stalled. You will find instructions to fix CxAerospace on this post. TL;DR: So the patches will survive updates and will be easily found when the time to delete them come. You will see advises about hot fixes on startup. They close by themselves, and they are there to keep you remembering that there're hot-fixes on your installment. Hot-fixes are workarounds, and can cause as much damage as the ones they fix if something changes too much - but since CxAerospace is stalled and no one can issue a fix without copyright infringement due the licensing terms, that's what I can do for you by now. However, your installment has a new problem, and with Contares this time. This is the patching process for one of the affected parts: [LOG 12:53:51.635] Applying update Contares/Patches/CONTARES_TweakScale/@PART[truss-octo-*] to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-04.cfg/PART[truss-octo-04] [LOG 12:53:53.774] Applying update FMRS/FMRS_MM/@PART[*] to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-04.cfg/PART[truss-octo-04] [LOG 12:54:19.725] Applying update RecoveryController/RecoveryController_MM/@PART[*]:HAS[!MODULE[ModuleAnchoredDecoupler],!MODULE[ModuleDecouple],!MODULE[USDecouple]]:NEEDS[StageRecovery] to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-04.cfg/PART[truss-octo-04] [LOG 12:54:46.894] Applying update TweakScale/patches/NFT_TweakScale/@PART[truss-octo-04] to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-04.cfg/PART[truss-octo-04] [LOG 12:56:27.295] Applying update B9PartSwitch/PartInfo/@PART[*]:HAS[@MODULE[ModuleB9PartSwitch]]:FOR[zzzzzz-B9PartSwitch] to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-04.cfg/PART[truss-octo-04] [LOG 12:56:39.318] Applying update InterstellarFuelSwitch/PatchManager/ActiveMMPatches/IntegratedDecoupler/@PART[*]:FINAL to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-04.cfg/PART[truss-octo-04] [LOG 12:56:40.627] Applying update WarpPlugin/Patches/NearFutureConstructionFix/@PART[truss-octo-*]:Final to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-04.cfg/PART[truss-octo-04] [LOG 12:56:41.130] Applying update WarpPlugin/Patches/OreTanksFix/@PART[*]:FINAL to NearFutureConstruction/Parts/Truss/truss-octo/truss-octo-04 The problem here is that Contares is applying patches for TweakScale on NFT, ignoring the TweakScale default patches. The good news is that this is old news, and was, too, already tackled down here. However… Contares doesn't provides a Github, Bitbucket or any other Code Hosting service, so I'm unable to apply the patches myself as I use to do. The canonical way of handling this is reaching them and asking to fix their patches. In the mean time, you can workaround the problem by deleting Contares/Patches/CONTARES_TweakScale.cfg - the TweakScale ones are the ones ruling the scaling now (as they were applied last), so this is the safest way to handle the mess if you already have ongoing savegames.

So, what do you expect for KSP 2.1'?

Liking to go against the grain, I got fed up of speculations about KSP2 and decided to look about what was KSP 1.0. Or 1.1, whatever. So I wasted some time on Youtube watching old videos. I found this one (between many) worthing of being mentioned.

Interesting revisiting of a George Michael song! I think it's better on Adele's voice, by the way.

Announce TweakScale 2.4.3.3 is now available on Spacedock and CKAN. I forgot to do it yesterday, and today we had some Breaking News to cope with! For non CKAN users, see OP for links, change log et all. Scale safe!

KSP is consistently dying for years already. When it finally happens., could anyone please warn me about? I will probably be busy fixing some bug on TS and will miss the event!