VoidSquid

That is using CKAN, see here For many, if not most players, we're using CKAN for managing our KSP mods. I'd think (please correct me, if I'm wrong here), @Fierce Wolf assumed that you're already using CKAN.

I'd copy the whole KSP folder, rather than moving it, as Steam "thinks" it as has a KSP installation. And if a new patch is released, I copy my actual game folder back to C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program, run the update via Steam, and copy it back to my actual game folder, e.g. C:\KSP. These copy operations are best done using robocopy, if you're not afraid of the command line window (Windows key+R, cmd), but you can do that via the GUI as well. Oh, and making regular backups, better safe than sorry

Thankfully KSP is one of the few games that doesn't require Steam running in the background, even more, it doesn't matter where the actual game folder is located.

I strongly recommend you copy your KSP to another location outside Program Files (x86) for a couple of reasons, namely UAC and to avoid auto updates.

...which is still alive thanks to - guess who - @linuxgurugamer

Not a KSP but a Windows issue. Shameless self quote: "outside of program files and program files (x86)" That's M$'s nonsense UAC. "Protected" storage locations. To be expected. Very helpful for both, end users (who don't care or bother), and administrators (who are just annoyed). Find any sarcasm? Be my guest. Follow my guide, and you're good.

Signed!

You might also want to check out this video, @Neil Kermstrong :

This mod can calculate the times for you:

Understood, then I'll stay with the current CC version, not worth taking the risk for this little annoyance. Hopefully @DMagic will soon find some time looking into this issue. EDIT: Just opened an issue at Github https://github.com/S-C-A-N/SCANsat/issues/391 , I hope I put in the right words.

I remember watching a guy on Twitch playing KSP who had the same issue (fresh KSP install, SAS not working at all). Verifying the files via the respective Steam feature did resolve the issue. Might be worth a try, I think.

So it's not just my imagination or my specific mod setup, glad to hear Will do, thank you again for your time analyzing this odd bug so far. Well, I'm playing the English version of KSP, no need for any localization for me. 1.29. is safe then, what do you think?

Hey @nightingale, I found some more time for testing, interesting result: when I replace CC with the older 1.29.0 version, the bug is gone! As soon as I use any 1.30.x version, the bug appears. Hope this helps to narrow down finding what's going on here. Question: will it be save to continue using 1.29.0 for the time being, or will it ruin my career save game due to incompatibilities?

IIrc, you'd have to change the string for both, the save game folder, and in the respective .sfs file.

Hey @EchoLima, the only thing coming to my minsd, and it's a pure guess, your save game folder is named "Eli's Space Program 2"? Might be the apostrophe in the name causing the issue.

And here I thought my answer was clear and obvious enough, seems it wasn't.

Recording and contract: https://easyupload.io/m/3899om Btw, the time displayed during the flickering is the remaining time for the contract, not the total required time. I admit, it seems to be a very odd issue - you're sure you want to invest your time here, @nightingale ? Already feel a bit silly bothering you with this, let me know, please

Have you tried nuclear engines? Very fuel efficient, ISP 800m/s, in contrast to LfOx which go to max 340 m/s. Another option would be to build a rocket with an integrated ISRU unit: you could harvest and process ore into fuel, this way you need only enough fuel for the flight to Duna, refill there, return to Kerbin.

I might be too dense here, but I have almost all of my mods via CKAN, including several mods that are official for lower KSP version but nevertheless work fine with 1.10.1. What is the problem installing JC via CKAN for KSP 1.10.1?

Will do when I'm back at home. What is so totally weird about this: when I remove CC and the contract point and load the save game again, the issue is totally gone, including the flickering of all orbit lines for about 10s when switching to map view. Ofc, this kills the persistent.sfs, when reenabling CC plus packs, all progress ever is gone. Funny fact: it doesn't matter if switch to another craft (and another CB) but the one from the contract, same result. I went back 2 or 3 CC versions, one ScanSat version, no difference. And as per my superficial view across, nothing useful in the logs too.

Hey @nightingale, Since a couple of days I have an quite interesting issue between CC and the new ScanSat (20.4 atm), though this also happened with the two or three previous CC versions. What happens is, when I accept a new contract (seems independent of the contract pack), fly the rocket, switch to map view, and active a ScanSat overlay (terrain, or biome, makes no difference), the terrain info under the mouse pointer flickers alternating with the initial contract duration time (e.g. recover a satellite after 60 days, the ScanSat terrain info alternates with a small box displaying "60 days") several times a second. Finishing the contract, all all is back to normal. Console doesn't give any output about this, and before I bother you with any logs: any at least faint idea what's going, or have you heard / seen this ever before?

Well, have a good time then @darkplasmaray, I'm out of my wits here, bye.

"Click Through Blocker" is a requirement for several mods, incl. Toolbar and Toolbar Controller. I highly recommend you install it.

Oh... well then, no offence, but that absolutely doesn't look the way it should. Or, in other words, Trajectories might be the smallest issue here.... I suggest you get yourself CKAN and manage mods with that.

Trajectories can display its respective button either on Blizzy's Toolbar or in the stock menu, and default was (or is, IIrc) Blizzy's Toolbar. Tough I'd think, it defaults to the stock toolbar if Blizzy's isn't present. You can get Blizzy's Toolbar directly from the respective link (see the mod thread), or (much better) via CKAN.