Jump to content

JPLRepo

KSP Team
  • Posts

    3,066
  • Joined

  • Last visited

Reputation

4,727 Excellent

Contact Methods

  • Twitter
    @JPLRepo

Profile Information

  • About me
    Lead Engineer
  • Location
    Australia

Recent Profile Visitors

29,179 profile views
  1. yeah so this mod doesn't support 1.12 yet.
  2. That contract is not one from this mod. So can't advise you there. No Logs. No support. Not that I'm aware of. But will check it out for the 1.12.x update of this mod.
  3. pretty sure answered this plenty of times before but anyway. Edit your persistent.sfs save file. look for this: SCENARIO { name = ResearchBodies scene = 5, 6, 7, 8 lastTimeCheckedSOIs = 149.18000000000251 RBGameSettings { BODY { body = Sun isResearched = True researchState = 100 ignore = True ContractsWeight = 30 } there is a BODY section for each celestial body. change isResearched to isResearched = False and researchState = 0 to reset them back to unknown/undiscovered.
  4. This is the maximum amount of time that TAC LS will consume resources in a single update cycle of the game. This is particularly of interest when you are not using background resources setting and so the consumption of resources is stacked up the entire time you have switched away from a vessel and then consumed once you eventually switch back to it. and yes.. that time is in seconds.
  5. Will look into this. In the meantime you can turn off the setting to integrate the pod with the temperature in the difficulty settings. No logs = No support, sorry.
  6. We ask if you could raise a bug report on the tracker with your issues. Provide as much info as you can, such as what landing legs? on what celestial body? You're not using any mods? Attaching craft files and save files will also assist in speeding up the bug triage process much more than bug reports with just words or attached videos. https://bugs.kerbalspaceprogram.com The same goes for reporting any bugs. It has a much better chance of being triaged and fixed if it's raised on the bug tracker. And I'm not saying it will get fixed, just that posting it in a forum post saying, such and such is not working has to then:- a) be noticed by a staff member. If ever. b) be then reproduced by a QA staff member if possible with the little info we can gather. This can take some time. before it even gets into the usual triage and possible bug fix list.
  7. We know about the MK1-3 command pods flag and the issue with the linux scrollwheel.
  8. If you can raise a bug on the bug tracker with details about how to reproduce the bug you are referring to along with copies of your logs then we can get our QA team to look into it. https://bugs.kerbalspaceprogram.com/ Without that information we are flying blind and have to spend hours trying to replicate your problem. The more information you can provide the better.
  9. Download 1.12.1 patch and you should be good.
  10. Download 1.12.1 patch will fix this issue and you can turn that game setting to clear up debris around the KSC back on.
  11. This bug was fixed by the 1.12.1 patch. Download it and you should be fine.
  12. As for all the comments about autostruts across docked docking ports. We've noticed it and taken action. Look out for more patches coming soon. TM
×
×
  • Create New...