Jump to content

JPLRepo

KSP Team
  • Posts

    3,141
  • Joined

  • Last visited

Everything posted by JPLRepo

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. We know about the MK1-3 command pods flag and the issue with the linux scrollwheel.
  7. 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.
  8. 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.
  9. This bug was fixed by the 1.12.1 patch. Download it and you should be fine.
  10. 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
  11. This looks like the issue that was just patched by 1.12.1. looking at your screenshot there. I'd suggest you download 1.12.1 and see if that fixes your issue.
  12. That is correct. You can turn on the tidy up debris cluttering KSC option again now and your game will be ok.
  13. This is a stock KSP game thing. Not related to this mod. Probably not. But I haven't even started looking at updating TAC LS for 1.12 yet. Thanks for your patience.
  14. AOORE = Argument Out Of Range. This occurs in programming speak when you try to access an index in a list that is outside the number of items in the list. eg: list contains 10 items and I try to access item 11.
  15. New PartTools has been updated above in the opening post for the new Unity version. 2019.4.18f1 LTS. Fixed the TMPro integration issues provided you follow the instructons in the opening post. Fixed the KSPAssets.DLL issues. Fixed the offset issues in IVA models when system OS language is not set to English (culture invariance). Fixed shader issues. The PartTools component now has an option to optionally write out the textures - so you can just write out the mu file only or both the mu file and the texture files. The PartTools component now allows you to export multiple objects (parts) at once by multi-selecting them in the hierarchy you will be presented with a multi-object export custom inspector drawer. Links to the older versions of PartTools are also included above if you still want to use those.
  16. The file version info version number stored in the file. Using https://docs.microsoft.com/en-us/dotnet/api/system.diagnostics.fileversioninfo.getversioninfo?view=netframework-4.6
  17. The modders notes and the new slim suit ID/UV maps are available here for modders.
  18. You can't currently. But, wait for the patch.
×
×
  • Create New...