Zeggpold

Thanks, that does the trick!

Is there some way to tell ckan not to try to update a given mod? I've looked at the wiki, the manual and FAQ, and tried searching this forum topic without luck, but I'm hoping there's something I'm missing. I'm asking because of Aviation Lights; the last version in ckan (4.1.3) breaks my save, so I either have to use 4.1.2 or use the newer version, Aviation Lights L, installed manually. But in either case, ckan wants to update to 4.1.3 (which is not really an update for the L version). Lisias apparently has a pull request to allow the new version into ckan, but is there anything I can do until that's taken care of?

Thanks for adopting this! However, I'm not seeing this on CKAN. Is that something you know about, or should I bother the CKAN folks?

I guess we should be switching over to the Aviation Lights /L sequel (and I'll do that as soon as it shows up on CKAN) but 4.1.3 appears to be missing the old(?) lights, which I still have in my save. Reverting to 4.1.2 allows me to load okay.

It looks like Euribanne and Palloocus have the exact same semiMajorAxis (68773560320). This causes problems with the Sentinel telescope (starting or stopping it fails with an exception in the log file (similar to the issue here). I would think moving one of them would fix the problem, but I had to move both.

Could you send your config files? I tried making the change you suggested on MainClouds and my volumetric clouds disappeared entirely. And when I tried turning on Volumetrics on the CirrusClouds, the whole world turned into a cloud...

Yes, I see that as well. The volumetric clouds appear (around 2500m) and disappear (around 10000m) abruptly. I found this so immersion-breaking I stopped using AVP. (But did re-install with CKAN to test with 1.12.1.) I'm on Linux, not other visual mods installed.

KIS 1.28 is not compatible with 1.10.1 (or earlier, presumably), but CKAN thinks it is. The suggestions was made in that thread to report that here.

Thanks for keeping this mod alive! I think it's the most Kerbally (and therefore most enjoyable) life support mod. I am having a couple of issues. I'm running KSP 1.81. on Linux with Snacks v1.25.2 installed by CKAN. First, I'm having trouble figuring out how much Snacks should be produced by the Mobile Processing Unit. As seen below, it reports "Max Production: 21.60 Snacks/day", but I get more like 4 or 5. I thought maybe the Kerbals were eating the rest (though that seemed too many), but when they stepped outside to faint, er, relax, the accumulation rate actually went down a little. (10 days with Kerbals gave me about 48 snacks, then 10 days without them gave me 44). There seems to be plenty of power and ore. Second, I can't see the Snacks entries in the KSPedia. I do see this in the Player.log file: (Filename: ./Runtime/Serialize/SerializedFile.cpp Line: 204) The AssetBundle 'file:///home/purtill/games/KSP/KSP_linux_1.8.1.ckan/GameData/WildBlueIndustries/Snacks/KSPedia/snacks.ksp' can't be loaded because it was not built with the right version or build target. (Filename: ./Modules/AssetBundle/Public/AssetBundleLoadFromAsyncOperation.cpp Line: 445) Error while getting Asset Bundle: The AssetBundle 'file:///home/purtill/games/KSP/KSP_linux_1.8.1.ckan/GameData/WildBlueIndustries/Snacks/KSPedia/snacks.ksp' can't be loaded because it was not built with the right version or build target. AssetLoader: Bundle is null Maybe a Linux thing you can't do anything about, but I do see entries from other mods (DMagic, SCANsat and Universal Storage).

I'm running KSP 1.8.1.2694 on Linux. Installing just this mod (0.8.5.4) via CKAN and it's dependencies: Click thru blocker 0.1.95 Toolbar controller 0.1.9.4 Zero MiniAVC 1.1.0.1 Everything seems to work okay, except the icon doesn't change when I hit F6, so I can't tell if the mod is active or not. Here's the Player.log file. I see lots of lines like: ToolbarControl: Cannot find texture to load:AutomatedScreenshots/PluginData/Textures/Auto-38 The actual directory name in GameData is AutomatedScreenShots (note the second capital S), so it looks like this is why the file is not found (Linux being case sensitive). I can't move or link that directory (I get an error message at startup saying AutomatedScreenShots has been incorrectly installed), but if I create a new directory AutomatedScreenshots/PluginData/Textures with just the .png files from AutomatedScreenShots/PluginData/Textures, the F6 does toggle the camera icon (and screen shots are created). (Crtl-F6 doesn't seem to do anything, but I don't need the auto-save functionality.)

I'm having a problem where as soon as I move my mouse into and then out of the Kaptain's Log window. the mouse cursor disappears. This is on Linux (Gentoo), 1.8.1.2694, no DLC, with the mod installed via CKAN and no other mods except what CKAN thinks it needs. Here's a link to a run where I just started up, clicked on the icon to open the Kaptain's Log window and moved my mouse in and out and eventually exited. (Without the mouse cursor, it's difficult to click on the exit confirmation.) Player.log

The video was the attempt with the parachute unaltered. I hadn't noticed the SAS but that might be the difference. I'll give it a try when I have a chance. [edit]Yup, that was the difference. Thanks to all, I'm marking OHara's answer as "the answer" since that's the one that answered my title question.[/edit]

Thanks for the inputs, everyone. Ohara, thanks for the analysis. It does look like the shape of the booster is different in the training flight. As you say, I know how to work around this (and there are more ideas below), but I wonder about a newcomer. Plusck, that's a great point. Too bad Squad didn't see fit to include it in the training flight. Rocket in My Pocket, your flight looks like just what I was trying to do at first. But when I try that with the chute set to the defaults, I get a message "[Mk16 Parachute]: Chute destroyed by aero forces and heat" at an altitude of about 9500. (I also don't see the same information as you in the parachute info box.) My flight on youtube (doesn't seem to be embedable for some reasons): https://youtu.be/Ae3txAVECho. if you (or anyone) could see what I'm doing differently, I'd love to hear it. bewing, that's another great idea that Squad didn't see fit to mention in the training flight.

Long story short, I do the first two training missions (build and launch). Everything goes fine. If I do the same thing in the actual game, the rocket goes higher (altitude of around 23000 rather than around 15000). The result is that the parachute won't work: if I change the pressure value to 0.2 (as in the training mission), the parachute never deploys (it turns blue in the staging, then the background turns red---see screen shots). If I don't change the parachute, it deploys and then is destroyed. Linux, 64 bits, version 1.5.1.2334 (linuxPlayer) en-us on Ubuntu 14.04, store version (not steam) no mods. Log files plus screenshots on dropbox here. Of course, I can decrease the amount of propellant in the Flea SRB to avoid this, bit it seems unlikely that should be necessary. (Especially as I didn't find anything else on this searching the forums.) Does this indicate something wrong with my game or system? I did try reinstalling (which is to say unzipping the file again) and downloading again, but neither helped. Any idea what could be wrong?

CKAN only. I have not much time to play KSP, so I don't have time to mess with anything else.