Jump to content

nightingale

Members
 View Profile  See their activity

  • Posts

    4,137

  • Joined

  • Last visited

 Content Type 

Everything posted by nightingale

  1. nightingale
    @Crocn - I didn't see anything in the log that would cause your issue. I suspect it's due to disabling all the stock contract types though - I've seen times where doing that causes the stock contract system to just give up and stop generating contracts at all. Try re-enabling one or two of those.
  2. nightingale
    @rasta013 - Yeah, I may have overdone it on the debug statements. I can say with near certainty that the amount of debug I added is what caused the slowdown. Looks like with the USI updates all should be well now though.
  3. nightingale
    Says it needs a decryption key.
  4. nightingale
    @rasta013, @AccidentalDisassembly, @MajorTom - I took another look, and although I still think you've got some other mod that needs updating to 1.1.2, I've done the following: Fixed one more spot that could be the one throwing the exception Added a ton of debug So if one of you doesn't mind grabbing the dev dll, and telling me: If it fixes this particular exception If not, please provide the log file
  5. nightingale
    One of the dev versions - I don't remember which one. Unless something broke again, the expectation is that the latest will work.
  6. nightingale
    The strategy that you can't access.
  7. nightingale
    Screenshots and a save file please.
  8. nightingale
    Those two things are unrelated. You must recover a Kerbal after they've visited the Mun/Minmus. This just looks at the stock progression stuff.
  9. nightingale
    If you have Kopernicus installed, then it appears normally. Also, the terrain detail settings affect it.
  10. nightingale
    Post KSP.log please.
  11. nightingale
    This looks like the exact same problem that @AccidentalDisassembly was having, and I see a whole ton of errors in your log as well. Could you update/remove the mods that aren't confirmed as working in 1.1.2? The ones that I see suspicious errors for are: MKS Orion Pulse Drive Wild Blue Industries AntennaRange I'll continue to see if I can fix something in Contract Configurator, but I believe that one of those mods is actually the root cause. --- And on another note - congrats to @Syntax for releasing his new contract pack, Interplanetary Mountaineer! Explore the high and low points throughout the solar system!
  12. nightingale
    Neat idea for a contract pack, I'll add it to the list in the Contract Configurator thread.
  13. nightingale
    @lude - Raised #42. @Enceos - I'd say that would fit, but the way I made it, the change would need to be done in GAP. @inigma, if this is something you're interested in, have a look at the example here.
  14. nightingale
    Can you post a KSP.log
  15. nightingale
    Checked, and all Contract Configurator does here is tally up the part.CrewCapacity values. For a stock command seat that will be zero (and as far as I can tell always has been). If TakeCommand isn't setting that value when it adds itself then I'd take the issue over there.
  16. nightingale
    Breaks how?
  17. nightingale
    To be honest I think it's just looking at a field/method provided by stock, do can't really say for sure without doing some digging (which I'll do when I can tonight or tomorrow).
  18. nightingale
    Was it not always like this, with the exception of when TakeCommand is installed?
  19. nightingale
    That would be inadvisable. KSP 1.2.0 is probably guaranteed to break Contract Configurator. You may have mean 1.1.99 (or something along those lines). But that's also inadvisable. Looking back we have: KSP releases that broke Contract Configurator: 0.25 0.90 1.0 1.0.1 1.0.2 1.0.3 (yup, the one that came 2 days after 1.0.2) 1.0.4 1.0.5 1.1 KSP releases that didn't break Contract Configurator: 1.1.1 1.0.5 ultra secret patch Contract Configurator is a huge mod in terms of the KSP footprint... so it's really rare to get a KSP release that doesn't break Contract Configurator in even a small way. So I'd rather be the one to certify when it's ready on a new KSP version.
  20. nightingale
    @Tossy64 & @severedsolo that's an upgrade problem from something that got removed. I'll write up something that just auto-cancels the contract (best I can offer in this instance). @AccidentalDisassembly - I don't think GAP is actually the problem though (that's just what's exposing it in Contract Configurator. I'm hoping once you clear up those other issues that it should be resolved. @crapstar - That is now fixed for the next release. @Warezcrawler - That error is 100% stock. If I had to guess it happened because a part changed in some way (got renamed or removed). Could be stock or from a mod. --- I'm pretty much out of time until sometime tomorrow, so releasing this to fix the couple breaking issues that have been identified. Download here. Contract Configurator 1.11.3 Revert additional check added in 1.11.0 that broke PartModuleTypeUnlocked (thanks KnotaiG). Work around upgrade issue with ReachSpecificOrbit (thansk Tossy64).
  21. nightingale
    Fixed for next contract Configurator release.
  22. nightingale
    @QiJian - You have RSS and a bunch of contract packs that don't support RSS. The historic missions one has two variants (one for RSS), and there are many SCANsat contract packs (the one that comes with SCANsat does work with RSS). @KnotaiG - Reproduced, think it's something to do with 1.1.2, but not sure. Raised #504.
  23. nightingale
    And release for KSP 1.1.2 is out. Download here. Contract Configurator 1.11.2 Recompile against KSP 1.1.2. Possible fix to PartModuleUnlockedRequirement (thanks AccidentalDisassembly). Fixed exception when generating autoAccept contracts.
  24. nightingale
    Contract Configurator 1.11.1 does not work on KSP 1.1.2. I'll get a new release out as soon as possible, and sort out the above bug reports (although anything that's on KSP 1.1.2 I'm ignoring, because it's clearly broken). @AccidentalDisassembly - I threw in a few more checks, try the 1.11.2 release (below) on KSP 1.1.2. @wqt0806 - MCE and Contract Configurator have nothing to do with each other. @QiJian - I need more info. There used to be a conflict with Kopernicus and Scatterer that would cause that error. Or you have RSS and a contract pack that doesn't support it. Won't be able to say much more without logs.
  25. nightingale
    The only one that I would not suggest doing is the Jool Monolith contract. Everything else should work fine.
×
×
  • Create New...