allista

Thanks for the report! This is definitely a bug. I'll investigate and fix this ASAP. Sorry for the mess. Thanks, I'll check the config. Maybe something was changed in 1.2.2 with this regard.

Alas, I still don't know what happens there. The only errors there are from some part trying to activate autostruts on themselves, but which one, and whether it is connected to the bug -- remains a question. Have you tried to switch between vessels (between the Miner and the Kit) before going into the warp? Or before deployment? I will try to recreate it and report back...

Great, thanks! And I'm sorry I was not specific enough: I meant the KSP_Data/output_log.txt, which contains unfiltered information from Unity. Anyways, this KSP.log contains two things indicative of installation errors: AT_Utils somehow miss the 002_MultiAnimators.dll that the Hangar requires. The installed version of InfernalRobotics is not fully compatible with KSP-1.2.2, because its IRSurfaceSampler.dll still references KSPUtils.dll which is no longer exists, so ModuleIRSurfaceSampler should not work. Neither is linked to GC, but you should still pay attention to them. As for the the bug in question, there are some errors involving PartJoints appearing right after you have switched to the ship and before you have deployed the Kit. But without output_log.txt (and maybe even with it) I can't see where they come from. So I ask you to post this file as well.

Wow! Thanks for the report. May I see the logs? As you may notice in the introduction video, I hadn't have such a problem. So I'll first need to find a way to reproduce it... And Happy NY, by the way

Well, first, I wouldn't be so sure about the "old/new" thing. Mechanical properties of the printed and forged->carved parts should differ considerably. Not everything could be printed and be functional. Second, the mass of such a printer and its energy requirements are no less forbidding for in-space use than that of an industrial lathe machine. Third, even if you have adequate propulsion+energy generation, you will face the overheating problem. No air around -- no fast cooling. Air around, and you need ventilation, heatpipes, tons of radiators to cool the air. There are, at least on paper, much more space-friendly solutions for producing structural components such as lattice girder.

No, TCA is added to absolutely every part that has ModuleCommand. And it doesn't seem the install is messed up, as it usually leads to simple absence of TCA in flight, which is not the case here. And I'm sorry for misinformation, but I have outsmarted myself here and forgot about it. I'm looking at the code now and see, the action is active in editor only for the part where TCA is enabled. This part indicates so on the context menu. But the action group you assign to it is saved in the vessel-wide configuration, and when something causes the switch off the active TCA instance, the action group is restored from it. So, how it should work: in editor you find the part that says "TCA Active: true" in its context menu. You use it to assign the action group. The multi-part situation TCA handles by itself. It's a shame to forget such things. But I hadn't have the time to play KSP for over a year, launching the game only to test things I know. In editor I'll add highlighting for the part with active TCA, so one won't have to click through parts to find it.

Non-movable manual limiter means there's an autopilot engaged. Probably the Stop program which was automatically engaged after you took off to steady the ship. The TCA is installed into every control part (cockpit, probe core, etc.), so each one will have the "Toggle TCA" action which you can assign to one of the action groups. The caveat is: if you have more than one control part you will want to add this action from each of these parts to the selected action group to ensure consistent behaviour. Because in flight there's no guarantee that there will be no switching between TCA instances if, for example, you somehow damage the ship and some parts will be destroyed. I'm probably becoming too technical here...

There are two options. Both require the aft engine to be set to Manual Thrust mode: 1. With this setup you can use Path navigation or Cruise Control, or Go To program. The autopilot will automatically use "manual" engines to control horizontal speed instead of pitching. Or you could just use them yourself: push "Show manual engines" and use the appropriate throttle slider. 2. You can use one action group to manually enable the aft engine to accelerate and gain enough horizontal velocity; then use another to disable VTOL engines and TCA itself. Thus you can switch to conventional airplane mode. Edit: ah, and you can automate the latter using a simple macro.

Can't help but share this About producing "simple" mechanical parts. On the planet...

I encountered this as well, but so far have failed to find a fix. It's somehow connected to colliders and CollisionEnhancer framework inside KSP. What I notice is that if you have a kerbal inside the rover (like Canyon Crawler) and you go EVA, the problem is also fixed (at least as soon as you board back). So, I'm working on it. And, hopefully, will come up with something. Ironically, in KSP-0.90 and earlier there was another problem -- the ground hangars somehow didn't have any friction with the wheels -- which was fixed in 1.0 and I've hoped that was the end of it. But, as you can see...

Yep, thanks! I forgot to mention it here Configurable Containers v2.4.0.1 for KSP 1.2.2 (2016.12.29) ChangeLog:

I doubt it. The mechanics of the spawning exactly repeats the stock spawning at KSC. So anything that spawns at KSC as you expect will behave the same when you launch it from the Kit.

Hangar v3.2.1 for KSP 1.2.2 (2016.12.29) ChangeLog: And also @smunisto, you may be interested in my new mod here:

TCA v3.3.2 for KSP 1.2.2 (2016.12.29) ChangeLog:

Sorry, but the whole point of GC is to be grounded. As I said, I consider in-orbit construction of parts as being out of the question on the current level of Kerbin technology. All the other limitations are also deliberate and made to add something to the gameplay, not just to ease its walkthrough. To be completely honest, I'm planning to add something of a compromise for in-orbit construction, but not to this mod. Rather, some of the hangars from the Hangar mod will receive the ability to keep a KIS inventory of parts and dis/reassemble ships inside them quicker than you would do manually just using KIS. But that's still a long way to go... Bingo!

No-no-no, not right! Any stock part, non-stock part, any part that have space for a crew already have the GroundWorkshop module. By default. But some of these parts are simply too small to be effective, so the module switches itself off. Look at the part's tooltip in Editor before considering using it as a workshop.

Almost. There are three differences: First, it don't just "pack" a ship. It "packs" only essential parts, materials, tools, etc. This decreases the mass considerably compared to the sum of parts. But it also balances the gameplay: you can't expect 3 kerbals in a small workshop to produce all the high-tech equipment that is needed to assemble a rocket engine, even if you have enough still. The engine is a precise mechanism which simply cannot be build "out of Ore" using a smelter. And by what magic ELP manages to produce, say, enough radioactive element to fuel a nuclear reactor (or a simple RTG, for that matter), I have no idea. Second, in contrast to ELP, Ground Construction allows arbitrary placement of the built vessel. No need for a "launchpad", the launched vessel is not coupled to anything, it just stands on the ground wherever you placed the Kit. Third, no in-orbit construction. For this you have KIS which accurately "emulates" all the complexity of building something in space. Even when you have all the parts built for you on the surface.

It adds 3 parts: the DIY Kit Container (which is essential), the Mobile Workshop and the Space Crane (both are not essential). All crewable parts (stock or not) are considered to be workshops, but their real efficiency is calculated dynamically and only qualified parts are left with the working workshop functionality. This (as described in the OP) could be seen in the part's extended tooltip in Editor: a workshop part should have Ground Workshop module with the efficiency indicated below. GC does not add any new resources; it uses stock Ore and a single resource from the Community Resource Pack -- Metals. Internally it is called StructuralResource and it could be changed via configuration (if actually want to do it, I'll explain in detail later). If you have a part that attaches itself to the ground (like Launch Clamps do) then yes. Otherwise, GC produces the exact same vessels that VAB or SPH would produce on the Launchpad or the Runaway.

Introduction This mod allows you to build any vessel directly in orbit or on a surface of any planet from a DIY (Do It Yourself) Kit that contains all the high-tech components, needed equipment and blueprints, using only raw materials produced on-site, energy and kerbal workforce. The major benefit of the Ground Construction is that it allows you to build big, heavy, asymmetrical contraptions that aren’t meant to fly at all. Buildings, or even blocks of buildings; heavy rovers; huge rockets held by launch clamps — all this could be built with Ground Construction anywhere on any planet. In addition to construction from DIY Kits you can construct the kits themselves, allowing you to build a fully independent colony or space base. Also, if you're building a space station, you can build new segments docked to the station directly, without docking ports. Features Build anything: any ship, spaceplane, or really any construction you come up with in Editor. Even with launch clamps! Build anywhere, on the surface or in orbit: the assembled ship will appear right where you've placed/docked the Kit. Expand your space stations by building new segments docked directly to it. No docking ports required. Build DIY Kits themselves: make you colony independent, produce your own kits from scratch using blueprints and raw materials. Background operation: fly other missions while construction takes place on a far-away planet. Days, even weeks may be required to build something complex, but you don’t have to babysit your workers. Wireless transfers: fill the assembled ship with resources and crew before you launch it using dedicated UI. Centralized UI for progress tracking and fast switching to construction sites. See for yourself Magnetic Forklift Incremental Station Construction with GC Global Construction Ground Construction 2 - Independence Day! Introduction to Ground Construction v1 (legacy) Requirements ModuleManager CommunityResourcePack AT_Utils (already included) This includes the core components of ConfigurableContainers And its game content, located in GameData/ConfigurableContainers/Parts subfolder. Note, that it can be safely removed. Downloads Spacedock is the main download site for releases GitHub have sources (MIT), assets (CCBY-4.0) and also releases CKAN is supported How it works First, you need a simple mining operation already running near the spot where you want to build something. So you need: a Drill, an ISRU, some storage tanks for Ore, Material Kits and any other stuff that you want/need to supply the newly built ship with; a Workshop and, last but not least, kerbal engineers that will build things. Second, you need to assemble the DIY Kit with required materials (good luck with finding enough Blutonium for RTG on Minmus), tools and components. This is, fortunately, the simplest thing: in Editor you have a special part, namely the DIY Kit Container, which allows you to “load” any previously created and saved ship inside of it. The container is automatically resized to fit its contents, which are much more compact and weight much less than the original ship. Third, you need to attach this container to a carrier or store it in a hold of a cargo ship and fly it across the Void to the construction site. Then, all that’s left is to summon the control UI of the Workshop, deploy the DIY Kit, add it to the construction queue and order the kerbals to work (day and night, no holidays, no weekends!). Forth, when your base is mature enough, you can start your own Kit production. Getting technical How a ship is converted into a DIY Kit In Editor, you add the DIY Kit Container part to the carrier you’re building. In its part menu select “Select Vessel” to open the standard vessel selection dialog. Once selected, the ship is loaded into the Kit as follows: For each part of a ship, its complexity is calculated as a function of dry mass, cost and number of modules the part carries. The complexity determines the fraction of part’s dry mass that could be manufactured from Metals. Most resources are stripped away. The exceptions are: Solid Fuel, Ablator, all non-tweakable resources (cannot be transferred) and resources with zero density (EC, for one). Everything that’s left is packed into the Kit. Thus, a set of Part Kits is produced, which (along with the blueprint of the ship) constitutes the contents of a DIY Kit. A DIY Kit usually weights much less than a ship that is constructed from it, but, except for the resources, costs almost the same. How a DIY Kit is converted back into the (new) ship First of all, you need to land the kit somewhere on a flat surface, and, preferably, detach it from the carrier. For that DIY Kit Containers are equipped with their own simple decoupling mechanism, which is located on the top side, marked with yellow arrows. Then you need to Deploy the Kit. This could be done by a kerbal in an EVA suit or remotely from a nearby Workshop. A deploying kit detaches any part that is still attached to it, then gradually “grows” (imagine that kerbals assemble working scaffolds inside the box) until it have the size of the ship that will be constructed; then it is attached to the surface, so it cannot be moved any more. It doesn’t matter how the Kit was oriented. As far as it lies on one of its sides, the deployment dimensions and the orientation of the launched vessel will be automatically chosen to correspond to the surface. A deployed Kit can be processed by a nearby workshop with kerbals, but there are some limitations: The workshop should be at most 300m away. The kerbals that will be working on the Kit should be inside the Workshop, not in other parts of the same vessel. These kerbals should be engineers. Scientists or pilots don’t count. The skill level and number of workers do count: a 5-star engineer works literally as much as five 1-star ones. And five 5-star engineers perform spontaneous miracles. The distance from the Workshop to the Kit affects construction efficiency and, consequently, the time needed. So it’s best to make Workshops mobile and get as close to the Kit as possible. The amount of free space per kerbal inside the Workshop also affects efficiency: a small compartment with a place for a single kerbal may be more efficient than a big one packed with two dozen passenger chairs. Note 1: the crewable parts that have Workshop capability have the “Ground Workshop” module (could be seen in part’s extended tooltip in Editor), which shows the efficiency of that part. Note 2: the efficiency of any generic habitat is capped at 50%. To be more efficient you need to use the provided Mobile Workshop part and build a rover with it. If you want to benefit from background construction, you need to make sure you have enough power and Metals to work with, as resources are not generated in the background. When the Kit is complete, you can “wirelessly” transfer resources and crew to it from the Workshop using dedicated UI. Then you can Launch the assembled ship, which will appear at the exact place where the Kit was. Acknowledgments My patrons on Patreon. Thank you for your support! Kevin Casey Bob Palmer Ryan Rasmussen Matthew Zaleski Bart Blommaerts eL.Dude Layne Benofsky Igor Zavoychinskiy Issarlk Meiyo BP Jenna Mitchell Squiddy Ted Achenbach SCESW Patrice Hédé Steve Victory

Through ScanSat: can it add stock waypoints (like contacts, or waypoint manager)? If so, you can do that, and then add this waypoint to TCA through "Add from contacts" button. For direct interaction between ScanSat and TCA both mods should be aware of each other's API. Numeric editing of waypoints in TCA is already available (since two versions ago) via waypoint list or by right-clicking on a waypoint itself.

Nothing is wrong. But TCA has builtin Collision Prevention System (CPS) which does exactly this: avoid collisions with other vessels. To toggle it, go to "advanced" and use the "CPS" switch there (green -- enabled, yellow -- disabled). *and there's no team. Just me and my beloved wife as a moral support

Sorry for the delay. TCA has two Land functions, one for landing from orbit and the other, for landing VTOLs after performing a search for flat-enough surface. Landing a plane on a runaway is just not something TCA can do. For that you need specialized for-plane autopilots. Few pages ago there was a discussion of such autopilots with some links.

Configurable Containers v2.4.0 for KSP 1.2.2 (2016.12.20) ChangeLog:

Hangar v3.2.0 for KSP 1.2.2 (2016.12.20) ChangeLog:

TCA v3.3.1 for KSP 1.2.2 (2016.12.20) ChangeLog: