Grimmas

You do not need any rebalance mods to play BDB with JNSQ - BDB parts are balanced like stock so they are perfect for JNSQ scale.

So, I looked at Mechjeb's porkchop thingy and I can now only assume that you were joking. Well, strictly speaking it may really be better than stock for some vague definition of "better" but ugh. Not a fan.

I've done the same Blueshift run to Nova Kirbani at high c and had no such issues (well, not quite true, but my issues were more like exploding when landing on planets around Nova Kirbani a). So YMMV. I have a high end PC though. Post your logs?

I may look at it this weekend but no promises. TBH I do not find much joy in balancing mods and I'm still far off from actually using Blueshift and SpaceDust in my career saves. You may be better off integrating or adapting Rakete's version if his numbers work for you.

I'm not the guy who made that, I just linked to it because it's brilliant. I'd be happy if I can come up with anything that's even remotely close

Good way to do that is to make a post on imgur.com and then linking the image in here.

Best Lunar Rover design this way. And scroll up from there a few posts for the pics of it.

Is it in career/science mode? Did you unlock alternative engines for it in the tech tree?

Album this way.

Here's a gallery for the remaining issues as promised. These are the issues I described a few posts back, more comments are in the image descriptions. Some issues are just minor visual glitches that probably won't even appear when installing EVE/Scatterer while others are in the realm of making it difficult (cubism) to impossible (exploding on ground contact) to play. The logs are here. Player log is here. This is clean install with the minimum number of mods (ie just Kopernicus, MFI, MM, and clean GU with only Alpha Centauri installed and enabled without Galaxy or HomeSwitch). I managed to land a few times but ultimately still exploded towards the end, although I did not manage to reproduce the two bugs I had yesterday where either the vessel exploded immediately upon landing or when switching from the tracking station.

Err, I thought it's supposed to have a bright blue spiral background like in your picture? It's not the case?

Deformation happens when Kerbin is still in the original location as well. It pretty much always happens when I switch to a flight scene that is far away then switch back to KSC scene. But the fact that you're aware of it means that this is fairly normal with KSP at interstellar distances isn't it? That's sad. I was hoping there maybe was some workaround. BTW you have a syntax error here: [WRN 16:49:06.778] unrecognized trailer: ',*' on: GU/Configs/GU_Patches/Rescale_Sigma/2.5x/@EVE_CLOUDS[*]:LAST[GU]:HAS[@GU_GENERAL_Settings:HAS[#Scale[2.5]]],* As for the Galaxy mode, here are some screenshots. I did restart KSP twice after enabling Galaxy mode. The only thing that really comes to mind is that the version of instantiator I used is fairly old, but it doesn't seem like there is a newer one. And here is the log. For the other issues, I'll post separately later as I need to capture some screenshots. Seeing as you are asking for "proof" I take it that those issues are not expected behavior so there is some hope for fixing them.

Yes, it's possible. You'll need to add the resource to a hopper as well, or you won't be able to get it out of WOLF.

You are more likely to have problems the farther back you go. It's not only RP-1, the express install pulls in a lot of RO dependencies and other mods as well, many of which have long since dropped support for anything lower than 1.8-1.10.

Some mod was likely providing that module when you created those crafts and now you do not have that mod installed anymore. It should be unrelated to BDB. A missing module is actually not a big deal, all you need to do is open the craft file and save it again and it should save it with the modules that are currently relevant for the parts present on the craft. It's only when actual parts themselves are missing that you really will have problems as most craft files with missing parts will refuse to load.

Given how scale worked in KSP, we can probably also expect scaled down galaxies... I expect the nearest star system would be less than a lightyear away. And since we can now burn during timewarp it won't take that long to get there. FTL will be left for the realm of modders.

Mine does not look like this either, when using Galaxy mode with the full install and Instantiator and Singularity. It just has the regular stock skybox instead. All I get from Galaxy mode is that the Picasso/Cubism KSC deformation and frustum error logspam happens immediately on game start instead of only after first loading a flight scene at a distant star. Do you have any insights into how to avoid that issue or the other issues I posted on the previous page? I'm happy to post additional info or screenshots/logs if it would help.

It's probably as simple as changing "Orange" to "Orange|White" I just don't have the time to fix it right now, maybe a bit later. EDIT: Fixed, PR on Github. This should be more future-proofed now.

Thanks for letting me know. I could reproduce it, so I'll look into fixing it (might take a few days as I'm busy with work during the week).

That part looks like it isn't finished. As for what it is intended to do in the future, your guess is as good as mine, but for now it is safe to ignore it. You shouldn't need it to use WOLF currently.

This is a syntax error and already fixed in Blueshift 1.7.8 If you do not use SpaceDust then it is safe to delete that patch though.

So, I've been trying to prepare myself (ie selecting a stable mod combo) for an interstellar GU campaign and I'm running into some fairly fundamental stumbling blocks. Before I start bombarding you with logs or what not, I just want to check if this is expected behavior, as I suspect that the main reason is basically that KSP is not set up for these sorts of interstellar distances. I was worrying about mod compatibility so I restarted with a clean install of just the basics (1.12.3 + latest Kopernicus + latest GU with only Alpha Centauri installed and enabled, no other mods at all except ModuleManager) but the issues are the same. Some are just annoying while others are game breaking as they would prevent any sort of colonization. Mainly: 1) Landing on an extrasolar planet has a good chance of causing the craft to explode. 2) If landed despite that, going EVA has a good chance of causing the Kerbal to explode when exiting the craft. 3) If Kerbal survived going EVA despite that, then if I switch to the tracking station and back to a craft or Kerbal on an extrasolar planet then either the Kerbal, the craft, or both will usually explode. 4) View frustum error logspam when switching back to KSC scene after flight scene on interstellar body, this also causes the KSC to glitch out - massive loss of precision leads to deformed buildings which are not clickable and keep changing shape in surreal ways (like something Picasso would paint). If quitting back to the main menu at this point, the menu buttons also become unclickable. 5) Patches of terrain randomly disappear when trying to land on planets, making the planet transparent for obvious reasons. This usually is followed by my craft exploding. 6) Stars shine through planets that should be obscuring them (this is fairly minor and I've only seen this happen when installing GU without any other visual mods). 7) Parts of the atmosphere are missing when close to the planet (ie the halo on the horizon is "incomplete", again this is also fairly minor and I've only seen this happen when installing GU without any other visual mods). @StarCrusher96 Please let me know if what I am seeing is expected behavior given GU's ambitious scope, or if I am suffering from some bugs and should post logs etc. If there are ways of coping with this then I'm interested in hearing people's experiences, as I was fairly excited about the prospect of building a USI colony on an extrasolar planet :-)

I don't think it's possible to not make beautiful crafts when using Nertea's stuff. Just install all his mods and have at it.

This is important so it bears repeating.

If you mean Transfer Window Planner, it's better in that it is actually useful unlike the new stock tool, but it is worse in that it has about a 1 in 20 chance or causing a CTD when I actually use it Are there better alternatives? (Apart from Astrogator which is sort of useful but too narrow in scope)