Aelfhe1m

Looks about right to me - at least for an October maximal sea ice extent. NASA diagram, video showing sea ice changes Mar - Sep 2014

There are two attachment nodes above the interstage fairing base. You want to attach the TOP node to the bottom of the engine (the upper node is the one that has the detachment point on it) then reduce the height setting to get the engine a suitable height above the base and increase the extra height until the fairing sides reach the bottom of the next stage. Judging by the numbers in the last image you attached the lower node to the engine. Edit: example image I did for a similar question on Reddit a while ago.

Typically I've not found this to be too much of a concern provided you get the initial plane close enough. Take for example a space station orbiting Earth at 400 km altitude (comparable to ISS) and a supply vessel launching to an initial chasing orbit of 200 km. The synodic period of the two orbits is approximately 1.4 days so even in the worst case scenario - where you launched into orbit just ahead of the station's position in its orbit - a rendezvous should need no more than 2 days life support (with a generous margin). Usually it's not too difficult to put the supply vessel within a quarter orbit behind the station which cuts down the time to rendezvous to less than 10 hours.

Kerbal Renamer can be configured with additional cultures. You need a suitably sized image in the GameData\KerbalRenamer\icons folder (some example flags here) and a module manager patch like:

Your manoeuvre is 4 days early which makes a huge difference for such a short transfer. TWP shows departure Y1 D44 while KAC shows current is Y1 D40. You need to warp ahead to closer to the departure time before setting up the node or use some tool like Precise Node or Precise Maneuver to move the node further ahead in time. (You could also use the + one orbit buttons on the stock manoeuvre edit tool to adjust forward)

Did you make the changes to Scatterer's planetconfig file and rename the Kerbin and Duna folders as per the RSS section on the Scatterer first post or use the Scatterer files included in the RVE download?

The space centre overview is often glitched like that. Have you checked whether it looks OK from the launch pad/runway in flight mode?

It affects the number of unlocked build queues in KCT. One queue per level.

I'm on Windows 10 running both KSP and KSPTOT on the same machine. Not sure what you mean by "hostname" in this context. The IPAddressWhitelist.txt file contains both 127.0.0.1 and 192.168.1.1 (current actual IP address on local network). Edit: just before submitting the above comment I decided to try creating the bodies file again (another failure). Then started looking around in KSPTOT to see if there were any settings or configs I'd missed (there weren't). Finally I tried using the "KSP Real Time System" menu to "Upload maneuver" (it worked). Then tried creating the bodies file one last time - lo and behold it worked this time! Don't know if any of that information will help you or others figure out why it didn't work initially since other than it not being the first thing I did after opening KSPTOT, I didn't do anything different that I can see. Well all's well that end well and all that. Thanks for trying to help with my problem. Now time to dig into the tutorials.

I'm having trouble with "Create new bodies file from KSP" (for RSS). I followed the instructions on the first post to install the MCR 2015b, download the latest KSPTOP zip and extract it, copied KSPTOT connect folder into GameData and then restarted my computer (just in case). Launched KSP and went to vessel in Earth orbit. Alt-Tab to desktop launched KSPTOT and tried to "Create new bodies from KSP". Got an error box - "There was an error pulling data from KSPTotConnect. Is KSP running in the flight scene with the KSPTotConnect plugin loaded?" Here's the relevant section of the KSP output log showing it's trying to send the data: I also tried using the Pre-release 9 exe linked further up the post but that made no difference.

Nothing wrong there. The progression in RP-0 is tiny sounding rockets (or planes) first then gradually bigger rockets. In your engines list you've got the aerobee rocket engine (first entry) for sounding rockets (with a small procedural fuel tank usually) and the Tiny Tim SRB (last entry) to give it a bit of an initial boost.

The RP-0 config ties the number of build queues to the upgrade level of the VAB/SPH. i.e. you start with one queue, upgrade your VAB building to level 2 you now have 2 VAB build queues.

I think it's an issue with Contract Configurator that @nightingale will need to look at. When RP-0 starts a new career it auto accepts the six initial milestone contracts. But CC now has a 6 contracts limit for 1 star contracts (at first Mission Control level) and there are no free slots left over to manually choose the first launch and Kármán line contacts - despite the heading showing 0 out of 6 contacts accepted.

An example of a mod that works with individual experiment results in a ScienceDataContainer would be Ship Manifest take a look at it on GitHub. To do what you're talking about I would suggest starting by writing a PartModule that inherits ScienceDataContainer and then overriding the CollectDataExternalEvent and StoreDataExternalEvent methods with whatever filtering code you need (or hide them and replace with other actions and events). Use a module manager patch to replace existing ScienceDataContainer modules with your custom module. The methods and fields are all public so it looks like it should be possible but I don't have any real experience with writing PartModules.

@ZobrAA have a look at Modular Fuel Tanks (or Real Fuels). Their tanks can be configured to hold multiple resources (including electric charge and life support) in a single part with the available volume divided up however you want. You could then have your resupply vehicle have a MFT for consumables and a KIS container for spare parts.

Starting date is 1951-01-01. RSS configures planets and moons for that initial epoch. The mod RSS Datetime Formatter will modify date displays in game to correct format.

I'm just gearing up to first manned Moon landing in my current RP-0 save but I took a peek inside the contracts folder to see what might be available later: There's also a pull request on RP-0 GitHub for additional Lunar base and station contracts so they may be added to a release in the near future. I like the idea on sample return missions. Could be either just return safely from X or maybe include requirement for bio sample or film return camera experiment results as well.

The current release was compiled against 1.1.2 although it is also compatible with 1.1.3. Download the zip from that link and copy the content of the GameData folder into your own KSP GameData folder. Documentation on using and configuring Historian is in the readme - several example layouts are included in the download. Happy to help if you have any specific questions. The new update I'm currently working on will be compiled against 1.1.3 however.

The stock bug fixes mod now includes a patch for the docking bug. Can't vouch for its effectiveness since I've had the good fortune to avoid this bug so far.

In the linked post scroll down to the section that says "1. The Logs" - the relevant file for Windows 64bit version is "<KSP>/KSP_x64_Data/output_log.txt"

Screenshots of your GameData folder don't really contain much debug information. Try posting your log file as described here.

I've encountered this problem in the R&D building as well. It can usually be fixed by clicking an already research node closer to the start of the tree (may take more than one attempt) and then back on the desired node again.

You also need Kopernicus, ModularFlightIntegrator and ModuleManager. Make sure you have the latest version of each mod for 1.1.3.

Had a look at the log. Most obvious thing was a very out of date ModuleManager (v.2.6.21) and the exception it was throwing during its Awake() method. There was also a Kopernicus related exception near the end that I've not seen before. I'd try replacing ModuleManager with the latest version first.