Lisias

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!

What doesn't means it does it properly. There're some inconsistencies on the Linux/MacOS port of Unity that I find…. interesting, to say the least. Things are not perfect on Windows neither - the Mono's JIT are playing havoc on some especial circumstances on Windows machines. Initially, I though it would be confined to the XInput stunt, but I saw one or two output_log.txt that appears to hint it can be a broader problem . Squad made that agreement. KSP2 is Star.Theory land now. I don't think they will need any push on selling KSP2, by the way. The game can sell by itself nowadays - and I expect them to avoid cannibalising the KSP1 eco-system, at least for while. That said, my expectations are so good as yours. All of this are just educated guesses.

For the best and for the worst, will be Unity. Not a clue about what version.

Right now, I hope they fix all the problems for Linux and MacOS, as I think these ones can be their best shot as KSP 2.0 is coming (and it will be Windows only, at least for some time). Interesting times ahead.

Where is the link for the preorder? (the Joysticks will work this time, right?) — POST EDIT --

Firing up KSP in 3..2… uh… No, work time. Damn. I want to bring to your attention the work being done by the wheels!

#BlameUnity is an explanation, not a fix for the problem. They are right in blaming Unity. The problem is not workarounding the problem (assuming it's not a fixable one) -- post edit -- That said... I'm not having so much issues with wheels as I see here. I'm even getting good results on scaling them (using TS beta), and this is solving a good part of my wheels and landing struts problems. Keep the wheel stress below 0.5 or 0.4 at rest, and below 1.0 on rolling and even the tendency for running off the runway is minimised (over stressed steering wheels pops and trembles, with the same results as on a real vehicle - the thing drifts from the intended course). I think that the worse thing about them is being unable to anticipate, on SPH/VAB , how the wheels will behave with the current settings.

I have about 1.500 hours of registered hourson Steam, at least the same on unregistered hours, and I still borking on my Mün landings. The worst thing on KSP, as it appears, is me.

When you get the time (and the mood), publish the KSP.log again and send me a link. I wanna to register these parts in order to help me to priorize the tasks I need to get them working. (good to know if worked! And remember - "A landing from which you can walk from is a good landing. A landing in which you can reuse the same aircraft is a excellent landing!!!") It means that you need to publish the whole KSP.log, otherwise I could not detect who is the guy double patching the part. Without the full KSP.log, I don't know who are messing up - I can just see the one being messed with. All I can do is to guess. Perhaps you have the same problem as this guy, but without further information, it's a wild guess.

Hi!. Brazilian here. Welcome. Let's see what's bitting your KSP. Older KSP will be a problem. Most Add'Ons don't support 1.4 anymore, so we will need to apply Hotfixes on your KSP installment. You will have to learn how to create directories, unzip files and copy files between directories Are you ok with that? I will flood this post with technical information. Don't worry, you don't need to cope with that. I do that because as the time goes by, I forgot what I was doing here, and so that information will help me to remember. It's a very heterogeneous collection of affected parts. Some, inclusively, will show a Warning later because TweakScale doesn't support them yet (about 9 on a Stock KSP). You can ignore that Warning, but if the counter rises, I ask you to hint me here about the affected parts so I can support them. Interesting… It's as if every Making History part was double patched. I think I know whats happening ! And yep… It's TweakScaleMakingHistoryConfigs again. You got lucky, it's pretty simple to fix it. Tell CKAN to delete the Mod TweakscaleMakingHistoryConfigs. This will fix all that double patching on the Making History parts. It's not impossible that some other problems, hidden by this one, arises. Kick me here if that happens. Only the "Houston" messages are really problems that need me to fix something right now (these message has a Red Title). For some time, Warnings and Advises (Yellow Titles) will be issued while I fix some things on my side, but you can ignore them for now. But if the counters get bigger as you install things, would be helpful if you publish the KSP.log so I can register that parts and see if there's nothing new in need of being updated from my side. In time do you know S.A.V.E.? You will need to learn to manually install it (there're old versions for KSP 1.4!), but I think it's good to have it - or some other Add'On that does this job. Relax. Most of people here don't talk English fluently, and mine is far from being perfect. If you find hard to express yourself in English or are unsure if you translate it correctly, write both - what you would had written in your mother tongue, then your best effort to translate it to English. Someone will come to the rescue if anything is wrong. “Navegar es necesario, vivir no es necesario”, Pompeyo Kerman.

Hey, are the guys from Squad expanding their business??? https://www.kspconstruction.com

Well, last week L Aerospace had a serious settle back. Well, the passengers and crew are still there, waiting for the rescue. What will be somewhat messy, as having a crash with survivors caught everybody with their pants down (we are not used to this!), and we are facing some…. difficulties… on organizing and executing the mission. The Rescue Brigade Committee just release report about:

ROADMAP Fellow Kerbonauts, The TweakScale 2.4.3.x series is, finally, near the EoL. I think it will be [one two] three (!) more build release to fix any small bug or add some minor improvement, and unless something else happens, that will be it for this troublesome 2.4.3.x. I want to thank every one of you that helped me to diagnose all that glitches, bugs and misbehaviours in which TweakScale was, directly or indirectly, involved. Every bug report, every complain, every log, helped me to detect, diagnose and fix a huge amount of bugs and misconfigurations on the whole eco system, what ends up being good for everybody. I'm pretty happy with the ending results besides the trouble, we have a way more stable gaming installment nowadays. As nothing good cames cheap, we have a somewhat whiny game setup too. Oh well. What I want to share with you now is what to expect from the next two minor TweakScale versions, 2.4.x and the yet somewhat far 2.5.x . 2.4.4.x : Unbreaking Ground Parts The whole 2.4.4.x releases will be focused on properly supporting what's now unsupported from Stock, DLCs and some heavily used Add'Ons, as Firespitter (and probably some others, as you suggest and it's feasible). Deprecated and or redundant patches will be removed from the distribution, so no more stomping the fellow Add'On Author's toes [done on 2.4.3.5 due the potential toe stomping fest]. Patches to Add'Ons under my control will migrate to them - I intend to declutter TweakScale and minimize the surface of exposure. And as my Add'Ons gets updated, it will avoid the need to update TweakScale too - hardly a bad thing. The sole purpose of the 2.4 series is to zero the Warnings and Alerts (as it was the 2.4.3.x to zero the FATALities), both on screen as in the KSP.log. At least for the Add'Os being maintained - there're not too much I can do for stalled ones besides applying Overules and Hotfixes, and these will not need necessarily a dedicated release - not to mention that they will still be lingering on the future TweakScale versions. 2.4.5.x : Old parts, New tricks Renewed support for currently (partially) supported parts will be updated - in special, I want to make Wheels correctly scalable again. This, as usual, will not be free - by correctly scaling up the Wheels, we end up correctly scaling down them too - and so things can break on games with tiny little wheels that now are too strong for they sizes and will became weaker as they should. So there's a chance to postpone these features or to make it optional, as I made with the Input resource of the ModuleGenerator. Let's see what happens... While one or another mistake will probably bite our SAS, I expect a very smooth transition for the whole series. 2.5.x : "My Kraken…. It's full of ":FOR"s…. This one can be troublesome again. My apologies. The root cause of some of the worse problems that plagued parts using TweakScale in the last years (yeah… years) is rogue patches. However, TweakScale also didn't did its part of the bargain to help the fellow Add'Ons Authors - currently, it's not possible to use :BEFORE and :AFTER on TweakScale, as it's still on the "Legacy" patching support. A lot of mishaps would had been prevented by using that two directives. However, they :NEEDS need TweakScale using :FOR on its patches, what would remove the TweakScale from the Legacy patching - and this is where things start to go through the tubes. Almost every Third Party Add'On on the wild, now, relies on TweakScale being in the Legacy with the Add'Ons ending up, after some blood, sweat and tears, reaching a fragile equilibrium on the patching - as an airplane flying in its absolute ceiling. A Kerbal farts somewhere in the plane, the thing stalls. This aphorism describes pretty well the current status quo, by the way. There's no easy way out of this mess: I don't do it, we will live with patching problems for the rest of our lives - on every install of a new Add'On. And sooner or later we will need another round of a new incarnation of the 2.4.3.x series. Not funny. I do it, and we will have a new flood of KSP.logs around here. So, in the end, it's a matter of choosing the KSP eco system we want to have - and I have a hard time believing that KSP players like their rockets anchored in the 3D space, or having the statics exploding for no reason. But, as already is usual, no savegame will be left behind. The (current) schedule is here. Thoughts? -- -- -- POST EDIT -- -- -- Superseded by the new road map.

Hi! There's another Add'On (or "Mod") that I recommend to use. S.A.V.E.. It's for automatic backups of your savegames. Now and then some interactions between different Add'Ons can cause misbehaviours on the game . Using a backup Add'On will make sure the misbehavior will be a nuisance, and not a trouble.

It's right to assume that when people try to upload a too much big of a file (as the KSP.log) into a post, that thread stops being indexed on 'My Activities" (and perhaps the front page)? I also think that the offending post is not shown on the thread, but I'm unsure.

Sorry for that. Let's fix this thing so you can enjoy the FdS WeekEnd (sorry by your first post being motived by a FATALity but you came to the right place. No savegame is left behind around here!) I gave a rapid look in which you posted, and that pesky duplicated properties are surely due double patching, i.e., when two different patches ends up applying a patch for TweakScale on the same part. This is a problem because uncontrolled patching leads to non-predictable results. You change something, the ordering of the patches changes and then TweakScale suddenly apply different rules on flying crafts - nasty results. This is the reason I declared this problem as FATAL, as it would ruin the savegames in which such parts are used. And I cannot automatically fix the problem, as I don't know which patch would be the right one without eye balling the thing. In order to help you., I really need the full KSP.log. Most of the time, providing me with the GameData/ModuleManager.ConfigCache also helps me to provide a patch to fix things on your rig when needed, so I ask you to post it in advance. It saves time if I come to used it. Google Drive and Dropbox are nice file sharing services, and most of the time is which people is using here to send me these files. But you can zip them and post them on this Github Issue if you have an account there (if not, don't bother. Open a dropbox or google drive account, they will be more useful to you on the long run). — — — EDIT — — — Are you using the latest versions of TweakScale and SXT? SXT was recently updated, and most of the fatality parts on your KSL.log are from SXT!

Well… I changed my password on a Chrome browser, I was obviously unlogged on the Safari. Trying on my phone it had synced the password and saved me the hassle to type it on the phone; I'm still logged since, after logging again on Safari. Occam's razor hints me something on Firefox (had it being updated recently?) or perhaps some of the plugins (some of them were updated?).

Forum bugs is on the wild. What browse are you using on your devices (just for curiosity)? I noticed some people using Duckduckgo lately, and this browser is a bit agressive on privacy protection. However, some sites rely on some technics to keep track of where you are logging and perhaps some of that privacy measures would be triggering something on the site's code that leads it to revoke your logged credentials to make sure nobody is trying to steal your credentials. Are you noting some other inconsistency? I noted that URLs, locations, etc on my (and some other's) profiles are being shown as "array", and some of the TweakScale thread posts are not being shown on my Activities (not in the Threads I posted, neither on the Threads I started) besides being reachable by the Search. I'm using Safari, Chrome and Firebird on different devices, so this rule out a browser issue for me.