Jump to content

nightingale

Members
 View Profile  See their activity

  • Posts

    4,137

  • Joined

  • Last visited

 Content Type 

Everything posted by nightingale

  1. nightingale
    Interesting! Nothing out of the ordinary in your mod list. Could you send me your save file? - - - Updated - - - Possibly.... hmm.... save file for you too and I'll look at the casino issue. One thing is to make sure you have a 3 star contract slot open - sometimes the "Explore X" ones take up the spots.
  2. nightingale
    New version out, with an important fix for the whole vessel hashing/tracking stuff. This should make everything work perfectly for those long-duration contracts when not sitting and watching the vessel. Download here! Contract Configurator 0.7.10 Fixes to vessel hashing to work with unloaded vessels. Fixes some issues with duration timers resetting. Fix SCANsat issue where number instead of name of scan gets displayed. Expressions support 'null' as a value. PlantFlag no longer uses the stock parameter and is now a VesselParameter. Closes silly exploits.
  3. nightingale
    Hmmm.... been meaning to look into TAC-LS for this. I raised [#151] for this a while back, but haven't looked into it yet. I'll do that for the next release.
  4. nightingale
    Update: I've got a partial working fix for this (part of the problem is a bug in Contract Configurator). However, to get the full fix, there's some changes required to the contract pack. I can make the changes and throw a pull request DBT85's way, but no idea if he'll be able to make a release - he's been AWOL for some time. - - - Updated - - - Alright, sent a pull request to DBT85. Let's see where it goes.
  5. nightingale
    Very odd, since it produced warnings (I thought they were different than what you see, but can't remember now), but it still put all 5 in the pod. Perhaps an issue with TAC-LS or EL, since those are also spitting out stuff? Not really sure. But yeah, ideal fix would be changing the model on the BizCoPo side.
  6. nightingale
    This is one of those ones that I was never able to reproduce... so hopefully it really is fixed. Note I have gotten a report today of the duration resetting when switching vessels, so I'll be looking into that.
  7. nightingale
    It's not supposed to reset on that case. Could you send me your save file and I will take a look.
  8. nightingale
    Thanks to Invader Myk! A bunch of little tweaks on the Kerbin contract to make it far more reliable. Download here. ContractPack-RemoteTech 1.1.2 Bunch of fixes to Kerbin contract (thanks Invader Myk). Note that if you are in the middle of trying to complete the contract from 1.1.1 you'll have to cancel the contract and re-accept that. Of course, if you're in the middle of trying to complete it, the contract likely won't be offered again. To force it to get offered again, go to the Contract Configurator debug window (alt-f10), expand the RemoteTech group, expand the Kerbin contract. Near there bottom are two lines marked REQUIREMENT. Hit the button beside them to turn them red. You should now see the contract get offered (you may have to cancel other stuff in mission control to get it to show up).
  9. nightingale
    Fixes the RemoteTech contract pack. Download it here! Contract Configurator 0.7.9 Add support for Part (AvailablePart) in expressions. Fix to passengers not being seated when the capsule crew capacity is bigger than the number of seats in the IVA (thanks SpaceNomand). More fixes to vessel tracking (fixes issues with RemoteTech contract pack). Thanks to Invader Myk. Minor bug fixes.
  10. nightingale
    Well, you should see a couple more tonight, there's a bit of a mess to unravel with the contract vessel tracking stuff.... the new enhancements to better support docking/undocking broke the stuff that was being used for the RemoteTech vessel tracking. Anyway, I try to keep everything working nicely, glad that it's appreciated.
  11. nightingale
    Ah, I see the problem, Ratatosk II is acting as both CommSat I & III. That's a problem on my end. I'll test it and get a fix out. The places that say CommSat III should've also automatically changed to Ratatosk II, but I suspect that's just cosmetic. Still, I'll fix that as well.
  12. nightingale
    Nah, not really necessary.
  13. nightingale
    Hmmm.... not sure what the problem might be. Could you provide a screenshot showing both the linkup of the sats as well as the contract app for one of the sats that is meant to be commsat II, III, or IV? Oh and on that last one... I get how that might be nice in some cases.... but it does indeed sound like a pain.
  14. nightingale
    Two ways of meeting the "Direct connection to: <other commsat>": Have each commsat pointing a dish at each other (and make sure the dish is powered). Be within omni range (the range being the smaller of the range of the biggest omni on each commsat). For a four CommSat network, this can be achieved with the Communotron 16. For a three sat network you'll need Communotron 32s or dishes. With the latest revisions allowing the four CommSat networks, you should be able to meet the contract if you follow the RemoteTech tutorial.
  15. nightingale
    Issue fixed! It'll still generate warnings (stock KSP, can't change that), but they will be loaded into the vessel. It'll be in the next release. Since I can't rep the QA team (SpaceNomad) due to having rep'd him recently, everybody who stops by should give him a little thanks with some rep.
  16. nightingale
    I'm sure the MK3 cabin works - tested that one. So maybe it's when the number of seats doesn't match the stated capacity?
  17. nightingale
    Interesting, not something I ever saw on any of the stock parts! Raised [#177], although very possible the problem is with the BizoCoPo pod. Still, let me look into it, and I'll post over in their thread if it's their issue.
  18. nightingale
    Thanks tjsnh for verifying. New version - download now! Contract Configurator 0.7.8 More fixes for docking/undocking and vessel tracking (thanks metl). Fixed problem where requirement status was no longer showing up in debug menu. Minor bug fixes.
  19. nightingale
    The issue was reported on the contract Configurator thread this morning, I'll get a fix out tonight. EDIT: It's addressed by 0.7.8, out now!
  20. nightingale
    @tjsnh - I think this may be the same issue that I fixed for metl last night. Can you grab the dev version from here and let me know if it fixes it? If it does I'll release soon (likely tonight). If not I'll do some more digging!
  21. nightingale
    I meant the CONTRACT_TYPE and everything in it in the .cfg file.... but I realize now that I meant that for metl and not you. Anyway, taking a look at the log, that's all I needed for your issue. - - - Updated - - - Well, nothing particularly damning in the log, except I see that you had and then uninstalled the RemoteTech pack - which I think is sort of the root of your problem. Since Contract Configurator 0.7.3 that will no longer cause a fatal problem, but that update is 11 days old, and you originals said you'd been having the problem for "a week or two". You also said "Even without CC now I get "launch a new vessel" contract whenever I load a current career". So if you remove CC, I'm not sure how KSP will handle the "unknown" contract, but I strongly suspect it would also cause the contract system to load improperly. So I think if you keep CC installed and keep playing as normal, you should be okay from here on out. But correct me if I'm wrong and you still keep seeing the issue....
  22. nightingale
    And I start my parental leave in 15 minutes... The timing works out, looks like I will be able to update my mods when 1.0 drops.
  23. nightingale
    Try this out (let me know if it doesn't work as a replacement for EnterSOI): [COLOR=#333333]PARAMETER [/COLOR]{ name = ReachState type = ReachState targetBody = Minmus }
  24. nightingale
    With ROCKS. To actually answer OP, I much prefer winging it.
  25. nightingale
    Sounds very cool, and very Kerbal. My suggestion would be that EVA kerbal's don't walk home, but instead get switched to unowned and a rescue contract is spawned. In fact if you're interested in going this route I could whip up something using Contract Configurator in less than 10 minutes. Of course, then it's a bit asymmetric with respect to how it works for a ship/station/base running out of supplies - so one would make the argument that you would want those to generate some form of resupply contract (which wouldn't be terribly difficult either).
×
×
  • Create New...