Lisias

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.

Multiplayer é complicado porque as pessoas precisam jogar todas ao mesmo tempo, e pelo menos eu sou um que nunca tenho mais de 30 minutos de uma vez pra brincar. O KSP às vezes fica ligado o dia inteiro em pausa, e eu volto lá umas duas ou três vezes pra uns 15 ou 20 minutos de missão. Já sobre jogos mutliplayer… Não tem jeito. Pessoas diferentes se divertem de forma diferente. Eu sou zoeiro, me divertia mais dado razante em vôo invertido num 747 nas pistas de pouso nos meus tempos de Flight Simulator que voando de cidade em cidade. Uma vez pousei o 747 num porta-aviões - só não consigo lembrar qual foi o simulador (crashei, óbvio, as asas bateram na torre). Já meus amigos eram "sérios", um fazia as vezes de ATC e ficava no chat do jogo ordenando os poucos e decolagens. Adivinha quem não se continha e dava "Mayday, Mayday, Mayday" no pior momento possível?? Então as regras precisam ser definidas de antemão - e o código do jogo precisa "enforce-them" à ferro é fogo. O que é um dos trampos mais chatos de fazer num jogo, então quase ninguém faz. Se o Luna não fizer algo assim, vai se estrepar igual ao Dark.

Isso me deu algumas idéias… Que bom que hoje é sexta, hoje de noite (se o TwekScale deixar… hehehe) vou testar umas maluquices aqui do meu lado do cable modem.

And now for something slightly newer.

Been there, done that. But I got "lucky", and solved it the only way it works. I quit. She (as me at the time) got into a terribly nasty situation: responsibility without authority. Having some training on PMBOK, I quickly recognized what your wife needed to learnt the hard way and knowing the aftermath in advance, I turned the table and did it at my least inconvenience, not their best convenience. This is a loose-loose situation, there's nothing your wife could had done that would had prevented this outcome. On the bright side, your wife did the second best thing about the issue: she stood her ground and got fired by trying to do the right thing. As the word spreads, this eventually will caught the attention of someone that knows the trade. Once your current job is going down, you need to work thinking on your next one. Good managers pave the way for their led ones. Bad managers pave the way for themselves. These guys are social climbers, they need to manage every little aspect of the work so they can claim the merit for themselves. She was framed. Bad management uses the feedback process to pinpoint dissidents and punish them. This company is over, you get what you promote - no one will ever try to ask for help about anything on that sheet perforation again. The message was crystal clear. On the bad side, once that nice piece of used paper starts to hit the turbofan, she will be blamed for it for some time. There's not much anyone can do about, as trying to fight this, in my experience, usually lead to worst results. It's better to let them badmouth you on something that you did right (as it eventually will be realized), instead of defending yourself and taking the risk of the offenders looking for something that you may had be done wrongly on the past, and using it instead. And since everybody make mistakes, they will find something. It's the reason the best line of action when you detect this loose-loose situation is to just leave, the fastest you can. It's the only way they manage to "outperform" the "competition" - by getting rid of them until no one better stands. I will refrain on further commenting on this matter, as Forum rules forbids political discussions here. In a way or another, the Company will face some really harsh problems in the near future. Boeing style. if by some reason this company works on something that involves Public Safety (transport, mining, construction, etc), find a lawyer and take some precautions on the matter as soon you can. I'm serious - better safe than sorry. These situations usually leave a foul taste on the mouth. I got a serious burn-out, took me almost an year to be fully recovered. Of course, money talks and from the professional point of view, it's better to be hired for some time when the bullets start to fly on the previous job on a Witch Hunt. This will shield her, as the current coworkers, by knowing her for some time by then, will be able to detect the badmouthing and the reasons behind it. If they are smart enough (and wants to), they can use it to steal some clients from her former employers by diligently (but discretely) informing the clients that some of the people that were there when things worked fine now work for them. It works. I see this happening all the time. And this explains why the youngsters on management needed to get rid of her. She was the one risking getting into higher management as time passes, not them. It's, really, an impression. The problem is a bit worse. Somehow, we, as a Society, are allowing a cast of people to weaponize social behaviour against other people as a way to get what they want. It's, effectively, a new cast - as only them are allowed to use such weapons.

These ones are warnings. There're some parts that doesn't have TweakScale installed (to tell you the true, TweakScale uninstall itself from the part) for lack of proper support, so these parts are not scalable yet. The Engine Plates and Tubes have a thing called ModuleVariantPart with mass, and TweakScale chokes with the mass, so TweakScale removes itself from the part to prevent problems. There are a few other parts from other Add'Ons with similar problems - all of them safe to be used, however without TweakScale support. Yet. These parts will be supported on the 2.4.4.x series. These small annoyances are useful because as people get here with logs like yours, I can look and then priorize the parts that need to be worked first. These 9 ones are from Making History (if memory serves me well), and yeah, will be the first ones to be tacked down.

Now I understand! The transparency is done using the same technique used by the Interior Overlay!

The Barn! That would be something I would throw some money into! Specifically on a career mode starting from the very first rocketing experiments!

I would throw some money on The Barn. Hell of an idea, I would like to start an Career that way

"My SeQueL... It's full of bug-reports!"

Thanks for the heads up! I just fixed it. But this time, I'm innocent! Bitbucket had problems last night with GIT LFS, that is something not too unrelated to github's way of storing attachments. I wonder if something similar happened to github? I clearly remember **NOT CLOSING** the page while uploading (yeah, learnt it the hard way). Interestingly, imgur had just failed on me too. The damned thing unlogged me after posting this image and it's refusing my logins. [edit: And then I asked for a new password, got the email, clicked on the link and imgur page's appaers WITH ME LOOGED. Whatahell???] Well… one more step on the check list - be sure the github download is okey. https://imgur.com/a/Px4d19o

Announce. Minor Release 2.4.3.3 is on the wild. Just some typos fixed and added support for the new Cryo Engines from Nertea's. 2019-0814: 2.4.3.3 (Lisias) for KSP >= 1.4.1 Added support for hot-fixes - handcrafted patches to brute force a correct path when the normal way is not possible - as when an unmaintained ARR Add'On is involved on the mess. New hot fix for CxAerospace:Station Parts breaking Bluedog_DB. Links on the OP. CurseForce and Spacedock will be updated on the Weekend. — — News — — TweakScale 2.4.3.3 know recognizes and keep track of HOT FIXES. A Hot Fix is a hand crafted patch that fixes by brute force patching problems, forcing the original intended result for a given KSP installment. The difference from an overrule is that Hot Fixes don't break compatibility with sane installments, so you can start new savegames and share your crafts without worries. However, a Hot Fix is highly specialized to a given situation, and there're no guarantees that it will behave correctly as the affected Add'Ons are updated by the maintainers. So, a pesky Advise will popup when Hot Fixes are detected to prevent you from forgetting a old Hot Fix on your installments. In an ideal World, Overrules and HotFixes would not be necessary. These are temporary workarounds to keep KSP installments sane enough to keep going. Apply Hot-Fixes or Overrules only when recommended by me, LisiasT. It's ok to reach me asking about if you think it will help you, but please confirm with me first. These things can cause as much damage as they can fix them. Each Hot Fix will have an URL associated pinpointing to the Post where the problem were detected and fixed for traceability.

Hi, @cxg2827. Some people are still using your Add'On (and it's pretty easy to see why - if we manage to reach an agreement about what follows, I'll be another one! Excellent work!), but we are now facing some issues and I will need your help on it. Your patches were made for an environment where only you would be using parts you authored. With your decision of allowing some hand picked Authors to use them, your TweakScale patches (I'm the current maintainer of TweakScale, by the way) are being applied on some other Add'Ons by accident, as you can see on this post on TweakScale's thread. Would you consider a new maintenance release of your Add'On with the MM patches fixed? The best solution for the problem is, indeed, a new release of CxAerospace with the patches fixed, and may I suggest using also :FOR[CxAerospace] (and :NEEDS[<dependency>] where applicable)? We could check for any problems with the others Add'Ons and fix them too - so people that are still running savegames with your Add'On could keep going on. I'll gladly help on anything you need. No strings attached. Cheers!