allista

It was modified based on dynamic pressure down to about 5 deg in lower atmo, but then the limit was 10. Though the actual AoA was rarely larger 5. UPD I can upload the video of the whole thing. Hm... need to think about it. The whole framework of TCA configuration is based on the idea that it's part of the ship. To the extent, that docking/undocking preserves configuration and grouping of TCA instances. So it is possible to, say, attach a new core with newer TCA configuration to a station and get all the benefits.

Ok, so with the help of @JonnyOThan I've managed to do at least this: don't look at the Max. Angle of Attack -- it was 10 deg all the way, but I changed it afterward by accident But for higher orbits in this case conventional autopilot's logic is still faulty and needs improvement...

It should "happen" if you have enough resources and EC. It's "progress" should be displayed in KSC in main GC window (select the planet, then find the workshop in the list). It actually only happens when you switch back to the workshop, since there's no background processing of this level of detail in KSP, only the catch-up. This looks like an exception that happens during ship loading. Please, share the Player.log file (via a link to gdrive/Dropbox/etc) obtained after this happens.

@Daveroski ok... After some trial and error I've managed to achieve a 306km LKO with 166m/s of dV remaining. But the target ApA was 71km Well, TCA managed, not me per se. The reason is, obviously, the acceleration that had to be continued far past initial ApA. I'll try to figure out how to do it without moving ApA past the target value...

Ok, so the Luciole craft is not a problem; limiting AoA depending on dynamic pressure brings it safe and sound to orbit. But the Little Squawk gives me nightmares! Even on the steepest trajectory with thrust at 10 degrees to the prograde almost all the time it only manages to achieve 71km ApA ~40s ahead, then falls back, because the last stage has no thrust to circularize in the 80s span. Adding relative ISP to equation doesn't help that, even though it saves some more fuel. So I'm asking to make a video of your manually controlled ascent to learn from. I heard of incompatibility with 1.10.1 of some mods (mine including) to the extent that the game crashes on load screen. But I unfortunately haven't had much time to spent on KSP past few weeks due to the workload and family stuff, so I haven't even install 1.10.1 yet

Use the latest version compiled for 1.9.1 from SpaceDock https://spacedock.info/mod/198/Throttle Controlled Avionics/download/3.7.0

Err... what?

Correct, but this is more relevant for VTOL crafts than for spaceships, since in space the ship would turn using RCS or reaction wheels with engines off most of the time. So in general a conventional 1-engine+RW design works well. Nope. Visit the SpaceDock, ChangeLog section, to see all the versions and their compatibility info.

Not yet, but I'm planning to make one. Yes, TCA works with MJ alright.

It does if they have engineers and are set to work on the same kit.

1. You don't have to carry the resources: the stock drills can mine Ore, the stock ISRUs with GC patches can convert Ore to required resources, albeit not quickly. 2. Yes. And their level (starts) matters as well. 0-lvl engineer has 0.5 efficiency, 1-lvl => 1, 2-lvl => 2 and so on. A crew of 5 0-lvl is half as efficient as a single 5-lvl. 3. More like a single use launchpad. Container is fixed to the ground, ship is assembled inside, then the container is destroyed and the ship stays on the ground (don't forget launch clamps!). But no size/mass limits.

Looked at Tantares+LV. I'll do the patches and include them in the next release.

That is correct. There were some attempts to do so (you may look for patches in this thread), but there are two difficulties: First, there's no trivial way to patch "any part with arbitrary set of resources", because you need to figure it's equivalent volume in m3 using conversion rates as defined in TankTypes: https://github.com/allista/AT_Utils/blob/master/GameData/000_AT_Utils/TankTypes.cfg I myself do it by means of a somewhat lengthy python script based an a config file parsing library; that is I parse part and tank configs perform some calculations and compile a patch: https://github.com/allista/ConfigurableContainers/blob/master/PatchContainers.py I don't know if this could be done by some MM kung-fu. Maybe. But in principle this may be done directly in KSP by moving these calculations into part modules and mass-patching parts that have resources. Actually, I'll consider this. But second, there's the issue of compatibility with the other resource switching mods. By manually curating patches I can avoid many game-breaking conflicts, where two parts are patched by two mods at once. I'll check what Tantares uses. Parts with plain resources could be easily converted. But I suspect they used B9PS as everyone else. In that case the patches would have to be written by hand, and by someone on their team, so as not to upset the TWR balance they maintain.

The link is broken by double-pasting.

Thanks a lot! Got them too.

You work as QA specialist is impressive Can you spare the save to reproduce this?

Thanks! Got them!

It was merged 3 releases ago, at 2.5.0 for KSP-1.9.1 Why do you need it now? I'm any case, CKAN is just on of the ways to install things. If for some reason it isn't working for you at the moment, you can always install from Spacedock.

Also, I'd love to have a craft with these parts too; since what you describe -- the problem with shearing -- sounds different than what is happening with this Little Squawk.

Ah, I can't download it -- the links point me to my own dropbox account.

Because there's no more CORE -- it is merged into AT_Utils.

There's a master-switch for deployment hints in main GC UI window that is accessible in all scenes except VAB/SPH. Its value is saved with the save.

@linuxgurugamer it may be more convenient to move to discord.

Basically you just patch an existing tanks type, or create a new one wherever you want. Here's the current configuration with all tank types and their patches: https://github.com/allista/AT_Utils/blob/master/GameData/000_AT_Utils/TankTypes.cfg But you can add new types and patches in any .cfg file in GameData. Or you can PR your changes to this file

Thanks a lot! But wait, how would it help? Doesn't CKAN use .version file from distribution archive rather than from the repo itself?