INSULINt

Members
  • Content Count

    229
  • Joined

  • Last visited

Community Reputation

43 Excellent

About INSULINt

  • Rank
    Spacecraft Engineer
  1. I had troubles getting the original to work post Kopernicus 0.3ish, and the original completely borks 0.5. Nice to have these floating around again, so have all the thank yous!!!!
  2. Ya, this mods cfg files error out with MM and the new EVE release. I like all the clouds so I'm sticking with EVE 7-4 for now LOL. It'll almost be a shame when this gets updated tho, since I don't know if anyone will make duna dust storms a thing again, since it was sort of a one off from what I can gather. 1st world problems, eh?
  3. Ha! I did not know that! You would have to use "steam -applaunch 220200" for windows to launch the game. Translating the sh file to a windows bat or cmd should be fairly simple
  4. 1 - I don't know if this would also be possible in OSX, but depending on how it handles shortcuts/symlinks it should be possible. AFAIK, impossible on windows. 2 - This is more for people who use steam. Sure you can have multiple installs on steam, but then only 1 can use the steam overlay, add to your hours played amount, etc. All I can think is that this might save a minuscule amount of space for non steam people, or maybe be a little more organized? OK, now that that's out of the way, what am I talking about here? I'm talking about using symlinks in linux to have different GameData folders that you can launch the game with different part/mod configurations, but have a communal settings.cfg, and all your saves in one place. For the text part of this I'll stick to a dual stock/modded setup, but for mine I actually have 3: stock, some info/utility mods, and then modded to all craziness. First, lets set up the multiple GameDatas: 1 - Choose a location for them, I picked ~/KSP.Installs, then create your subfolders there for each GameData (eg. Stock, Modded) 2 - If your current install is modded I'd suggest cutting a pasting your GameData folder from your KSP install location into the Modded folder, then verify files in steam and cut/paste the new stock GameData into Stock. If you're running stock, copy/paste the KSP install GameData to both Stock and Modded, then add mods to Modded as desired. 3 - Delete your KSP install GameData folder if it's still there. You won't need it, and it'll confuse the launch scripts if it's there. Now, to create the scripts. Create a file named something like KSP.Stock.sh and put this inside it: rm ~/.steam/steam/steamapps/common/Kerbal\ Space\ Program/GameData rm ~/.steam/steam/steamapps/common/Kerbal\ Space\ Program/PartDatabase.cfg ln -s ~/KSP.Installs/Stock/GameData ~/.steam/steam/steamapps/common/Kerbal\ Space\ Program/GameData steam steam://rungameid/220200 Note that this assumes you put your stock GameData in ~/KSP.Installs/Stock, and that your have KSP/Steam installed in their default configurations. Now mark it as executable through the properties window or "chmod -x" and run it. If you run it in a terminal, there will be at least 1 error saying that ~/.steam/steam/steamapps/common/Kerbal Space Program/GameData isn't there, and that's fine, cus the folder shouldn't be. There should now be a symlink to the Stock/GameData folder in the KSP install directory, and it should load up as stock. For the Modded script: rm ~/.steam/steam/steamapps/common/Kerbal\ Space\ Program/GameData rm ~/.steam/steam/steamapps/common/Kerbal\ Space\ Program/PartDatabase.cfg rm ~/KSP.Installs/Modded/GameData/ModuleManager.ConfigCache rm ~/KSP.Installs/Modded/GameData/ModuleManager.ConfigSHA rm ~/KSP.Installs/Modded/GameData/ModuleManager.Physics rm ~/KSP.Installs/Modded/GameData/ModuleManager.TechTree ln -s ~/KSP.Installs/Modded/GameData ~/.steam/steam/steamapps/common/Kerbal\ Space\ Program/GameData steam steam://rungameid/220200 And this should load up the game using the Modded/GameData folder. Now, the reason for the rm commands for PartDatabase.cfg, and all the module manager data files, is that I've found that when adding or changing parts even in a single install removing PartDatabase.cfg prevents buggyness when you load the game again. The same reasoning applies to the MM stuff. By deleting those files I'm hoping to prevent 99% of the problems when I start the game. Anyways, hope you all find this interesting at least, and here's some pics of the folders/scripts as reference:
  5. Edit: nvm, removing remotetech doesn't remove the error from happening.
  6. It's definitely something in the kerbolplus folder that kopernicus doesn't like. I now have a successful install of Trans-K, OPM+Sigma and K+, with everything from the latest zips, using K+'s Kopernicus system.cfg and dll, but using the KerbolPlus folder from the 2.0.5 zip. - - - Updated - - - Just found the problem. Line 53225 of output_log. Exception: "Ganag-Kal" not found. at Kopernicus.Configuration.Loader.Generate () [0x00000] in <filename unknown>:0 at Kopernicus.Injector.Awake () [0x00000] in <filename unknown>:0 UnityEngine.GameObject:Internal_AddComponentWithType(Type) UnityEngine.GameObject:AddComponent(Type) AddonLoader:StartAddon(LoadedAssembly, Type, KSPAddon, Startup) AddonLoader:StartAddons(Startup) AddonLoader:OnLevelWasLoaded(Int32) Looking at the configs (you added kal since 2.0.5?) Kal has "referenceBody = Ganag-Kal", but you've set the name in Ganag-Kal.cfg to "Ganag-Kal-Barycenter". Also, Ganag has "referenceBody = Sun" (possible typo?) EDIT: Changing "Ganag-Kal-Barycenter" to "Ganag-Kal" fixes the stuff not loading issue. Basically makes Kal a moon of Ganag tho. It makes sense now why there was 1 MM patch amount difference: You removed Calad, but added the Barycenter AND Kal, which loaded, but made Kopernicus angry because of grammar, basically
  7. I have the same problem. The Kopernicus config loader throws an exception at startup, and I get no planets with the latest Trans-Keptunian and OPM+Sigma. 2.0.5 works fine. In both cases I'm using OPM's Kopernicus system.cfg and dll. Logs: https://www./folder/b4u546vdp761b/Kerbol_Plus_Logs EDIT: hope this helps. I love this mod! EDIT: There is also 1 less MM patch when I switch back to 2.0.5. MOAR EDITS: It also seems Calad is no longer in the latest build?
  8. Super excited that this has been updated for stock!
  9. Not really. I believe the mk2 and 3 parts are mass balanced for fuel. If an lfo tank has 10 tonnes of fuel, the equivalent lf only tank has 10 tonnes of lf in it. And it's not like the intake/lf stuff that have the excuse of having part of their volume taken up by intake equipment.
  10. This works in 1.0.2 but does kill the roids orbiting dres. It's a hard decision between roids with difficult orbits and the dresteroids
  11. Personally, i use tweakable everything, so i love the stuff that stockplus adds the number of fairing splits is my fave right now! It just makes the fairing separation look better
  12. Not sure if this has been mentioned, but I realized after watching Scott's vid on the LV-N that the mk1 liquid fuel only tank is WAY underfilled. 150 LF in the same space as 180LF/220OX? Looking at the mk2 parts, the LF only tank has 400LF and the LF/OX has the same 180LF/220OX as the mk1 half tank. Easy MM fix, and it makes the tank actually weigh around the same as the LF/OX one, much like the mk2 parts, which also makes me think this is somewhat of a stock "forgot to carry the 1" type thing... @PART[MK1Fuselage]:FIRST { @RESOURCE[LiquidFuel] { @amount = 400 @maxAmount = 400 } }
  13. Yes, both part are on those probes, and I stumbled upon why I had data from kerbin: I activated the narrow band on that sat, but not the others. I didn't even realize I'd activated the narrow on the kerbin one :/ Crazy bug for sure, but the basic "workaround" is activating the narrow band. Also realized I need the MKS orbital camera (MKS_Antenna part) to zoom in on the other resources, so I tested out the survey scanner with the MKS part. The MM patch for the MKS part doesn't kill the survey's ability to scan those other resources. Active module vs. not?
  14. LOL, sorry for not including that detail There is no Ore % readout on the big map, except for kerbin. Here's the persistent.sfs file. It's far from stock, but maybe it'll help? http://www./download/kj89t6kb5knnp5f/persistent.sfs