SilverFox1701

I never tried to make a "workaround of the spirit of the historical progression". If that's what it sounded like, I'm sorry. When I first started doing the contracts, I took the starters of the US, the Soviets, and Germany at the same time, as I try to take as many missions as I can as a general rule just from an efficiency standpoint. When I found one launch completed multiple contracts, I just went with it. Also, if this is a consequence of me doing a "workaround", then why has it never happened to me before? I've completed about half the American line at this point, as well as all of the German, French, Canadian, and British trees and have never experienced an issue like this in doing it.

Log's not gonna do you much good, then. I played a little yesterday, so it's yesterday's log and not Friday's. In regards to what I did, I made three launches. The first was standard operating procedure; I tend to accept and run these contracts in batches. Not exactly historically correct, but easiest for me. Right now, my habit is to pick up six or seven contracts and run them at the same time, complete as many as I can at once in a launch. I launched under the auspices of an Explorer contract - I believe it was Explorer 30 - and completed four other contracts at the same time. I then went suborbital with the probe and crashed it into the ocean. I remember I crashed it into the ocean because the solar panels survived re-entry down to about 1 km above the surface before they ripped off. When the contract didn't finish, I launched a small Flea-SRB powered probe with the intention of crashing it into the surface sub-2km away from the launchpad; this usually completes missions that want to derp for me, whether it's a crash mission or a recovery, but it didn't work this time. Skipped over to a SCANsat mission I was running for a bit, as I needed to do something different for a bit - had been working on HoS missions all day and needed a brief break - before coming back and launching the rocket I was using specifically for ballistic missions. Those are always suborbital from launch. Flight went like clockwork, mission still refused to complete.

I'm currently running KSP version 1.9.1 with the most up-to-date version of CC - or at least, what CKAN says is the most up-to-date, 1.30.5. That being said, because I'm crap - or because I've only been playing for a couple months and have never had an issue like this, take your pick - I don't actually know a) what kind of log I'm looking for and b) how to submit it. I know that's probably not what anyone wants to hear, but I haven't had to work with the technical side of the game before...:(

Right. Now I actually DO have an issue, and I don't think it's because I'm being an idiot this time. Have made four attempts to finish the Corona 22/Discoverer 22 mission. Checks all the boxes, still refuses to complete.

Disregard; I'm just apparently not very smart. I didn't hit me until after I posted this and was working on a different mission that I realized, "Hey, smart one. There's a difference between suborbital and escape. Maybe try getting a suborbital around the Mun instead of just carrying through on an escape." Finished the mission after that.

So I've been working my way through the US tree in the standard pack - I figured there was so much in it between the US and USSR it was better to focus on one line instead of split my focus between all of them - and have reached a bit of a confuzzlement. Pioneer P-30. Mission requirement says I need a Vessel State with a destination of the Mun with a suborbital trajectory. I've made three attempts so far to get this mission to complete, but it refuses to give me both requirements. I get Destination: Mun once I'm in the Mun's sphere of influence, but even with a free return trajectory giving me a periapsis only 20km above Kerbin's surface, it won't give me the suborbital trajectory requirement until I leave the Mun's SoI, which wipes the Destination: Mun. I'm a little stumped here, and am not sure if I'm missing something or if something's wonky.