Hudsonkm

So I removed the mods, and then downloaded the combined unstable 112.0.0 release with all USI mods in it. Now I can see the USI life support icon. Not entirely sure why I couldn't get it to work with just USI LS. After installing the combined pack, everything was working fine. But then I went and replaced the version in that total package with the newest bleeding edge LS release. At that point the issue returned where I couldn't see the icon no matter where I was.

So I finally decided to move on to KSP 1.12.2 from 1.11. Until now, I've never had an issue with any of the USI mods not working. In 1.12.2 however, I can't get the USI LS icon to show up on the toolbar in ANY location. This includes KSC, VAB, or space. This is on a fresh install of KSP, and with very few mods. I am guessing I am just missing a dependency perhaps? Or something else that I might be overlooking? I saw in earlier posts, people were able to get it running in 1.12 with the most recent release. The issue happens to me in brand new sandbox, as well as new career. Should also mention Ive started completely fresh, installing KSP, and then the mods 3 times now while trying to figure this out. USI LS - 112.0.1-bleeding-edge.1 KSP - 1.12.2 Breaking Ground - 1.7.1 Making History - 1.12.1 USI Core - 1.4.0 USI Tools - 1.4.0

Ahh no problem. Thanks for the reply clearing it up.

Hrm...AVC started telling me there is a 17.3... Only seeing 17.2 as most recent. Wasn't getting this yesterday.... Bug on my end?

Alright will try that! TY for the info.

So.... Was looking at the debugger, and eventually saw something which led me to try uninstalling Kronometer. Restarted the game and could once again enter the VAB and SPH, and leave the astronaut complex. The problem did not happen when Kronometer was installed WITHOUT FAR, but the two of them together at least in my case seemed to be causing the issue. These strange FAR toolbar errors only would happen in my install when both are installed. Once I uninstalled Kronometer I didn't see these errors in the console. I am not even sure if these errors should even be causing the problem? Somebody that knows more about this may have a better idea of what is going on. These errors do not show when I click on VAB or SPH and try to enter but cant. They pop up when I enter the astronaut complex and try to leave back to the KSC. But yeah, they only show up with both Kronometer and FAR installed... At least in my case.

Just came here to post that I am having the exact same issue. I install it, and start up a new sandbox game and cannot enter the VAB or SPH. I quit, uninstall FAR, and then start a new sandbox game and everything is fine. Quit again, and install FAR again to doublecheck and I can't enter the VAB or SPH. Before I do any serious digging I figured I would first post about this to see if anybody else has experienced it. I definitely didn't have the issue in KSP 1.11. Also, this is a completely fresh install of KSP. When I decided to finally move to the latest version, I installed it and then went and installed all of my mods over again, confirming compatibility first of each of them with 1.12.

Disregard. I figured out what the issue was.

So I took the extra step of reinstalling KSP completely, and reinstalling all of my mods and then starting a new career save. As soon as I researched one of the nodes where a part was that was being duplicated, it started happening again. If I check the tech tree, then enter the VAB, then come back out and check again, it adds 2 more entries of that part. It also adds 2 entries if I exit to main menu and then load my career save back up again. I'm heading out to run some errands now but will get some logs up as soon as I get a chance. To be honest I am not all that concerned about it since it isn't duplicating the parts themselves, but could it cause problems or performance issues just from how bloated the save file eventually gets with all the entries? When I first noticed this problem initially, there were around 6 hundred duplicate entries for each researched part where this was happening. LOL made it very difficult to scroll through the list of parts on that researched node.

TY for the reply! Luckily I am not all that far into my current career save. I will start a new career as suggested and see how it goes.

Thanks for the reply. Will wait and see what they say. It is odd that it isn't happening to every part in the two mods where I am seeing it happen, but only to 1 part in the cacteye, and 3 parts in surface experiments pack. Even more strange is that I discovered that it isn't just every time I load the game, but it even adds an additional entry if I enter the VAB, and then exit, and then check the tech tree again! LOL no wonder I had hundreds of additional entries with these parts.

So I have a further update on this. It isn't just adding entries when I load the game. It is also adding entries while the game is loaded and I am playing! For example these three parts from the surface experiment pack, as you can see here have many duplicate entries in the first image. These are the parts SEP.Box, SEP.StorageLong, and SEP.StorageShort. However, if I enter the VAB, and then leave and check the tech tree again it has added two more of each of those entries in that node in the tech tree. As indicated in the 2nd image. The same thing is happening with the part tele.gru1 from the cacteye telescope mod. It add's two entries of that each time I enter the VAB, exit, and check the tech tree again. Edit: just noticed it is happening with probeCoreSlim as well. But I can't for the life of me remember which mod that is from. Also SEP.FallenKerbonaut from surface experiments pack.

So I know that the issue of duplicate researched nodes have come up a few times, but I have noticed something fairly bizarre in relation to the problem. So I started my save using CTT, and didn't install it later on. And I started to notice the duplicate entries of a few items in my already researched nodes. After awhile, I noticed that the number of duplicates continued to increase. So I finally went in and edited my save to delete the duplicate entries, and figured the problem would be solved. But not long after I noticed they were back again. And more so, I realized that it is adding a duplicate entry for specific parts each and every time I load my save. So immediately after editing the save so that it is back down to only a single entry of a part in my researched nodes, quitting, and reloading the save, I then find one additional entry. After reloading again, another, and so on and so forth. So using this part as an example, after 4 reloads of my save, there is an additional 4 entries of the part. part = tele.gru1 part = tele.gru1 part = tele.gru1 part = tele.gru1 part = tele.gru1 This is for the cacteye telescope mod, and it isn't happening for every part from that mod that I have researched. It is only happening for the part from the mod shown above. The same thing is also happening for me with 4 parts from the surface experiment pack. Initially, I had hundreds of duplicate entries for these parts that I went in and deleted.

So I am having a really bizarre issue. I had the problem where i had a ton of duplicate entries in my tech tree, and did a bit of research until I figured out how to edit my save file and remove the duplicate entries. However, after doing so, I realized that the issue persisted and the duplicate entries continued to be added to the tree. This is for already researched nodes, and the entry in question is part = tele.gru1 I went back in and deleted the duplicates again, and after a few reloads I realized it is adding a new instance of part = tele.gru1 every single time I load my save file. So after each load, there is one additional duplicate added to my save files tech tree list under advFlightControl. So after quitting and reloading my save four times I am back to 5 entries. It isn't doing this for any other Cacteye parts I already have researched. part = tele.gru1 part = tele.gru1 part = tele.gru1 part = tele.gru1 part = tele.gru1 I apologize if this has already been addressed elsewhere and I somehow overlooked it. But if not, any ideas? Edit : Also only just noticed that the exact same thing is happening for two parts in the surface experiment pack too. Edit2: Also posted about this in community tech tree since I am guessing it could very well be an issue caused by that mod.

Thanks for the info! Much appreciated!

Just a quick question for anybody that can answer. I am returning to the game again after not having played regularly for quite a few years now. I have looked for the answer to this and have read a lot of conflicting suggestions. I want to either use the 4k or 8k textures but I was curious as to how big of a performance hit the 8k textures cause and what the exact recommended PC specs would be to use them? Currently am using the same machine that I use for editing work to game on. An i9-7920x with 128gb RAM and a 1080ti... Though the GPU will be swapped out with a 3080ti that arrived today. If I remember correctly, KSP performance is more tied to CPU than to GPU? I could be wrong... It has been quite some time since I last played, so plenty I do not remember.

Thanks for the reply! I could just install everything manually like usual. Just figured I would check and see if there were any mod managers now to make it easier. Will give CKAN a try!

So KSP, being easily what I consider the best game ever made, is one I come back to frequently. So I am coming back to play again after 2+ years since I last played. I first picked up the game 0.18 and it has always been able to snag me back. Anyhow... Seeing as I tend to play with a bunch of mods, I was curious if there any mod managers for the game now days. And if there are multiple, which is the best? Thanks for any help you can give to point me in the right direction!

So strangely enough, after downloading the update, I am having an issue with launch clamps of any sort. On the launch pad they are automatically disengaged and do not show in staging as shown in this screenshot. As soon as I remove the WarpPlugin folder from GameData and restart, the problem goes away.

Thank you all!

Quick question. Say I have a station hub in orbit and I want to fly up a pressurized crew tube to connect the two. Do I still need docking ports on the objects in order to connect them in space? Or are docking ports simply for docking ships and other non station components? Same goes for a fuel tank... Do I need a docking port on the end I want to connect to the station itself if assembling outside the VAB and in orbit? Also, if I do need them, and taking a hub for example again, does both the hub and the object I want to connect to it need a docking port, or just one of them?

The real question is.... "How many people are going to recognize this reference."

Link works now.

Well this is certainly depressing.

I believe I figured out what is happening to cause my problem. It just keeps going up until it finally crashes. Is anybody else experiencing a memory leak when forcing KSP to run in OpenGL?