Jump to content

JPLRepo

KSP2 Alumni
 View Profile  See their activity

  • Posts

    3,142

  • Joined

  • Last visited

 Content Type 

Everything posted by JPLRepo

  1. JPLRepo
    V0.23.1.0 published for KSP 1.2.1 Bunch of other changes as well. See the changelog in the OP for details.
  2. JPLRepo
    V0.1.11.0 published for KSP 1.2.1
  3. JPLRepo
    V0.1.5.0 for KSP 1.2.1 published.
  4. JPLRepo
    V1.2 for KSP 1.2.1 published.
  5. JPLRepo
    The default keybinding was changed to cater for OS-X users. there is only one primary, but as its bindable so you can go into keyboard/control settings and change it back.
  6. JPLRepo
    Ok thanks will take a look. EDIT: I want to take a look at this and KAS integration before I do an update release for 1.2.1. In the meantime the current release should work with 1.2.1 (just accept for the AVC version warning on startup).
  7. JPLRepo
    Not if you didn't back it up. Always back up when the new version comes out. Then you will always have that version.
  8. JPLRepo
    Backup/copy you "saves" folder - use the above to browse local files in Steam and you should find the saves folder inside the KSP folder. Then try. A lot of mods should still work with 1.2.1 as it was only a small patch. but if you run into trouble. You always have your backup.
  9. JPLRepo
    Open Steam client. Right click KSP and select Properties. The select the Local Files tab. Select "Backup Game Files" or "Browse Local Files" and copy the KSP folder somewhere safe.
  10. JPLRepo
    I repro'd it and udpated the issue on the tracker. http://bugs.kerbalspaceprogram.com/issues/13023
  11. JPLRepo
    No there are several backups in your backup folder and there is a quicksave there as well. Pick the most recent one : persistent (2016_10_29_18_42_54).sfs Copy that to where the persistent.sfs file is. Delete the persistent.sfs file. Rename persistent (2016_10_29_18_42_54).sfs to persistent.sfs Restart KSP
  12. JPLRepo
    Nothing wrong. Just CactEye is only increasing the research by 2% it would seem. I think the code does not expect that (it expects 10% on discovery) from memory. I will have to take a look at the code and adjust it. So that would be why you couldn't do anything until it hit 12% No I meant disappear from map view/ Tracking station completely.
  13. JPLRepo
    So I downloaded your save folder and had a look. The persistent.sfs file in your download is completely corrupted. There is nothing readable in that file. Your best bet is to delete this file. Copy and rename your quicksave.sfs to persistent.sfs or copy and rename one of the files in the backup folder (choose the one most relevant). As to how your file got corrupted... anyones guess. A mod? or KSP was closed/cancelled whilst saving the game? Hard to know.
  14. JPLRepo
    You can just delete the old part configs if you don't want them in your install. All it will do is break saves and craft files that use them. Yes you could rename the new parts to cover off the old part names if you want in your install. That would have the benefit of not breaking saves and craft files. Should be fine. (tm)
  15. JPLRepo
    This was reported in the pre-release. No need to raise another bug report. It's a known bug. http://bugs.kerbalspaceprogram.com/issues/11520
  16. JPLRepo
    No you can't. The UPGRADE node is applied to a MODULE node. You can't then nest a MODULE node inside another MODULE node.
  17. JPLRepo
    The new parts do have test subjects defined in them (where the part they are replacing had test subjects defined). I think only the LV-909 and LV-T45 did and have them defined in the replacement parts config files.
  18. JPLRepo
    Step1 - I intend to see if I can make the undiscovered bodies completely disappear so you have no idea where they are and cannot target them. If I can do that then step 1 would be a contract to initially discover their dot location. Step 2 - is scanning the sky in the vicinity of their location until they become discovered. Until I figure out how/if I can do step 1 this will be the starting point (as the mod behaves now) and you start by simply scanning (contract) to discover the new body. In step 2 it is still not discovered until the end of step 2.
  19. JPLRepo
    Or you can use this one:
  20. JPLRepo
    This belongs in http://forum.kerbalspaceprogram.com/index.php?/forum/15-modelling-and-texturing-discussion/ But .mu files are a proprietary format written by one of the devs of KSP. You can create your models in any modelling tool. You then need to import them into Unity and use the KSP PartTools toolkit to export the .mu files from Unity. There is also a python plugin that another dev wrote that you can add to Blender (but it can't do the shaders). Edit: You can use that blender plugin (with it's limitations) or export from Blender in fbx format. and import it into a Unity project to complete the part setup followed by a PartTools export from Unity.
  21. JPLRepo
    Are you sure this is in stock? with a stock only save?
  22. JPLRepo
    ah right. No Relay dish. Never mind.
  23. JPLRepo
    OSX Sierra GateKeeper will quarantine any downloaded app. It randomly moves the files to a temp folder when you run it. This causes problems for KSP and Unity apps. By copying the folder permissions are changed and the quarantine removed. and then moving them back again. You can then execute the app. Same goes for downloaded mods.
  24. JPLRepo
    Well I just checked.. and I have no relay issues with the probe built in antenna in a similar simulated scenario. Can you supply a bit more info as the picture is impossible to tell what you actually have there. I can see the active vessel has a connection but which one is that? What kind of relay? does it have power? Does the booster have power? is it in hibernation mode? What probe core is it using? Can you supply save file/craft files?
  25. JPLRepo
    Usually means your save is corrupted or failing to be parsed by KSP. Posting a link to your log and the save file in question might help to determine what is wrong with the file.
×
×
  • Create New...