Lisias

Members
  • Content Count

    2,720
  • Joined

  • Last visited

Community Reputation

2,738 Excellent

About Lisias

  • Rank
    Boldly crashing what no Kerbal has crashed before!

Contact Methods

  • Website URL Array

Profile Information

  • Location Array
  • Interests Array

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. They need some management. Whatever they have now, is worse than bad management!
  2. Yep. And I was fixing my argument using your data! (language barrier and context-less communication channels bitten us! Was the use of the "so" the problem? Honest question!)
  3. Well, só Junos start to choke when the instake airspeed reaches Mach 1.25 (more or less), until the point they get a flame-out.
  4. Use a Syntax File for YAML on your Editor. This will allow you to "Fold" and "Unfold" (also known as "Collapse" and "Uncollapse"). making easy to find yourself on the hierarchy. Use it for .sfs , .cfg and .craft files.
  5. Realize how in hell Douglas Adams found the 42.
  6. This didn't worked as I expected….
  7. The root part is the very first part on the craft. Crafts on KSP are "Trees" (a programming data structure), it looks lke this when drawn: The top node (1) is the root. The bottom ones (8, 9, 10, 11, 13 and 14) are "leafs". This is a binary tree, because each node can have only 0, 1 or 2 "sons". KSP use n-nary trees, i.e., has no limits about the quantity of "sons" a node can have. Being a tree, a "son" can have only one "father", and you can't have circular references - i.e., a node cannot reference a brother, a cousin, or any ancestral. You can't link 14 to 3 neither 4, for example. EAS Struts is a way to overcome this limitation. On a craft file, the ROOT is the part that has no parents, but has "sons". I suggest to edit the craft on VAB/SPH, and then cheat it into the space for testing, instead of trying to hot edit a living vessel. Using the reroot tool is way more convenient. As I said before, I only successfully rearranged small crafts (about 5 to 7 parts), bigger than that it's just too much hassle to do manually. At least on the craft files I edited (it's some KSP versions since the last one), its the first PART on the craft file. Each "father" has 0, 1 or more "link =" data, linking to a son - so a root part is a part where nobody has a "link =" to. You can edit the tree by editing that "link =" thingy. But yet, the reroot tool is the bast way to do that. I explained all of that to you so you can understand what the tool does. So the weight of their "sons" is too much for them. You need to auto strut some of its sons to root too, so they can share the load. Using auto-strut on everything can bite because auto-struts adds more load on the physics engine, and when you overload it the wobble happens, because KSP tries to cut some corners to save framerate and then suddenly the physics engine got flooded by "over-shoots", and eventually one of that overshoots ends up being bigger than the joints can withhold.
  8. I remember it as it was 30 years ago.
  9. THIS is what it should be about!
  10. The experiences the channels I watch says exactly the opposite. Great. Another A.I. believer. Still on this line of argument? Dude, do you know that making assertion that could be easily denied by a simple Google Search doesn't make your opinions exactly valuable, right? Google had obliged themselves to pay for content once the youtuber applies for Revenue and it's Accepted. It's a commercial relationship. I strongly suggest you to better inform yourself, please. How about this one on UK? https://www.copyrightuser.org/understand/exceptions/parody-pastiche/ USA has the Fair Use, and even Brazil (with a somewhat draconian copyright law that tries to make amends to a terrible past fro the 70's and 80's) has something like that. If you are on EU, you may want to read this: https://www.copyrightuser.org/understand/exceptions/ for a full essay.
  11. Got it. [LOG 17:50:01.838] [TweakScale] INFO: WriteDryCost: Started [LOG 17:51:16.772] [TweakScale] INFO: WriteDryCost Concluded : 1528 parts found ; 0 checks failed ; 0 parts with hotfixes ; 0 parts with issues overruled ; 1 Show Stoppers found; 9 Sanity Check failed; 855 unscalable parts. No big deal, just one FATALity: [LOG 17:51:16.461] [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 ). But this is a new one! Let's improve our TweakScale knowledge base a bit! [LOG 17:40:24.198] Applying update PlumeParty/Vapor/vent/@PART[pp_vvmach]:NEEDS[TweakScale] to PlumeParty/Vapor/vent.cfg/PART[pp_vvmach] [LOG 17:40:24.201] Applying update PlumeParty/Vapor/vent/@PART[pp_vvmach]:NEEDS[TweakScale] to Shuttle Orbiter Construction Kit/PlumeParty/Vapor/vent.cfg/PART[pp_vvmach] [LOG 17:40:28.101] Applying update Shuttle Orbiter Construction Kit/PlumeParty/Vapor/vent/@PART[pp_vvmach]:NEEDS[TweakScale] to PlumeParty/Vapor/vent.cfg/PART[pp_vvmach] [LOG 17:40:28.102] Applying update Shuttle Orbiter Construction Kit/PlumeParty/Vapor/vent/@PART[pp_vvmach]:NEEDS[TweakScale] to PlumeParty/Vapor/vent.cfg/PART[pp_vvmach] [LOG 17:40:28.103] Applying update Shuttle Orbiter Construction Kit/PlumeParty/Vapor/vent/@PART[pp_vvmach]:NEEDS[TweakScale] to Shuttle Orbiter Construction Kit/PlumeParty/Vapor/vent.cfg/PART[pp_vvmach] [LOG 17:40:28.104] Applying update Shuttle Orbiter Construction Kit/PlumeParty/Vapor/vent/@PART[pp_vvmach]:NEEDS[TweakScale] to Shuttle Orbiter Construction Kit/PlumeParty/Vapor/vent.cfg/PART[pp_vvmach] [LOG 17:40:51.786] Applying update kOS/kOS-module-manager/@PART[*]:FOR[kOS] to PlumeParty/Vapor/vent.cfg/PART[pp_vvmach] [LOG 17:40:51.786] Applying update kOS/kOS-module-manager/@PART[*]:FOR[kOS] to PlumeParty/Vapor/vent.cfg/PART[pp_vvmach] [LOG 17:40:51.793] Applying update kOS/kOS-module-manager/@PART[*]:FOR[kOS] to Shuttle Orbiter Construction Kit/PlumeParty/Vapor/vent.cfg/PART[pp_vvmach] [LOG 17:40:51.793] Applying update kOS/kOS-module-manager/@PART[*]:FOR[kOS] to Shuttle Orbiter Construction Kit/PlumeParty/Vapor/vent.cfg/PART[pp_vvmach] [LOG 17:41:03.758] Applying update B9PartSwitch/CopyEventsPropagator/@PART:FOR[zzzzzz-B9PartSwitch] to PlumeParty/Vapor/vent.cfg/PART[pp_vvmach] [LOG 17:41:03.758] Applying update B9PartSwitch/CopyEventsPropagator/@PART:FOR[zzzzzz-B9PartSwitch] to PlumeParty/Vapor/vent.cfg/PART[pp_vvmach] [LOG 17:41:03.767] Applying update B9PartSwitch/CopyEventsPropagator/@PART:FOR[zzzzzz-B9PartSwitch] to Shuttle Orbiter Construction Kit/PlumeParty/Vapor/vent.cfg/PART[pp_vvmach] [LOG 17:41:03.767] Applying update B9PartSwitch/CopyEventsPropagator/@PART:FOR[zzzzzz-B9PartSwitch] to Shuttle Orbiter Construction Kit/PlumeParty/Vapor/vent.cfg/PART[pp_vvmach] [LOG 17:41:04.615] Applying update Kopernicus/Config/SolarPanels/@PART:FINAL to PlumeParty/Vapor/vent.cfg/PART[pp_vvmach] [LOG 17:41:04.617] Applying update Kopernicus/Config/SolarPanels/@PART:FINAL to PlumeParty/Vapor/vent.cfg/PART[pp_vvmach] [LOG 17:41:04.662] Applying update Kopernicus/Config/SolarPanels/@PART:FINAL to Shuttle Orbiter Construction Kit/PlumeParty/Vapor/vent.cfg/PART[pp_vvmach] [LOG 17:41:04.663] Applying update Kopernicus/Config/SolarPanels/@PART:FINAL to Shuttle Orbiter Construction Kit/PlumeParty/Vapor/vent.cfg/PART[pp_vvmach] Well.. This is a new. There're many patches being applied to pp_vvmach, every one of them twice! This is a new one, indeed! Looking into the KSP.log, I realized that there are more than one copy of PlumeParty on your installment! [LOG 17:40:14.583] KSP-AVC -> D:\Steam Games\steamapps\common\Kerbal Space Program\GameData\PlumeParty\Version\PlumeParty.version [LOG 17:40:14.583] KSP-AVC -> D:\Steam Games\steamapps\common\Kerbal Space Program\GameData\Shuttle Orbiter Construction Kit\PlumeParty\Version\PlumeParty.version I'm pretty sure you copied the Folder on Shuttle Orbiter Construction by accident. Delete it, it will no only fix your issue but probably prevent some others that TweakScale doesn't knows about! Cheers! "install safe!"
  12. I used to use KOS. KOS allows you to name the part (I think this can be done on recent KSP?). This makes things slightly less harsh. Once I find the craft and the part I want, I keep track of the indentation. "Professinal grade" Text Editors as Notepad++ allows you to open more than one window with the same file, so you can have multiple "visions" of the same file. This also helps a lot. It's not exactly hard - the problem is that is way to easy to make mistakes.
  13. Ugh…. I was in "Developer Mode". Finding the heaviest part on a craft is somewhat simple with the right tools (I just use Notepad++, seatch for all "mass = " and then pick the biggest number on the list). Sorry. I'm on Mac, so I will show you a TextWrangler screenshot - but other than the looks, Notepad++ works the same. Changing the autostrut is just editing that "autostrutMode" thingy. Problem: you make a mistake, a simple typo, and you screw up the savegame. Use SAVE if you are willing to try this such a stunt. Every time you dock and undock a craft, you change the root part of the thing. There can be only one (#highlanderFeelings). When you undock, the root of the undocking craft is recalculated/restored (never bothered to check…. something to be done). However, doing it manually is a pain in the SAS, no doubt. I only managed to do that on small crafts, and I made a lot of mistakes until making it right. I did the stunt just by the challenge, there're easier ways to accomplish that (see below). The few stations I made were not that big, and I didn't welded them, I used the big docking ports and then autostrut them to root - at least for my stations, autostruting the key docking ports to root did the trick. But I had choose the root do be equidistant of them... I think it's easier to spawn a new, fixed station in the place of the current one, and then edit the savefile to move the crew from the old to the new, and then just delete the old station from the savefile. This will mangle the saveMD5 on the loadmeta file, however - since I don't care too much for career, I just don't care about, but that saveMD5 is there for a reason (for trophies, perhaps?). Oh, yeah. Use SAVE.