Morphisor

I am excited to see the creative possibilities everyone is going to come up with in the new game!

I like the concept! I'd suggest to be careful with how many nodes you might end up with, considering how many mods are out there. It might be an idea to group certain modsets together in some nodes, as long as they serve a similar purpose. Leave it up to the user how crowded they want their game to be... As for BDB, best I can come up with for integration is to have its progress oriented by the historical (alternate where applicable) timeline: it already comes with a natural progression in its parts in terms of science and power available. If you then split the spacecraft parts up into small sats / probes / crewed / station parts, you should get a pretty good progression out of it.

Any idea what would be causing this logspam? It's continuous during flight, I tried with versions 4.0.0.8 and 4.0.0.7, both were the same. KSP 1.12.3, JNSQ.

The Apollo XII contract needs an active craft identified as Surveyor-3 on the moon to locate the objective waypoint. So a random craft won't do. That's unfortunate. I can only suggest to try with older version of CC: I suggest 1.30.5 to be sure none of the recent changes are involved.

I have changed the prestige ratings for the Soviet early missions, this should fix the issue. Available on the Github master branch. The problem seems to be that CC is not recognizing the Surveyor 3 craft being in position and as a viable target. Interestingly, an almost identical problem was reported in the BDB contracts, but with Gemini not finding the Agena craft in orbit. That was reported quite recently as well - whereas these contracts have been out for 2 years without anyone reporting such issues before. I cannot help but wonder if the latest changes to Contract Configurator are involved here. So anyway, I've tried to apply the same fix here (Available on the Github master branch): adding an extra line to Surveyor 3 to hopefully let it be targeted again. Players will have to fly Surveyor 3 again to see if this works though. I'd love to hear if this solves it or not. Otherwise I'd recommend manually changing the waypoint generator, copying over your working example, to at least be able to progress their careers with Apollo XII. See above. Every time a science experiment is requested, it is because there are parts available that represent the craft referred to in the mission. The Explorer 1 probe core from BDB has the geiger counter you needed. FASA is an old relic and in no way recommended.

Hold on, this has not gotten the attention it deserves. I saw this was included in the latest update. How does this affect for example Beyond Home? Are all the 2.0 features now applied there as well or would an older planet pack still need to do updates on its own end? Either way it's huge.

That's odd and unfortunate behaviour. I have only one hunch towards a possible cause and hopefully solution: the ATV vessel stays associated with the completed contract and thereby not targetable by a new contract. Not sure why this didn't come out of testing before, but CC can be a little fickle. So I'll add an extra line to the ATV contract that would fix this if it is indeed the cause - but otherwise won't change anything. No guarantees here, if this isn't it, I don't know where to look for a fix.

Yeah that's pretty much expected behaviour. I don't play with Kerbalism so I wouldn't know where to start making it compatible. I'd happily accept a PR for a compatibility patch of course.

They're entirely optional, everything will work without them. There will be a few less things to do is all. Of course, replaying history is not nearly the same without those mods so I'd still recommend them if at all possible. But then, 8GB RAM is really insufficient for a modded install in general, good luck trying to stay off the good stuff.

No it's perfectly safe to do, the mission structure remains the same and your savefile stores the things you've already done.

I strongly recommend to fully remove the mod's folders before doing a reinstall of the latest version. Something has gone wrong with it given the behaviour you're seeing.

The experiments you show requested are not part of the current version of Gemini IV mission. If they are there for you, your install is incorrect.

You're using an older version. The latest version simplified the objectives to only include experiments from the vessel parts associated with the mission, at least insofar as they were made in BDB/Tantares at time of release. If you still wish to continue, try looking up the experiment name in the part search bar inside the VAB.

Elektron 3-4 is exactly identical to elektron 1-2, except for the orbit that needs to be achieved. If that works, the other should, too. Something else is breaking things in your game I'm afraid.

There's likely some kind of bad interaction going on, the mission parameters themselves are pretty standard. The mission calls for 2 craft, in what order are you setting their orbits? You could try disabling the duration sub-parameter and see if it works for you then.