Jump to content

nightingale

Members
 View Profile  See their activity

  • Posts

    4,137

  • Joined

  • Last visited

 Content Type 

Everything posted by nightingale

  1. nightingale
    Made one more change (updated file). But the check is for something that is insane and shouldn't happen - so if it fixes your Contract Configurator problem it only means you have bigger problems.
  2. nightingale
    Well, those major errors are gone, but there's a lot of weird stuff in that log. I think I found the exception in Contract Configurator, but if I guessed right then the cause is a really messed up parts list (there's a null entry that got in there somehow). You can test out the dev version here and let me know if at least the Contract Configurator issues goes away.
  3. nightingale
    I haven't been able to track this one down, can you turn Contract Configurator debug on and get me one more log file (instructions here). Also, this is scary and you may want to re-install KSP first (or validate if using steam): The file 'C:/Games/KSP_win/KSP_x64_Data/sharedassets0.assets' is corrupted! Remove it and launch unity again! [Position out of bounds!]
  4. nightingale
    Known issue, fixed in upcoming release.
  5. nightingale
    Indeed, although he already knows about it. @Thomas P. - if you're able to look at #109 for a near-future release you would have my gratitude.
  6. nightingale
    Oh right, that's working as designed... I had considered making it use "plant a flag" as the trigger to end the strategy, but mandatory flag planting (for XP and milestones) just irks me.
  7. nightingale
    All of them should be keyed to need a certain minimum amount of remaining science to offer an experiment. So if you set modifiers to zero it out, it should prevent those contracts from showing up for that particular body/situation/experiment. Also, rejecting contracts has no affect on the likelihood of future contracts showing up for Contract Configurator. I may implement a stockalike functionality for this at a later time, but for the moment it just like it was in 1.0.x for Contract Configurator based contracts.
  8. nightingale
    That's working correctly, it's just that it's using KSP Math. The numbers are actually "total (+additional)" when one would expect it to be "base (+additional)". So all three numbers are: base: 2,808 additional: 11,232 (base * 4) total: 14,040 (base + base*4) I do notice that you're missing the increase for the flag planting though, so raised #41 on that.
  9. nightingale
    Fixed, thanks!
  10. nightingale
    Missed this earlier in the week. Did you figure it out? If not, update to the latest, you might've gotten the wrong build by accident. Quick release to get CKAN happy. Download here. Kerbal Sports 1.0.4 Release with KSP 1.1.1 compatibility (for CKAN).
  11. nightingale
    Quick release to ensure no problems with CKAN. Download here. Wider Contracts App 1.3.3 Release for KSP 1.1.1 (for CKAN).
  12. nightingale
    Just a quick release to prevent any CKAN issues. Download here. Waypoint Manager 2.5.1 KSP 1.1.1 update (for CKAN).
  13. nightingale
    Thanks! I think I spoke too harshly on removing the upgrades... I think I'll be able to fix the text in the Admin building itself (not the upgrade pop up), which might be good enough to reduce the support to something more reasonable. Nope, it'll top out at 5. Stock limitations. It would be hypothetically possible to mod it, but would need to add new stuff for the extra levels, and do UI stuff to make it show up right in a number of places, so probably not something I'll ever do.
  14. nightingale
    Contract Configurator 1.11.1 for KSP 1.1.1. All the ones! No real change from 1.11.0, except I decided to compile against the dev RemoteTech since it seems everybody says the release version is too broken. Download here. Contract Configurator 1.11.1 Update to KSP 1.1.1 (release to make CKAN happy). Compile to latest *dev* RemoteTech.
  15. nightingale
    Do you have Kopernicus installed? If so, known bug.
  16. nightingale
    Release time! Download here. Contract Configurator 1.11.0 Performance fixes and improved caching of biome data. Duration values can now be used in arithmetic and comparisons in expressions. Added Duration.ToDouble() and Duration(). Added Vessel.MET(). Fixed issue with vessel re-assignment on undock (thanks chrisl). Improved contract window text when tracking vessels in a VesselParameterGroup. Improved API for requirement saving/loading. Add proper error handling to PartModuleTypeUnlocked. Added ReachSpecificOrbit.displayNotes back in (thanks severedsolo). Fixed so orbits for offered contract show up in the tracking station and NOT in flight. Minor bug fixes.
  17. nightingale
    The reason they are separate is mostly historical. Funny enough ReachSpecificOrbit actually uses Orbit under the hood since KSP 1.1. But I probably won't combine ReachState and Orbit any time soon.
  18. nightingale
    I've always been on the fence about the orbit info dump - I've tried to get rid of it before and someone complained (maybe you!). That being said, I love the look of the orbit lines in KSP 1.1 (great work, @Arsonide), so in some ways I'm now leaning towards ReachSpecificOrbit over ReachOrbit as a way to do "get to an orbit" in a contract. Still, they both have their uses, as ReachOrbit allows very loose goals (such as only checking for one orbital parameter like inc or ecc).
  19. nightingale
    Being realistic though: Anomaly Surveyor for KSP 1.1 KSP 1.1.1
  20. nightingale
    Added Vesse.MET() as a Duration. I also added Duration.ToDouble() to make the casting a bit cleaner. That gives you seconds though, so it didn't seem quite clean enough and one thing lead to another. @NathanKell once commented about my tendencies with Contract Configurator (and the expressions are the worst offenders) - "why build a hammer when you can build a toolbox?". Long story short, Duration now supports comparison and mathematical operators, so your example becomes: AllVessels().Where(v => v.MET() > 30d).Random() Yeah... I mishandled that one. KSP 1.1 broke ReachSpecificOrbit, and I either forgot or "forgot" to add the displayNotes functionality back in. Since you noticed it fairly quickly, I guess that means people use it? Anyway, wasn't too bad to add back in, so that's fixed now. Got a few more things that I want to look at, but a release should be forthcoming fairly soon.
  21. nightingale
    Sorry all, I've just been swamped with work these past couple days, so fell a bit behind on this stuff. I'll get everything logged into GitHub, but can't promise too much investigation tonight. The release priorities at the moment are: Contract Configurator 1.10.5 Strategia 1.2.2 Anomaly Surveyor for KSP 1.1 Based on the devnotes, I expect that at some point in the middle of that KSP 1.1.1 will drop, which may or may not throw a wrench into those plans (or it may just delay it). Should be good with the information that's been given so far. Raised #39. Raised #40. Can I get a screenshot on this one? I took a quick peek and everything seems to be in order on this one (the config is a 5.0x and 0.2x multiplier - so it's rather difficult to get a reversed +80% / -400% out of that).
  22. nightingale
    @rakol - Yeah, that file just tells the Contract Configurator science subsystem to ignore those experiments so they don't get offered as part of contracts (like the ones in Field Research). It has no effect on anything outside of Contract Configurator.
  23. nightingale
    It's easy*, just read the documentation! * for certain values of easy
  24. nightingale
    You could use the latest version of CC and just have errors in the log - they don't hurt anything other than not having RT contracts working.
  25. nightingale
    Would need something that is a lot more complex than what is available now. Best I could suggest would be to look a combination of parts to say that planes are unlocked to try to avoid these cases as best as possible.
×
×
  • Create New...