Jump to content

nightingale

Members
 View Profile  See their activity

  • Posts

    4,137

  • Joined

  • Last visited

 Content Type 

Everything posted by nightingale

  1. nightingale
    The DMOS config currently lives here. Most of the experiments just have an empty entry (to quiet warnings), although some have special flags to identify whether they are valid or not in certain custom situations (like requiring an atmosphere). Until I get some documentation done, you can at least see the valid fields in the code here. The config serves a few purposes: To tie experiments to parts (to determine if the appropriate tech for performing an experiment has been unlocked). To tie experiments to building unlocks (again to see if it's unlocked) To support mods that make special situation/biome/body exclusions/inclusions in their own code so that Contract Configurator contracts don't show invalid ones (in your case that'd be stuff like a Bio Drill experiment on the Mun). To completely exclude experiments that are just too specialized For stuff like the SIGINT scan I'd be inclined to just set ignored=true to prevent it from showing up (as supporting the special biomes would be more work, and you have your own contracts anyway). Oh, and as far as the config files go, there's no special location or file names needed - just the config node names need to be correct.
  2. nightingale
    The way the stock weighting system works is based on the class of the contract, and there's only one contract class in Contract Configurator (which is how it can allow a contract author to not have to write any code). So it's turned off for Contract Configurator contracts. Right now it still fits in with the stock generating mechanics, but in a very awkward way.
  3. nightingale
    If it's really not liking something and not showing up you can also check KSP.log - it might be that it was unable to load the group at all.
  4. nightingale
    There's a contract pre-loader in Contract Configurator for performance reasons (so it can generate contracts over multiple frames, rather than having to execute all the expensive expressions immediately when the contract system asks us to generate a contract). The cache is persistent, so it could be generated before you made the change, and then just sat in there for a bit. I'm going to be doing some work in that area soon to improve the expiry mechanism.
  5. nightingale
    Really nothing jump out (a few errors here and there from mods not updated for 1.1.2, but nothing that should affect contracts). In the contract debug menu, you should be able to force-create contracts of the different types using the "E", "M", "H" buttons beside the contract type names. Also, can I see a screenshot of your mission control? You've got the basics down, make sure you read through the wiki if you haven't already. The version file is good to have for KSP-AVC, but won't affect anything in game. First thing to do is check the alt-f10 debug menu to see if there were any errors loading your contract config. If not, then it could be that a REQUIREMENT node is unmet and preventing your contract from showing up. If that's not it, then it could just be that it hasn't been generated yet - test it out by clearing all contracts from the debug menu and see if doing that a couple times makes your contract show up. Finally, if you have your contract set to exceptional (3-stars), make sure you have enough reputation to have a free slot open for the contract (just spam the add reputation button in the debug menu).
  6. nightingale
    Sorry, forgot to respond on this one. Most likely it was a cached contract that came up. If you cancel a bunch of contracts does it keep coming up still? @DMagic - I don't know anything about this SIGINT scan. I'm assuming it does something special with biomes, since "Northern Hemisphere" isn't a real KSP biome. That about right? If so, I'll just disable those experiments from showing up for Field Research. Or if you like I can send you the config I have for Contract Configurator / DMOS and you can put it in your mod (although that would mean that I need to properly document the structure in the wiki). Thoughts?
  7. nightingale
    I set the min KSP version to 1.1.2 since I never tested on anything less than that. It'll probably work on 1.1.0.
  8. nightingale
    I'll see if I can catch Thomas on IRC. If not, I've got a new idea for how I might work around it partially (previous attempts would've been a big change to work around the issue).
  9. nightingale
    Nope, see my original response - it's in the Kopernicus court.
  10. nightingale
    And last one of my mods to be ready for 1.1.x, yay! Download here. ContractPack-AnomalySurveyor 1.4.3 Recompile for KSP 1.1.x
  11. nightingale
    This seems a bit off, with only those contract packs I'd still expect you to see plenty of stock contracts. Can you provide a log? Oh, and BTW - the Tito Kerman one is Contract Configurator too. Already fixed for next release, let me get that out ASAP. Done. New version here. Contract Configurator 1.11.4 Clean up some "Input is null" errors/warnings. Deprecated VesselParameterDelegator. Remove support for ancient versions of Module Manager.
  12. nightingale
    For the most part they are unlocked as you orbit different celestial bodies. The exception is the monolith contracts, which go Kerbin => Mun => Jool (but Jool is broken in 1.1.2, will be fixing that this week). There's contracts for Kerbin, Mun and a bunch of Joolian moons.
  13. nightingale
    You've got a fairly old version of Contract Configurator, which is what's causing the problem. I forgot to mention that the minimum version of Contract Configurator is now 1.11.0 (I'll have to go and put some proper version/compatibility checking in).
  14. nightingale
    Nothing beyond my original response: Since TakeCommand adds a command module to the chairs, I would assume that's enough to increment that value.
  15. nightingale
    Release day, with the most important fix ever included (I'll let you guess which one that is). Download here! Strategia 1.2.2 Output the adjusted number of max strategies allowed in the admin building so that people stop posting about it in the thread (thanks literally everyone). Fixed exceptions when researching a tech (thanks smjjames). Change currency popups symbols to work around font issue. Fixed exception loading Massive Scale Launches (thanks KocLobster). Workaround for KSP 1.1 bug where vertical scrollbars don't work in Admin UI. Fixed some issues with cancelling contract-based strategies. Allow a Kerbal returning being landed on a moon to trigger the planetary strategies to handle cases where the ship doesn't make it home (thanks dlrk). Fixed Pilot Focus III ISP adjustments with multi-mode engines (thanks lude).
  16. nightingale
    @Honeybadga - you need to change GameData/ContractConfigurator/science/DMagicOrbitalScience.cfg. The module manager config would look something like this: @CC_EXPERIMENT_DEFINITIONS[DMagicOrbitalScience] { @EXPERIMENT[dmbathymetryscan] { ignored = true } } And it's always the ice caps because the RNG is programmed to be evil.
  17. nightingale
    @Fallarnon - Usually that means some sort of exception happened and KSP has gotten into a bad state. Post up a log and I'll be able to tell where the issue is happening.
  18. nightingale
    @dlrk - Ah, makes sense. I've added a check for that for the next release.
  19. nightingale
    @Galile0 - Fixed for next release.
  20. nightingale
    @cyberpunkdreams could be RNG hating on you, or could be RT problems. If you post a log I can double check, but at this point I'm somewhat doubtful I'll find anything too conclusive. Actually before you do that, try clearing all contracts through the debug menu first, and see if that makes them show (it may clear out active contracts too, so do it with care).
  21. nightingale
    @AccidentalDisassembly & @rasta013 - yeah, that's no surprise, since GAP and other contract packs use the bits of Contract Configurator that were causing the error to show up (but the actual cause was whatever part mod was messing things up on load). Anyway, glad it's all sorted.
  22. nightingale
    Neat! Glad that Contract Configurator's expressions helped you in this way!
  23. nightingale
    Known issue. Will be fixed in next release.
  24. nightingale
    That's a GAP contract! Still, if I remember correctly, it should work without a command pod (although TakeCommand may help there). To pick up the passengers you have to cycle to them using the '[' and ']' keys, and manually board them on the bus.
  25. nightingale
    If you still get it, try another long that includes when you have venera-13 and complete it.
×
×
  • Create New...