Jump to content


KSP Team
  • Posts

  • Joined

  • Last visited

Everything posted by JPLRepo

  1. I'm not sure what this has got to do with ResearchBodies mod?
  2. Oh right. So you have Realism Overhaul installed? Look at the file \GameData\REPOSoftTech\AmpYear\MMConfigAmpYear.cfg note the second section that changes reserve power on all command pods to 1000 if and only if you have RealismOverhaul installed. I'm running without that mod and I get 80 (the first section of the file). If you don't want it remove that whole section. Or change the amounts.
  3. Yep so I see lots of these: EXC 07:57:23.599] NullReferenceException: Object reference not set to an instance of an object BackgroundResources.SolarPanel.ProcessHandler () (at <5091cf6c7dfe48e7ad95ce0493f04787>:0) BackgroundResources.UnloadedResources.ProcessInterestedModules (BackgroundResources.InterestedVessel vessel) (at <5091cf6c7dfe48e7ad95ce0493f04787>:0) BackgroundResources.UnloadedResources.FixedUpdate () (at <5091cf6c7dfe48e7ad95ce0493f04787>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) What's that? a bug in Background Processing code that I have fixed in V0.16 for KSP 1.10.x Doesn't help you running on KSP 1.9.x and TAC 0.15. But the good news it's fixed for the latest version. What can you do still on 1.9 and 0.15? Move forward into the light of KSP 1.10. (Yes I know it's not that simple). It's a joke. About all you can do if you are using solar panel parts that are affected by this bug, Turn OFF background processing in the difficulty settings and just live without it for KSP 1.9.
  4. Not sure what 1000 EC you are referring to. Sorry.Can you give more information?
  5. V0.16.0 published for KSP 1.10.x Re-compile for KSP 1.10.x. Background resources can now track any mod part that uses stock resource converters to generate EC. This can be turned on via the Difficulty Settings (off by default). Fixed potential null reference errors on solar banels in background resources if the solar panel is missing transform definitions. Removed "Vessel situation change" log spam.
  6. It should still work and continue working for all versions of KSP. But I released a new version regardless, so yes.
  7. V1.12.0 published for KSP 1.10.x. See OP. Thanks to those that took the time to test the dev build.
  8. I haven't seen any issues raised. so I will try to get a proper release out for this this weekTM... along with my other mods.
  9. Yes know about this. and had one of the other modders test a fix which worked. Will schedule in some time so we can put a fix out for parttools.
  10. It already does. So something clearly broke for you. Would need the logs from when you recovered the vessel to investigate further. You should be able to recovery your save from the automatic backup KSP makes.
  11. You could assume that. But there is no way of knowing it for sure without knowing what all the mods are that you have installed and then only reinstalling just the JSI mod and flying your craft again. As for can you disable it for that one craft. You could if it is indeed JSI. right click the pod..... err.. there's a pod there somewhere right? that is using JSI transparency? i have no idea what those parts are and if in fact they are using this mod. Let's assume there is one there.. you can right click it and tell it to turn transparent pod OFF for this part. done.
  12. Not sure what this is doing in my AmpYear Mod thread? You mention one of my other mods, and three other mods that aren't mine.
  13. Note the test build is a test build. It's not a release. and no it doesn't work in 1.9.x. NOTE: it REQUIRES requires Contract Configurator 1.30.2. and that doesn't work in KSP 1.9.x either. I have no intention of releasing a version for an old version of KSP. It's hard enough to support one (latest) release of KSP.
  14. I have a test build here for those willing to help test it. This is for KSP 1.10.1 and requires Contract Configurator 1.30.2. NOTE: This is unsupported and not a final release. Don't download this and install into your main save games and then come here telling me it broke your saves. It may or will contain bugs. Those willing to help testing it can download, start a new save, report anything you find back here.
  15. No it's not. I'm working on an update. Hopefully not too much longer. (TM)
  16. Thanks. I've incorporated into the correct branch. And I updated the github zip distribution. But I'm not going to go through all the hassle of trying to update spacedock because it would mean doing an entire new release to update that. Far as I know this doesn't impact running of of mod anyway.
  17. V1.12 published. See links and massive changelog in OP. Many many thanks to @JadeOfMaar for all the work he has put in to updating many things for this mod.
  18. It would help if you supply more information in the issue on github. Screenshots don't help much. If you could supply: Full logs. List of mods being used. Attach a copy of the save file that has the problem.
  19. I have retrospectively updated AmpYear v1.5.5 v1.5.6 v1.5.7 on Github with the corrected file. Unfortunately spacedock etc do not allow you to update already posted release files. So I cannot update those. Here is the corrected file for anyone who needs it for any previous releases of this mod. (This file is only of importance to those using this mod with RSS/RO/RP1 mods). MMConfigAmpYear.cfg
  • Create New...