Jump to content

nightingale

Members
  • Posts

    4,137
  • Joined

  • Last visited

Everything posted by nightingale

  1. The load failures are due to to changes in @linuxgurugamer's Unmanned contract pack (some of the contracts got renamed) and is normal. I can't say much about the failure you hit, as I don't know the specifics of the Rover contract pack. You may want to try in the thread for the contract pack itself.
  2. The contracts are fairly spoiler free, but if you want it to require a bit more play it with SCANsat - that'll require you do a biome scan for a body for its contracts show up. It's really hard to just run into many of these Easter eggs if you don't know they're there, for most you need to get pretty close before you actually see them. I've "accidentally" seen the Mun arches, but I think that's the extent of it for me.
  3. I had to revert this change. The amount of log spam that it creates is absolutely atrocious. If you want this on, you can change the log level to VERBOSE only for the ContractType class.
  4. You were on the right track with the completeInSequence: PARAMETER { name = ReachState type = ReachState targetBody = Kerbin biome = Shores } PARAMETER { name = PlantFlag type = PlantFlag targetBody = Kerbin completeInSequence = true } Basically, the PlantFlag is not allowed to complete until the parameters above it (not parent parameters, but siblings above it in the ordering) are completed. --- Ah, that makes sense now. That's also why I make sure GameData is always the root folder in my zips - makes it harder to install wrong. Or there's CKAN, but I respect that it's not everyone's cup of tea. Anyway, glad it's sorted --- Hmmm.... going to have to add a few more guards to those in that case. Thanks!
  5. At this point I'm just assuming that the ISP thing needs to be completely broken down and retested... when I do that (hopefully in the next few days) I'm going to go through the last few pages of this thread for this specific items you've mentioned.
  6. Seems to be the same root issue - the science experiment definitions are somehow messed up.
  7. Changed it for the next version. I think I had it to VERBOSE since the contract generator can be quite spammy. Not too surprised, it was a long shot. That will work. I just need to see/test the contract.
  8. Took look at a Science - Full Reward (the new name of No More Science Grind), and it's also just MM patches like CSS. So seems unlikely to be the problem too. If removing either of those doesn't work, send me the contract file (if you can find it) and I'll take a look.
  9. The key additional lines are: [INFO] ContractConfigurator.ContractType: Loading CONTRACT_TYPE: 'FirstEVA' [R&D]: No Experiment definition found with id evaReport ContractConfigurator.CollectScienceFactory: CONTRACT_TYPE 'FirstEVA', PARAMETER 'CollectScience30001' of type 'CollectScience': The value supplied for experiment (System.Collections.Generic.List`1[ScienceExperiment]) is invalid. I want to say that contract comes from @tjsnh's Advanced Progression contracts. Unfortunately, I don't currently have them installed and the only link is to KerbalStuff (and therefore broken). I'm inclined to say that there's something funny going on here though, as evaReport should be a valid experiment. Can you try without Crowed Sourced Science? I have heard of it breaking things before, although I'm kind of doubtful that's the case here. Unless you're running some other mod that drastically messes with science?
  10. Raised #27, assuming you have Media Circus I. The reputation value is way too high, but I think I need to rethink it completely, as vessel recovery is super easy to game, as you have shown. Even worse is if I recovery 20 pieces of debris, I'll get the bonus 20 times. @smjjames is absolutely correct. I've changed the text from "mission" to "strategy" to be less confusing.
  11. Yup, I was just going to ask @eberkain for the KSP.log - that should have all the +rep events listed.
  12. Yeah, I still haven't had a chance to look at the ISP stuff, but it's clearly broken. Delta v should increase proportionally to ISP, so a 2.5% increase in ISP should just be a 2.5% increase in delta-v. I'd expect your last stage to have 1015 m/s of delta v after the change - not 5200. That's *really* badly broken. 20 rep from the science, from a contract, from something else? Which strategy/strategies do you have active? Might be normal, but not enough info to say for sure.
  13. This is poorly documented, but you should be able to rig up your own orbit generation in expressions, if you so choose. Here's a super quick orbit with random inclination between 5-30 degrees (negative or positive). Untested (naturally). DATA { type = double inc = Random(5.0, 30.0) * int(Random(0, 1) * 2 - 1) } BEHAVIOUR { type = OrbitGenerator FIXED_ORBIT { ORBIT { SMA = 1449999.99996286 ECC = 0 INC = @/inc LPE = 270.690311604893 LAN = 1.93635924563296 MNA = 1.55872660382504 EPH = 31.3999999999994 } } } Let me know if you start getting into this, as you may need either more math functions (Exp, Sin, Cos) or ability to control the random distribution (eg. normal distribution instead of the uniform distribution).
  14. Huh, I didn't think I'd like that, but seeing it all together does look nice. Problem is, it would look terrible unless everyone is doing it, and the only way to get more than 25% of the thread titles to look like this is to have it baked into the forum software somehow or other (ie. have fields where people put the mod name, KSP version, date and mod version). I suspect it's possible given the level of configurability we've seen with IPS, but no idea whether "possible" means download a plugin and spending 5 minutes setting it up, or @KasperVld spending a week of time that he likely doesn't have.
  15. Well, if you mean source like source code, then have a look here. If you just want the coordinates that it generates, then search for BiomeTracker in your save file.
  16. Ah, but my point isn't to allow sorting. My point is to have version numbering that adheres to a common general understanding, so that people intuitively "know" the implications of a new release. Straw-man argument. Just because I don't place high value on being able to sort the different version numbers of a software release has no bearings on date format. The "sortability" of ISO 8601 is a nice thing, but the main benefit is in removing the ambiguity present when using either the MM/DD/YYYY or DD/MM/YYYY formats.
  17. Personally, I see no need for the extra zeros - there's no reason that these version numbers need to sort, and it looks odd to me. More importantly, the KSP version is 1.0.5 - not 1.0.05, 1.05 or anything else. Squad gets to decide that. I don't agree with a lot of the version numbering choices that they've made (0.25 => 0.90, 1.0.1 should've been 1.1, 1.0.3 should've been 1.2, and so forth), but that doesn't mean I'm going to go and add to the confusion by trying to change it. Now, if we're talking standards, then lets talk standards. Most of the version numbers used either loosely or explicitly follow Semantic Versioning. From the linked page, emphasis mine: Again, the dashes are hardly arbitrary, they are part of the standard. See ISO 8601. The format is YYYY-MM-DD.
  18. My threads all look like this: [1.0.5] Contract Configurator [v1.9.6] [2016-02-17] ... and therefore I declare that to be best. I will never concede on the ISO 8601 date format. KSP version first because it's what everyone does, and makes it easy to see Name of the mod next because it's the most important thing Version number. With a v to make it obvious what it is (and different than the KSP version identifier) and square brackets because I think it looks best ISO 8601 date because it's unambiguous, and visually it's quicker to see than having to mentally parse 3 letter month abbreviations (which may or may not be in your particular native langugage). That being said, I fully expect every other mod developer and person with an opinion to come say why the way they do it is best. Also, since we're starting holy wars, vim is better than emacs.
  19. Congratulations to @severedsolo, who has released his latest contract pack: Clever Sats. Clever Sats is a replacement for the stock satellite contracts that has more logic than stock when deciding what satellite missions should be offered for which vessels, as well as additional contracts.
  20. Yup, you need to have reach Kerbin orbit. You also need to have a 2-star contract slot open (if you have low reputation, that could explain it). You can try cancelling a few other 2-star contracts to see if that makes it show up.
  21. I understand that people do like the functionality that emails when an update occurs, but it requires too much maintenance to host my mods in two places (and there are other benefits to doing it on GitHub). So no plans on hosting on SpaceDock, sorry! Yup, that's all related. Fixed for next release, thanks.
  22. Thanks, I'm glad you enjoyed it... it was far too much work to get that scene working, and so few people have actually seen it.
×
×
  • Create New...