Caviar

Hey all. Great work everyone !! I have been getting a strange bug where the crew roster has all the tourists (due to an accepted contract) but does not show up on the Crew Assignment section of VAB. The only thing left to do is to edit the persistent save file after the ship has been launched. I am not able to remember from when this has started, because most of my missions were unmanned. Also, my KSP is very heavily modded. I'm attaching a .ckan file here to give you the list, and yes I know many of them are rendered incompatible due to KSP updates. The save file and the .ckan modlist file: https://drive.google.com/file/d/1hVSyAcJfuXAEdSRINxcDZc2bGzH8VeSE/view?usp=sharing https://drive.google.com/file/d/118YTf_64kGmJfu26lYEDU0c0M5vH9a4j/view?usp=sharing The VAB crew editor pic: https://drive.google.com/open?id=10jAlHIiVOYxe2kstqaHRPFfjmR2AApqM But before that, this problem is not limited to tourists. The whole of crew assignment section itself is quite buggy. I'm not able to select the crew I would like to send on a particular mission. I thought it'd solve if I use BetterCrewAssignment mod, but to no avail. After a while, I find out that none of the crews can be assigned to any ship !!! What's happening here?

@Snark Thank You for the quick reply. I sure would have done the above suggested steps if it the same set of ships have never docked with each other, EVER. But prior to this, it had docked perfectly, and then due to a stupid mistake of mine that's totally unrelated to docking (wrong cargo bay size, mission to capture a rogue floating part in career mode), the ship was severely damaged. So now I reloaded to the prior launch stage, put in the correct size and relaunched it again. But only now it doesn't dock. Plus the port is opposite to the corrected part, so no dependency of the port on the new part. I would do the bug hunting method you suggested, but lack of free time and the reason stated above are preventing me from doing this. As for the exact problem, This sums it up perfectly. Only "state=PreAttached or state=Ready" doesn't work because its already in Ready position. Plus I'm trying to connect Clamp-O-Tron and CDP Shielded port, which has the same size and shouldn't bother me much. @KroShan Thanks for the suggest. I've around 30 dockings under my belt. Would it qualify me as an expert docker enough, master ?? Anyway, yes I have played the tutorial many many times. I'm very comfortable with docking, the process itself is not the problem. It might be the idiotic port acting up. I limit my speed to 0.08-0.1 m/s, and that too is no problem. But whats this angle alignment you are talking about?

What I came to observe is that the Docking Ports (Any size, any make) never behave consistently. Docks sometimes, sometimes doesn't. I have also ensured that the parts have the correct orientation, is controlled from the port, the destination port is targeted and everything else (disabling RCS and SAS just before docking). Didn't work out. I then tried editing the save file from various VERIFIED sources, but all i found was that they were in perfect order. Nothing indicated that the ports had erroneously considered itself docked when it wasn't. So drew a blank there too. I simply can't figure out the pattern of successful or unsuccessful docking. Looks like the ports have a mood of their own. What am I missing?? The game runs smooth as butter, but a huge headache when i have to start docking stuff. If it doesn't dock, start the mission all over again and HOPE to work perfectly. I have come to notice that docking had issues in previous versions, say before year 2015. Very rarely have docking problems been reported in 2016-17, so I assume it's been debugged. So what would be my issue? (I would have attached my quicksave.sfs file, but u cant figure out how.)