Hlothwig

I think all he posted was his patched version and the errors it put in the log. It looks like you already tried that and couldn't get it to work. It's a shame nobody with the skills to update this mod has the time and motivation to actually finish the job - this is a great mod, and I was really looking forward to using it in my new install. If I understood anything about how it worked, I'd try my hand at updating it myself.

@Olympic1 Figured out the issue, I'm running KSP 1.1.2 because 1.1.3 apparently has orbital glitches with some of the mods I use

That's the thing, 1.0.5 is the latest version CKAN has for Kopernicus. After I resolve this issue I'm uninstalling CKAN, it's more trouble than it's worth. No offense to you or any other developer, of course, it's just that it just can't stay on top of every single mod update, and when I have to update them all by hand, I figure I may as well be modding manually.

@Sigma88 Both pastebin and google docs crashed their tabs when I tried to paste the config cache, so here's the dropbox links. https://dl.dropboxusercontent.com/u/90666681/ModuleManager.ConfigCache https://dl.dropboxusercontent.com/u/90666681/Prima.Body.log https://dl.dropboxusercontent.com/u/90666681/Secunda.Body.log https://dl.dropboxusercontent.com/u/90666681/PrimaSecunda.Body.log Edit: Glancing at the PrimaSecunda log, it seems I may have an outdated version of Kopernicus. Curse you CKAN!

@Sigma88 Anyway, is there any particular place I should upload the logs and cache, or should I just link to pastebin?

Pkmniako's "Other Worlds" mod had an outdated SigmaBinary patch (at least, I think that was the problem; it used to crash the game and blame bad SigmaBinary configs when I tried to load Other Worlds, and now it just doesn't change Prima at all), so I've been trying to get Prima and Secunda to be binary again. (For the record, the Other Worlds config says "needs SigmaBinary 0.2.4".) This is my config patch based on the DunaIke patch: I also renamed the file to "PrimaSecunda", but it didn't work, so I deleted it and directly edited my copy of the Secunda config. This is the edited Secunda config - all I did was add "SigmaBinary {}" right at the start of the Body node.

@Sigma88 I can't seem to get it to work. I tried editing the secondary object's cfg file and putting "SigmaBinary {}" inside the Body node, but maybe I didn't put it in the right place, because it didn't seem to work. I tried copying and editing the DunaIke patch to use the names of the bodies I wanted to be binary (changed the file name and the body name in the file), and putting that file in various places, including the secondary body's directory, but that didn't work either. If it makes any difference, the primary object orbits something other than the sun. I feel like a chimpanzee fiddling around with a drill hoping to stumble across the power button while a construction professional watches me and facepalms.

A question from an idiot: How do I DunaIke? I seem to remember a separate patch for making Duna and Ike a binary system, but I can't find it anymore, and I don't quite understand where the SigmaBinary node is supposed to go. Is there an Ike cfg somewhere? Do I need to create a separate file? I think I understand the basics of Kopernicus syntax, but that's about it. Really the reason I'm asking is that I'd also like to apply this to some other planets I have that are supposed to be binary but aren't. How would I go about doing that? It seems relatively simple, but again, I'm just not quite sure where I'm supposed to paste the empty node. I apologize in advance for wasting your time if it turns out I'm just a total moron.

This mod doesn't move the sun. It adds another star by putting it in a distant orbit of the sun.

Well, I tried that and it worked... kind of. The Mk II and Mk I still have their prices swapped, but whatever. For 175 spesos I'll make my own ladder. Two new questions: 1. Why is the Dachsund still in general rocketry, and not basic rocketry like its flavor text would imply it should be? 2. Since the pruner still doesn't work, is it possible to get a version of this pack with just the new parts that doesn't overwrite Squad textures? Much as I love the Ven ones, having both is killing my memory usage and causing overflow errors every time I return to the space center. 3 (bonus question). Is there any way to change these things myself? I tried deleting everything but the parts bin, and it destroyed the LVT-15 Dachsund, the LV-900 Beagle and the NT-5R Shiba.

I seem to have a problem with the Mk1 Cockpit IVA. RPM works fine on everything else, but the Mk1 cockpit RPM screen just displays some 'not found' errors and a retro KSP logo. I thought it might be related to Active Texture Management, but I uninstalled that and copied all my mods into a new directory that I copied out of Steam and the issue persists. It's not a huge deal, since so far this is the only one that broke, but it's annoying not to be able to, for example, get a view through an underside camera to make landing easier.

Well, here goes (spoilered to save space): Aside from Ven's Stock Revamp, only SpaceY, RLA, KIS, KAS, Jump Beacons, and the Alcubierre Drive add any parts, and none of them add ladders. Edit: And upon updating from 1.9.0 to 1.9.1, all of the ladders are gone except the original Pegasus. That's a shame, I liked the square ones.

I somehow seem to have two sets of three seemingly-identical ladders, one in the shape of Pegasus Mobility Enhancers and one with its own style (with vertical bars as well as rungs). They have different names but identical flavor text, and one set costs all the same while the other's pricing makes no sense, with the medium one costing less than the short (regular Pegasus) one. This is the only pack I've installed that affects ladders, so can somebody tell me what's going on?

@Virtualgenius I don't keep my modded installs in my Steam directory, I keep them on my desktop for easy access. I'll try what you're suggesting, but it will take some doing. It seems like only the Mk1 Cockpit is affected by the original issue - RPM worked fine in the Mk1 Command Pod and the Probe Control Room. I've also updated RPM since my first post, and the issue is still the same. EDIT: So I copied all my mods into a new directory that I copied out of Steam. Not only does the RPM for the Mk1 Cockpit still not work, but the issue I installed ActiveTextureManagement to fix - game crashing when returning to space center - is back. Edit2: In retrospect this seems to indicate the issue has nothing to do with ActiveTextureManagement, so ignore me.

I have this problem too, with aggressive. It's really frustrating as it seems to break RasterPropMonitor even after uninstalling. This is pretty serious - do I have to copy the whole directory out of Steam again and reinstall all my other mods? I don't want to break my save too.