When we clone this instance, it will be outside of Steam's update jurisdiction.Ģ.5) Okay, so make sure you have the right instance (Kerbal Space Program) and "Path to clone" sorted. This is your regular Steam install and will maybe (most likely) break all your mods every time it is updated! Not good.
Path to clone should read this: C:/Program Files x86/Steam/steamapps/common/Kerbal Space Program The "Path to clone" should read what is below, or wherever you have your steam games installed (for me, it's C:/Games/Steam/steamapps/common/Kerbal Space Program). From the drop down menu, if it's not already selected, click your instance (most likely named Kerbal Space Program).
This will open a new window with two options and some stuff at the bottom.Ĭlick Clone existing KSP instance. Not good! This means every time KSP updates, your mod list will probably break. You will see your regular KSP instance, probably named "Kerbal Space Program". This is where it gets a little confusing, so please pay CLOSE attention. Click this and there will be a little drop down menu. It should do its beep boop registry stuff and then present you a menu of all your mods. Got your folder made somewhere? Great! Remember where it is. I have a games folder where all my games from Steam and GoG are installed, so I just added a KSP folder. Feel free to respond with any questions and I will try to help as much as I can!ġ) First, make a folder somewhere on your drive. Key instructions will be bolded and listed at the end, but I recommend reading everything. However, this is a super easy fix! Allow me to help you solve this issue with different instances of KSP on your machine. With 1.11 coming out, well, today, it will probably break a few games if updated.
0 kommentar(er)
