Jump to content

nightingale

Members
 View Profile  See their activity

  • Posts

    4,137

  • Joined

  • Last visited

 Content Type 

Everything posted by nightingale

  1. nightingale
    Indeed. Since it's not the 1.7 version that they released I expect things will probably just work. But I'll double check that soon and release a new version of Contract Configurator if anything needs to change. At that point I'll also update the contract pack to be 1.0.2 compatible.
  2. nightingale
    That's a simple enough suggestion. Raised [#206].
  3. nightingale
    Correct. All that SCANsat changes is (for some contracts) requires you to have done an orbital scan of the specific location before the contract is offered. If you add in SCANsat later, those requirements will just get enabled via ModuleManager.
  4. nightingale
    It looks for the onVesselWillDestroy event from KSP - so I don't have a good answer, it's whatever KSP decides "destroyed" is. To extend Contract Configurator, check out the wiki page on Extending Parameters. That being said, in this case it may be better for you to just make changes to TargetDestroyed if you want to make it work better for everyone. I do accept pull requests.
  5. nightingale
    Though, there seem to be far fewer entries relating to the plugin, so something was fixed perhaps. Still seems to be dealing with the SCANmechjeb though, which I should note I did not delete for the test with the new dll. Yeah, I get a lot of PMs, and I don't think I got a warning when my inbox was near full this time. Anyway, as long as it's just the one warning at the top, it should be working as expected - give it a go and see if you get the contract generated. BTW, DMagic said that you're on the dev version of SCANsat and so there's a SCANsat/MechJeb version mismatch that may be causing that error. So if you upgrade SCANsat, that error should hopefully go away entirely.
  6. nightingale
    53 to go! Still hoping I'll make it to double light green before UpsilonAerospace updates his light-green group list (thus skipping the one-bar list entirely).
  7. nightingale
    Got one of the classic "forgot to change to .net 3.5" errors for you in SCANmechjeb.dll: [COLOR=#333333][EXC 19:32:05.831] ReflectionTypeLoadException: The classes in the module cannot be loaded.[/COLOR] [COLOR=#333333]System.Reflection.Assembly.GetTypes ()[/COLOR] [COLOR=#333333]ContractConfigurator.ContractConfigurator+<GetAllT ypes>d__1e`1[ContractConfigurator.ExpressionParser.IExpressionP arserRegistrer].MoveNext ()[/COLOR] [COLOR=#333333]Rethrow as Exception: Error loading types from assembly SCANmechjeb, Version=1.1.6.0, Culture=neutral, PublicKeyToken=null[/COLOR] This was reported by one of my users in this post, so I can't confirm the version (although I assume the assembly version in the log snippet above is meaningful to you).
  8. nightingale
    Aha! Some old code that is unfortunately causing Contract Configurator to fail due to another .dll that won't load properly. I just need to convert that part over to the safe version and it should be good. You'll have a fix in Contract Configurator 1.0.3. I'll also let DMagic know - since the MechJeb integration was introduced recently, he probably forgot to change the default .Net framework setting that will fix this. In the meantime, if you remove SCANmechjeb.dll, things will start working. You will lose the SCANsat/MechJeb integration though. And there's a small chance it may break SCANsat, but DMagic tends to be very careful about that stuff, so you'll probably be alright. Or you can just wait for my update, which should come before the weekend.
  9. nightingale
    The current version contract pack should work under older versions of Contract Configurator. Note though that I offer no support for older versions of KSP, so you'll be on your own. The biggest issue will be the "ghost ship" issue that you may have read about in this thread, which won't be fixed until CC 1.0.3 (coming soon).
  10. nightingale
    New version up. Hard to explain the change without spoilers. Suffice it to say there will be minor spoilery graphical glitches on the Jool contract if you use 1.1.0 with Contract Configurator 1.0.3 when it comes out (in the next few days hopefully). So download here! ContractPack-AnomalySurveyor 1.1.1 Future proof Jool Monolith contract against changes upcoming in Contract Configurator 1.0.3.
  11. nightingale
    Make sure there's an empty seat on the vessel. Make sure there's no errors in the log file. Make sure you actually have the contract showing in your window as accepted. If you've checked the above, then send logs (and maybe a save file if the log has no errors).
  12. nightingale
    It's the duration all the child parameters must remain complete - so you'd have the same issue if you took your pilot and buggered off halfway through the mission. So for technical reasons, it has to stay where it is - but I can make the main description more clear.
  13. nightingale
    I didn't update the description (I'll do that next update) - but it should still say as part of the contract parameters. For example:
  14. nightingale
    There is no duration for the sub-orbital contracts. Hit the waypoint and the contract should complete.
  15. nightingale
    The original dev for this mod has been gone for a while, but I expect this should still work. SCANsat for KSP 1.0.2 was just released yesterday, I haven't had a chance to test against it - if you run into issues you can report them here or on the Contract Configurator thread.
  16. nightingale
    Then thanks for the coffee, and thanks to khyperia for HyperEdit.
  17. nightingale
    Ah yes, the survey contracts were introduced in 0.90 (when Fine Print became stock). Those are for surveying things that are not anomalies.
  18. nightingale
    Two ways to fail the tourism contracts that I can think of: Kill one of the tourists (doesn't sound like it here) Uninstall or otherwise mess up the contract pack Sounds like you didn't do #2 until after the contracts were failed.... but I can't think of any other reason at the moment. As to restoring things, I can't say much without more info. First, double checking you don't have any exceptions in your log related to Contract Configurator. If that's clean, send a save file and I'll take a look. It could also be that the contracts just aren't making it into the offered list, so you may want to cancel other contracts just to see if they show up. As to Tito remaining in the Astronaut Complex - there's at least one stock bug that I'm aware of that can cause that - if you recover the Kerbal from the KSC scene rather than the flight scene that happens. If you toss him on a ship and recover him through the flight scene, he should disappear.
  19. nightingale
    Oh, well then... there's still a bug in Contract Configurator, which I'll fix. Which will make the cupola optional until severedsolo fixes it.
  20. nightingale
    Ah, I never tested for an optional parameter in that situation... Bug in Contract Configurator, I'll fix that up for the next release.
  21. nightingale
    Just wanted to drop by and say that HyperEdit is a modder's best friend... It's saved many many hundreds of hours in setting up stuff to be tested. So a big thanks to you Ezriilc!
  22. nightingale
    Not sure if you're saying they're not there or are there but don't have enough science. As of KSP 1.0, most contracts give little or no science (part test contracts seem to generally be in the 1-10 science range). The only thing Contract Configurator can change is to allow the stock Part Test contracts to be disabled, but there are no mods/contract packs in the wild that I'm aware of that do that.
  23. nightingale
    Hmm.... maybe I do need the details for this one - all of the Anomaly Surveyor contracts are on the ground! Also, progression-wise, most of the contracts have fairly arbitrary requirements - so there isn't a contract that's really "after" the Island Airfield one!
  24. nightingale
    Oooh yeah, there's a few problems there: There's not meant to be a duration on that contract, it should complete as soon as you hit the waypoint. I need to bump up the distance tolerance.... I think it might be 15 km? Either way, needs a wider margin The negative timer thing I'll need to look into, but shouldn't be an issue after I fix the contract. I'll get a fix out ASAP for #1 and #2. - - - Updated - - - Alright, 1.1.1 is out - download now! ContractPack-Tourism 1.1.1 Fixes for sub-orbital contracts (thanks Enceos). Removed duration Need to be within 50km of the waypoint instead of 15km Note that your current contracts will need to be manually cancelled - the fix will only apply to new contracts.
  25. nightingale
    Sort of. Currently Contract Configurator doesn't support making the waypoint disappear, but it would make sense since that makes it consistent with stock contracts. Raised [#205] to enable that behaviour.
×
×
  • Create New...