Brigadier

Use a cloud service, such as DropBox or Google Drive, and upload the file there. Then post the link in a forum post.

Feature suggestion: If the parts window is open and you deselect the subsystem button, the parts window should close. Unless there's a case for keeping the parts window open regardless.

From where do we get the textures? Are you going to farm them out or choose from all submissions? Whoa there. When I said "from scratch" I really meant it. I still want to learn and have started reading up on config files but if you have a link to a good planet cfg file resource to learn, I'd appreciate it. I've started with a Google search and will see what comes up. Don't you already have planet cfg files that we can insert data into? Do you have any particular guidance as to what you would like to see? Would you prefer us to follow KSP convention regarding biome names, i.e. highlands, lowlands, polar, grassland, etc. or will you simply take what you get and alter later. If the latter, then I don't have to wonder what I'm going to call them. Absolutely! Does every last pixel need a colour or is there a default for the biome map (i.e. if it has no colour in the map it must be biome x)?

That would be fantastic. I'm sure you would get quite a few people who would give it a try regardless of method (some of them would actually do a good job ). I speak for myself but I think we (the big 'we' not the Royal 'we') just want to help you deliver what appears to be an amazing addition to the KSP ecosystem (hey, there's a suggestion for your system name ). In any event, it potentially reduces your workload but you'd still have to review any submissions for correctness and completeness.

Third time's a charm. I, too, would love to learn but it would be from scratch. Education is probably not what you want to get into at this stage of development.

Is this more of a Texture Replacer or an Indicator LIghts issue?

Understood and thanks for the answer.

A picture that included your AGX windows would have been a nice addition since that's where your problem lies. I've never tried to put engines in an action group. Let me test on my install. I don't think this is the case, but if you assigned the action group in flight and then had to revert to a previous quicksave, the action groups are not persistent. True persistence occurs only if you create the action groups in the VAB/SPH. This has not been my experience (not to say your issue isn't legitimate) and don't know how best to advise you. What are your KSP and AGX versions? How did you install the mod? Have you tried removing and re-installing the mod? I'm assuming that you have solar panels that actually retract, right (it appears that you do but I'm just making sure)? I'm not an expert so the next time you post, if you haven't resolved the problem, post a link to your output_log file to help those wiser than I am. Make sure it's a brief game session that includes the suspect behaviour. There may be something in there.

Are you creating the action group in flight or in the VAB? It shouldn't make a difference since it's supposed to be persistent but it might be a clue. In the VAB, I open the AGX windows, and in the Selected Parts window, I select a key, enter a title for the action, then click on the part I want to affect. Finally, I select the desired action from the list of possible actions. In flight, I right-click the AGX button and go through the same steps. Can you describe the steps you take to create your action group if they're any different than these?

KSP 1.1.3 I installed this mod via CKAN and, at first, I didn't see any any indicator light part. I did see the status light on things such as batteries, command pods and the like. I started a new career save and, lo and behold, I see the part in the VAB. However, now in the output log, I get some errors: This probably results in the part in the VAB appearing as black dot, a behaviour which continues in flight. I can't get the light to do anything, but I figure it's all related. The entire output_log is here. Have I done something wrong? Is it a Texture Replacer (v2.4.13, manual install) issue?

Here's another question: Do these come from stock, SVE or Kopernicus? I realize these aren't errors but why might I be getting these warnings?

Thanks for your suggestions and I'll keep plugging away. Time to return our regularly schedule programming (i.e. we're way off topic).

KSP 1.1.3, latest Steam client, i7, 32GB RAM, GeForce 960 I get the following error sometimes when quitting KSP: It usually results in KSP hanging on exit and I'm concerned that it is somehow corrupting my saves. I cannot reproduce the fault and haven't found a pattern to the situations in which it occurs. It doesn't seem to matter if I start KSP from within Steam, from the KSP icon that Steam placed on the desktop, from CKAN or from my own shortcut. All of them have the same commandline switches, -single-instance -popupwindow Is there a solution workaround out there? I've searched the Steam and KSP forums and haven't found anything useful yet.

That's really good to know. However, I now never have anything else running in the foreground when starting KSP (I have 32GB of memory and still KSP and Firefox don't behave well together. I can get out of memory errors if they're both running). I do occasionally have open other things after so I'll have to stop this as well. I have two monitors, and I'm thinking that clicking on an open application on the other monitor is the same as Alt-Tab.

It certainly does and I already have it on the command line (along with -single-instance), regardless of the method I use to start the game (from Steam, from the desktop or from CKAN).

No big deal. I'm hoping that someone with more smarts than I have can help resolve this with me. <whine> I've never been able to play enough to get out of the Kerbal SOI because either the game gets a save-breaking update (some times) or my save gets corrupted (often). I see the occasional errors in the log file and have no idea if they're symptomatic of some bigger problem that I have. It's not my machine (i7, lots of memory, good gfx card with lots of memory) so it must be my installation. With 1.2 due soonTM it'll be another save-breaking update that will force me to restart a career. </whine> BTW, great work on your mods.

KSP 1.1.3, SVE 1.0.8 (manually installed), Win10, 32GB RAM I'm try to sort out yet another corrupt save. In the output_log I get the following errors (amongst others): I'm unsure if they're related and the devicelost lines repeat hundreds of times. Is this an SVE or Kopernicus issue? Or perhaps neither?

Oops, forgot to read the OP (again), sorry. Nope, still don't use it.

KSP 1.1.3, Exploration Pack 0.5.4, Win 10, 32GB RAM. I'm trying to track down why my save is corrupted and I note that I'm consistently getting the following error in the log: Full log here and the save is here. Is this a problem?

TBH, what is the Power Turn feature? And, no, I don't use it but it's because I don't know what it's supposed to do.

I see why you say that, but for some of us still trying to get out of Kerbin SOI in a meaningful way, I'd hate to delay the opportunity of fly by/to these wondrous celestial bodies for however many years of real time it would take me to conquer the stock system then move on to this one. It'll be what it will be, though, and maybe I'll just have to gaze enviously at this thread for a while. Marvelous job, @Galileo

It works in 1.1.3. At least it does for me.

Thanks for updating these useful utilities.

Thanks. Tutorials are always a good idea and will certainly help weekend flyers like me.

5 minutes