Lisias

Gotcha! [LOG 02:42:19.610] [TweakScale] Version 2.4.3.10 /L But there's something else too - and this appears to be a new: [LOG 03:05:16.438] [TweakScale] ERROR: **FATAL** Part pp.vvmach (Plume Party Vapor Vent Mach) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 03:05:16.439] [TweakScale] ERROR: **FATAL** Part pp.vvmach (Plume Party Vapor Vent Mach) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 03:05:16.616] [TweakScale] ERROR: **FATAL** Part pp.vvmach (Plume Party Vapor Vent Mach) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). [LOG 03:05:16.616] [TweakScale] ERROR: **FATAL** Part pp.vvmach (Plume Party Vapor Vent Mach) has a fatal problem due having duplicated properties - see issue [#34]( https://github.com/net-lisias-ksp/TweakScale/issues/34 ). It's like pp.vvmach was not only being TweakScale applied twice, but the module TweakScale is being applied four times itself too... And, well, apparently it is what happening.... [LOG 02:52:43.150] [ModuleManager] Applying update PlumeParty/Vapor/vent/@PART[pp_vvmach]:NEEDS[TweakScale] to Chrayol_Design_Org/FX/PlumeParty/Vapor/vent/PART [LOG 02:52:43.150] [ModuleManager] Applying update PlumeParty/Vapor/vent/@PART[pp_vvmach]:NEEDS[TweakScale] to Chrayol_Design_Org/FX/PlumeParty/Vapor/vent/PART [LOG 02:52:43.161] [ModuleManager] Applying update PlumeParty/Vapor/vent/@PART[pp_vvmach]:NEEDS[TweakScale] to PlumeParty/Vapor/vent/PART [LOG 02:52:43.196] [ModuleManager] Applying update PlumeParty/Vapor/vent/@PART[pp_vvmach]:NEEDS[TweakScale] to PlumeParty/Vapor/vent/PART I'm unsure about how to proceed. Could you please send also the ModuleManager.ConfigCache ? I want to confirm this is not something on the TweakScale's Sanity Check before pursuing it further... POST EDIT: @moguy16 check if PlumeParty is not installed twice - of if there's some old files lingering when you updated. Try to plain delete everything installed with PlumeParty and then reinstall them from scratch, this looks like rogue oldies lingering on a update. METAR Visual Studio for Mac update just TRASHED my VS instalment, I can't develop anything on the damned thing. Frankly, Microsoft, it's time to serious rethink what you are doing - it's ok if you want to drop support for automatic Updates on the Mac - so just warns us and ask for a manual update, I'll do it when possible. But just trashing my machine while I'm trying to use my not so abundant time it's... it's... it's... (sigh) Damn, I would infringe half forum rules if I don't shut my fingers up.

Well... I got into this, and I just didn't knew where to post it - but I knew I had to post it here somewhere. So a new Thread, for curious things related to Space Program and Space Exploration. I remember a friend of mine bragging his computer was used at NASA when I was a teen, but didn't took him seriously until some time ago, when about 20 years later he sent me this video - still bragging about it. Seriously (sort of), that Amiga computers where really ahead of their time...

Understood. I need some days to assess this new situation - I need to get a compromise between this and everybody else that are running KSP <= 1.7.3 too. I already have a plan for this (i.e., KSP Recall), I need to do some digging on KSP 1.8.0 and 1.8.1 to decide the best line of action.

@kcs123,

Ouch. KSP 1.8.0 has a glitch that was fixed on 1.8.1 (something missing on the prefab for a thingy called UI_ScaleEdit - full details here). Since KSP 1.8.1 came rapidly, with a lot of fixes (including this one), I never bothered to apply a patch on TS for it (I didn't even tried, besides having clues that this is feasible if really needed). My best advise is to update to KSP 1.8.1 - unless 1.8.1 had borked on something really, really important to you.

NOTAM Due some pressuring issues on the country I live, KSP and TweakScale are on slow pace for the past week and probably for one more. Things are under control for now, and me and some other people around here intent to work to keep things this way. Health is fine, no additional worries on this subject besides the usual one (that freaking tooth is starting to be annoying....) I also work from home, so the current quarantine didn't changed things too much for me (other than overloading me with more duties to be carried on together my professional life), and all of this ended up consuming all the available time. However... Support requests will be handled. We are still in business here - only the front-door is shut. I may took some time to answer, but I will answer. --------------------------------------------------------------- As a side note, I would like to invite you to give appreciation and, when possible, support to all the professionals of the Transport Industry on every country. Some of them are going through some bad moments - the Aviation Industry in special, but they are not the only ones. I live not too far away from Congonhas Airport, I'm used to see planes going to land on the horizon from my window (I'm seeing the airport lights right now), and I never thought that I would miss the vision of airplanes going to land - there're fewer of them nowadays.

Now I get it. Deep stress is known to negatively affect the immunological system. But I'm unaware of any study specific to this detail, all I had read are opinions from physicians based on personal experiences.

COVID19 is essentially a pneumonia that spreads like a flu. The information I have to this moment says that the root cause of mortality is the immunological system. The persons at most risk are the ones with disieses that compromise the immunological system, as cardiorespiratory illness, diabetes, people with transplants taking immunosuppressors, you name it. So, assuming I understood correctly what you mean, the clearness of mind is irrelevant for this disease. An Alzheimer's victim with a strong immunological system, assuming we have all the data for the SARS-CoV-2 M.O., should withhold the COVID19 better than an elderly those body is aged enough but is perfectly lucid.

Kub.

Today we lost Albert Uderzo. "father" of Asterix, by a heart attack at 92. Farewell, you made my childhood way happier.

It's WAY too soon to forget about this damned thing and carry on our lives, but.. Sit tight and fasten your seat-belts - respect quarantine where it's due. Things are expected to get better as the Summer come on the North Hemisphere.

Lebowski. Poland. Excelent.

The ground sinking Kerbal is also stock related. I think it's fixed (or kinda, read someone complaining about how it was fixed) on 1.9.1, but I didn't tested it myself - found a nasty showstopper for me on the 1.8 and 1.9 series, and ended up going back to play on 1.7.3 .(I enjoy to play KSP, not to endlessly hunt and work around bugs on it). ------ post edit ----- Weirdly, one word is missing on a key argument of mine on a previous post (I use to make a lot of typos, but a whole word appears to be a new...). I tried to fix the post, but more weirdly, that post is locked and I can't edit it. Well, I fixed the argument above, the missing word ("time") is emphasized. ------- post post edit ------- Well, the edit lock on that post was lifted. So I fixed it there too.

What's serious from the development point of view may not be seen as serious by the end-user. The user cares about the results, the thing is working, it's fine. We, developers, on the other hand, should worry about a thing called maintainability, that it's the ability to correctly... maintain ... the damn thing working in the future. In a nut shell, maintainability is what we need to have in order to avoid a thing called bit-rotting. As an example, that new annoyance on the nav-nodes. Every time you enter the Navigation Scene (on 1.9.x), all your nav-nodes are "gone" - until you manually find one and select it, where all the nav-nodes are "remembered" suddenly. From the user point of view, it's an annoyance. From my point of view, this is smelling bit-rot - the developers are losing control of the code-tree, as they are forgetting to do some things (as initialise some data structures on some events), relying on some deep buried code to do the thing in a way nobody knows or understand. Such a mishap is obvious, it's plain impossible that KSP 1.9 were gone gold without anyone knowing about this. So, by inference, they choose to let it go as is because they don't know how to fix it or don't have the [ time ] to learn how to fix it (what's just an explanation for the reason they don't know how to fix it). The problem with this approach is that you end up forced on developing new code over misbehaving code, and sooner or later you are drawn into a corner because the new developed code works only over misbehaving code, and you can't fix the misbehaving code (because it would break the new developed code that depends on the misbehaviour to work). And so you need to code a stunt (known as "gambiarra" where I live). But since such "gambiarras" are meant to empirically fix problems without caring for anything else, once such "gambiarras" pile up, you have a system full of conflicting requirements - you can't change one thing because a "gambiarra" depends of it, and you can't remove that 'gambiarra' because it fix something else that you don't know how to fix, or worst, can't be fixed because it would break another "gambiarra", and so you are lock on a vicious cycle. Don't expect too much. There're visual and life quality enhancements on KSP 1.9, but the worst bugs are still there (as well some new ones). Follows a small resume from the ones I know about (links to the reporter): https://forum.kerbalspaceprogram.com/index.php?/topic/191967-kerbal-space-program-191-is-live/&do=findComment&comment=3751656 https://forum.kerbalspaceprogram.com/index.php?/topic/191967-kerbal-space-program-191-is-live/&do=findComment&comment=3750122 https://forum.kerbalspaceprogram.com/index.php?/topic/191967-kerbal-space-program-191-is-live/&do=findComment&comment=3750642 https://forum.kerbalspaceprogram.com/index.php?/topic/191967-kerbal-space-program-191-is-live/&do=findComment&comment=3748676 this one is more than annoying. I have to play this thing on a pretty low texture quality, what's ok for the overall game (I use a 1280x960 resolution anyone), but its completely horrible on the U.I - I just don't known when a cheat is active, because the check-mark is so blurred that it became transparent. https://forum.kerbalspaceprogram.com/index.php?/topic/191967-kerbal-space-program-191-is-live/&do=findComment&comment=3748407 https://forum.kerbalspaceprogram.com/index.php?/topic/191967-kerbal-space-program-191-is-live/&do=findComment&comment=3748415 This one appearts to confirm what I said above, by the way: https://forum.kerbalspaceprogram.com/index.php?/topic/191967-kerbal-space-program-191-is-live/&do=findComment&comment=3748416 https://forum.kerbalspaceprogram.com/index.php?/topic/191967-kerbal-space-program-191-is-live/&do=findComment&comment=3748456

Coming back to life.

In your case, nope. This, unfortunately, is one of that nasty cases that can corrupt savegames if you uninstall CX Aerospace with living crafts using the affected parts. You risk getting your crafts, both on craft files but also living one on the savegame, to get some of the misbehavirous I described here: https://github.com/net-lisias-ksp/TweakScale/issues/34 Unfortunately,. you need to make a choice: delete CX Aerospace or apply the patch that it's already supplied on TweakScale's distribution zip. (And since CX Aerospace cannot be fixed, I expect more problems in the future from it if any new add'on arises using assets from that same author...)

Hi! A bit late to the party. While @Azic Minar did a Quality Assurance check on your instalment, allow me to give some hints about Quality Control Install ZeroMiniAVC, or if you are on a UNIX machine, find ~ -name "MiniAVC.*" -delete . (this will get rid of every single MiniAVC on every KSP you have on your account) This DLL is outdated, and currently a source of problems on KSP >= 1.8 Deleting everything is the best line of action, use KSP-AVC instead. The two FATALITIES (bluedog.CXA.APAS.A.L04F and bluedog.CXA.APAS.P ) are about double patching. It's a glitch on CX Aerospace already handled last year. Boy, that one gave me a run for my money. TL;DR : the patches for CX Aerospace were made when all the assets belonged to a single author, but then some assets were passed to third parties, and the way CX do its patches became not only obsolete, but also a source of problems as it started to apply patches to assets from unrelated add'ons because they were authored by a dude. As far as I know, CX was not fixed (and probably never will - the licensing terms are terribly restrictive), so you will have to apply a HOTFIX. On the TweakScale zip file, take this file: Extras/TweakScale/HotFixes/CxAerospace--Bluedog_DB.cfg And copy it to a place where you will surely remember it later. I recommend __LOCAL/TwealScale/Extras/HotFixes . This will prevent you to forget where in hell you shoved the stunt, and also prevent some manual or automated update to delete the patch - what could be damaging to your savegames. Cheers! ( and Scale Safe! )

High Hopes.

"Safety first, Cooper!"

As safe as it's possible. This crisis is more a social/political/economical one than a health one around here. We are on Summer here at South Hemisphere, the higher temperatures helps, and helps a lot - what Winter is reserving for us is still to be seen, on the other hand. The behaviour of people under the crisis, however, is worse than the crisis itself. Ignorance and selfishness are a deadly combination.

I'm fighting this thing for some time, and managed to get the history of it. The Module AA uses to do its thing extends (an OOP term) the stock ModuleControlSurface. The problem is that by doing it, the module itself is renamed on the craft, and so the default values are reapplied. Initially things worked fine, but somewhere in 2014 (if memory serves me right) something inside KSP changed and so this misbehaviour started to bite us. In a nutshell: the ModuleControlSurface is renamed SyncModuleControlSurface. New crafts and savegames, after installing AA works fine because everything is created from scratch, using SyncModuleControlSurface. But older savegames and craft gets the control surfaces reset to default because the ModuleControlSurface data is ignored, and a new SyncModuleControlSurface one is created with default values. There's a cumbersome workaround for it: using an editor, open the craft and savegames (after making backaups!!) and replace every instance of "ModuleControlSurface" to "SyncModuleControlSurface" - this will "import" your artifacts to be used on a KSP with AA installed. The other way around is also possible - exporting savegames and crafts to a AA-less instalment is essentially doing the inverse: replace every SyncModuleControlSurface to ModuleControlSurface. An automated tool to do that would be the ideal solution, however.

It's the price we pay for inheriting their work. You know, someone had to work and earn money and pay taxes before you had born. Just Imagine how it would be your life if they had choose to burn all that money with iPhones and travels instead of applying on investment funds and paying taxes... Wonder what would be your country if every elderly man and woman just leave to live somewhere else, taking all their money with them... We live on a Consumerist Society. We need consumers to be alive, otherwise we would not have an Economy to be rebuilt. Living People are the reason we need an Economy at first place. It's hard to understand when we are young (been there, done that). But as we grow older and start to understand how things really work, we change our minds. Be patient. Be wise. Your generation will have to cope with things that my own generation just knew from history books.

Tonight I decided to put KSP 1.9.1 on test on something I value very much : water ships. I'm toying with hydrofoils since KSP 1.4, maritime crafts are my second most favorite type of crafts - hydroplanes? Just love them. So I made this ship, a hydrofoiled MK3 fuselage. 64 PAX and 2 pilots being pushed over the waves by 4 Wheesleys. It worked perfectly on KSP 1.7.3, beautifully surfed the Kerbin seas at > 70 m/s. Not bad for a 53 tons fatty lady. But... Why in KSP 1.7.3? I wasn't going to probe 1.9.1? Well, I did. And got his: The freaking thing just took off and reached 5K high at Mach ~1. I don't know exactly what's happening, but apparently wet fuselages and wet lifting surfaces lose drag. And perhaps weight? So I made this stunt to check the facts: And yes, this time I got drag, the thing didn't got beyond 200m/s - but it took off the same. The (almost) very same craft behaved absurdly differently on KSP 1.9.1, what again confirms my original thesis that it's plain impossible to import a reasonable complex KSP < 1.8 game into current KSP. it just doesn't worth the trouble, things changed too much on essential, primordial behaviours on the game to the point I consider migrating savegames from KSP < 1.8 a liability. So I will just won't.. I'm currently reevaluating my options. There are real value on KSP >= 1.8, better graphics and faster physics. And some new cute and usefull parts. But none of it worths my savegames, I'm playing them for 2 years for a reason. My verdict is that KSP 1.9.1 is almost good enough for newcomers (the glitches are annoying!), as long they stay away from the water and don't mind (too much) airplanes. Anything that splashes down will behave in an absurd way, harming the game if you enjoy KSP by what it is (was?) - a physic simulation with some resemblance with real physics. On the bottom line? I'll handle KSP >= 1.8 to keep my Add'On working and supporting them, but my gaming will remain on 1.7.3 . Crafts on my site, one of them on Kerbal-X.

Use your 3D glasses.

Source: https://divinity.yale.edu/news/15000-year-old-bone-and-fall-2013-issue-reflections