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
    Yes it does.
  2. JPLRepo
    Correct. It is also very useful for fuel transfers where using the resources app to highlight the part/resources Part Action Windows pop-up. You don't have to search around for the part, or trying to find them inside fairings/etc.
  3. JPLRepo
    Correct. Only the shrouded ones were changed to have higher impact tolerance. As they are shrouded.... The ones without shrouds were not. That's not to say you could mod all of them. There are apps in the game... (the icons at the bottom or right side of the screen depending on what scene you are in). a PAW is the Part Action Window (when you right click a part) The resources app is the one in flight that shows the resources on your currently active vessel. The change was you can now Pin (the pin icon) a Part Action Window that is opened automatically when you highlight/select resources in the resources app. And when pinned you can now transfer resources between parts.
  4. JPLRepo
    That has been explained several times. It's not a bug. But what was done in 1.5 is the shrouded extendable panels now have separate crash tolerances when they are retracted.
  5. JPLRepo
    yes that should work.
  6. JPLRepo
    New PartTools are available via this thread. https://forum.kerbalspaceprogram.com/index.php?/topic/160487-parttools-updated/
  7. JPLRepo
    PartTools for KSP 1.5.0 has been updated. Link in the opening post above. This includes the new part shaders. Also fixed a bug with localspace offset on IVA models (when exported) then being spawned for prop placement being placed in the wrong position in world space when spawned from parttools. NB: PartTools still requires Unity 2017.1.3p1.
  8. JPLRepo
    API docs updated for 1.5. link in opening post.
  9. JPLRepo
    Coming [Edit]:
  10. JPLRepo
    the order of the list should not matter.
  11. JPLRepo
    Correct. IGNORELEVELS { // body = easy normal medium hard Sun = true true true true Kerbin = true true true true Mun = true true true true Minmus = true true true false Duna = true true false false Eve = true true false false Jool = true true false false Laythe = true false false false Vall = true false false false Tylo = true false false false } the true false indicates if a planet is available at the start of a new career game depending what difficulty level you set for the game.
  12. JPLRepo
    No you cannot.
  13. JPLRepo
    This mod works fine in 1.4.x (including 1.4.5).
  14. JPLRepo
    Sounds like potentially some of the part categories aren't quite right if you aren't seeing all the parts. They should appear in their appropriate categories. Not following.... they look fine to me in 1.4.5. Which btw - this mod works fine in 1.4.5
  15. JPLRepo
    [ERR 10:00:22.605] [HierarchyUtil]: CompileID failed because it reached the scene root without finding a 'SpaceCenter' game object - Means some mod you have installed is moving the SpaceCenter object. So ResearchBodies can't find it. Contracts should start to appear after:- You Reach space. You have observatory level 1. You have tracking station level 2. If you take a picture with a TST telescope of a body not discovered - it is discovered - but not researched. If you take a picture with a TST telescope of a body discovered but not completed research. Each picture increases the research value on that body. (after you return or transmit it). I don't know what "James Webb type" telescope is.. not one of my mods. No idea... nothing to do with this mod... no errors in the gigantic log related to this mod. science mode - this mod recommends career mode... playing in sandbox/science sandbox - there are no contracts.. and things will appear odd. The Ground telescope is referring to the Observatory itself. Look at it - it's a giant telescope.
  16. JPLRepo
    I am not following. You don't want help?
  17. JPLRepo
    No there are 8 galaxies in the mod. As to the reason you don't see anything... I can't answer that. because: a) No info supplied about what configuration of mods you are running. b) No info about what versions you are running. c) NO LOGS. No logs = No Support.
  18. JPLRepo
    My comment wasn't directly at you.. rather a general statement. Raising good bug reports with as much info as you can provide to help us; means we can help you. One line statements on a forum about a potential bug you may have found are unlikely to be noticed by QA or Devs.
  19. JPLRepo
    Because that wasn’t what was reported; but rather was the root cause of the problem once the bug report was investigated. The point is: if you find something you think is a bug. You raise a bug report on the bug tracker with as much inf - save files - logs etc. which provides QA and Devs much more info to investigate and identify a bug , it’s root cause, and apply a fix.
  20. JPLRepo
    Have you raised a bug report on the bug tracker? or know of one already raised?
  21. JPLRepo
    That got asked about one page ago.. and has been asked many times before.
  22. JPLRepo
    The API docs have been updated for KSP 1.4.5. and Making History 1.4.0. Link updated in the opening post.
  23. JPLRepo
    Was the same issue. Should be fixed.
  24. JPLRepo
    That is exactly what the new behavior is. You are given a warning before it loads the save... so you can choose to continue or not.
  25. JPLRepo
    It will still delete them if it can't load them. (missing parts, etc). * Fix fairings and shroud displacement when switching to vessels. Not sure what bug you are referring to there. Do you have the bug number?
×
×
  • Create New...