DestinyPlayer

These days it's probably better to use LibreOffice, because OpenOffice has sort of been abandoned. At least from what I remember.

Oh, I wasn't actually complaining about Kopernicus taking too long. I can wait, and I also perfectly understand just how much effort and energy is required for modding. As an amateur writer, I know that even just putting words on the screen is often times difficult enough. No, my main complaint was about me spending so much time debugging a modded install of KSP, and only then discovering that Kopernicus isn't yet updated, so now I'm stuck with either backporting and doing all of that all over again, or playing without Kopernicus. More of a "laugh at my misfortune and poor observational skills" complaint than a "please update soon" complaint, I guess.

Grumbles endlessly So, I installed all the mods that I wanted for 1.8.1. I made sure the install runs while waiting for my planet pack of choice to download (it was really fat), so I didn't have Kopernicus installed yet. So what do I discover? The friggin' thing doesn't support 1.8.1 yet, after I spent several hours debugging things with my other mods, so now I'm stuck with a pack built to end in going interstellar, without having anywhere to go interstellar to... Just wanted to get it off of my chest. Continues grumbling

Same problem as well. The Research Bodies window shows up as blank. Haven't rebooted yet, I'll see if it helps later.

Personally, I wanted to use both of them. This Warp Drive for "To Boldly Go", USI's warp drive for whenever I need to actually roll around a system with ludicrous speed. I like RoverDude's warp drive more, but it's impossible to use if you want to go from system to system simply due to the lack of time warp.

Well drat. Even on 1.2.2? That's sad.

The Warpotron screen refuses to open up. It's just a tiny, thin line on my screen. And with that, every time I put the Warp Drive onto a ship, it floods the console with a buttload of errors. KSP version is 1.2.2, but CKAN said that it's compatible, and the version checker doesn't say anything. Modlist If you need the KSP.log, please tell me. The latest one is, sadly, from a game where I hadn't used it.

My apologies, completely forgot about that. Here's the log.

Hadn't there been a 1.2.2 version of To Boldly Go? Or am I mistaken? Not asking for a backport or anything, I'm just confused, because I thought that I'd played it a few times on the older version and I can't find it anywhere...

Well duck a truck. It was indeed the VPN. I've gotten 1.2.2 and checking it right now with the (approximately) same mods but older versions, but I probably should do the proper debugging process on 1.3 now that the slowdown is over. After a minute: What the hell. 1.2.2 crashed with the exact same error. Actually nevermind, I might have accidentally started up 1.3. Lemme check again. In a moment: Yes, that was the problem. Checking for other incompatibilities. Yes, 1.2.2 works. The only problem was that CKAN decided to do a stupid and download the 1.3 versions of RoverDude's mods.

Isn't it basically saying the exact same thing?

Thank you for the suggestion, but sadly it didn't work. Still loads as slow as before. For some reason it spends the most time on sounds and textures. I did have a VirtualBox adapter, and turned it off. The most annoying thing is that it does work on my laptop, with the exact same mods. There's just something about my PC it doesn't like. As a sidenote: Could it be that KSP/Unity doesn't work well with a turned on VPN to Sweden that affects everything?

The vanilla game also loads for a ridiculously long time, so won't be much of a change.

I would have done it that way from the very beginning. But it will take literal days to do that because modded KSP loads for... About two hours last time I checked with a stopwatch before crashing. That's why I asked if anybody knows what the problem is. But it feels like at this point, that's the only way.

Deleted Firespitter, it's not the case. Still crashes with the same exact error.

Okay. I deleted the entire KSP folder. Then I proceeded to uninstall KSP from Steam, reinstall it again, copy it over into a separate folder, download a brand new CKAN exe, and used the exact same .ckan file that worked on my laptop. The exact same bloody crash. What the hell is going on? The base game starts up all right, even if it takes half an hour to load... Is there something with my hardware or something? Because both the laptop and the PC have the exact same version of Windows 7 on them so it can't possibly be software.

The problem is, it was a clean install. I'll try to delete everything and clean install it once again when I get back on the PC.

Okay. I just exported CKAN's modlist, moved it to my laptop, and installed it there. The exact same mods, the exact same CKAN, the exact same KSP. On the laptop, KSP loaded perfectly. I am at a loss for words. What is going on.

More or less. There used to be ones I never used, but I've since removed them in trying to get the game to work, and it still crashes.

The last thing that loaded used to be Universal Storage. I removed it. Now the last thing before the crash is Roverdude's Aldubierre Drive. Not only is it highly unlikely that his mod would break anyhting, but I also am absolutely certain that that specific version works with 1.3 from playing it on my laptop.

The problem isn't the amount of mods, since I have 12 gigs of RAM. The problem is that one of the mods seems to be the wrong version, but I'm absolutely confused about which, because I literally checked every mod's version and it is up to date. I would've considered adding/removing mods one by one, but it would take literal days because KSP also seems to load like a snail on a turtle on this setup, seemingly because my dual core (for some reason task managed splits them into four) processor is not fast enough to load textures and icons quickly. So I'm stuck in the annoying situation where I know what to do to figure stuff out, and I have enough skills to do it, but I still can't do it because of the load time taking literal hours (most likely about one and a half or something)

qQwQq

Did just that. Deleted everything where the version was either unknown or unupdated, everything else is completely up to date. Still crashes with the same error. Current Modlist Didn't get the actual crash log due to some checking with a side program to figure out specifically what is crashing the game, but from what it seemed it's still the same. Later: Got a new one, same modlist.

Basically, I get the mono.dll access violation crash every time I try to load up KSP with these mods. I've got absolutely no idea which one of them is outdated, since I've installed all of them from CKAN, and it said that all of them are compatible with 1.3, so as a result I have absolutely no idea which one of them is the one that breaks everything. Could anybody please help? I would have done the manual "remove all mods and add one per one until it breaks" myself, but Kerbal seems to also load for an hour on this setup, and only crashes at the very end, so it would take literal days to try and figure out which one it is.

Nintendo, I think? Not sure, but my point is that it's still a stand-up guy thing to do, no matter the technical legality, at least in my opinion.