Jump to content

nightingale

Members
 View Profile  See their activity

  • Posts

    4,137

  • Joined

  • Last visited

 Content Type 

Everything posted by nightingale

  1. nightingale
    New release, download now! Contract Configurator 1.5.4 Added new extended PartModule mode to PartValidation parameter. Added new methods for determining engine thrust and ISP in expressions. Added additional validation to WaypointGenerator.RANDOM_WAYPOINT_NEAR (thanks Xaegr). Minor changes to VesselSpawner. Fixed issue with VesselNotDestroyed firing for EVA Kerbals boarding a vessel (thanks Cooper42). Fixed Pow() and Log() expression functions to work correctly with types other than double (thanks NathanKell). Fixed major issues with CanResearchTech requirement (thanks NathanKell). Fixed holes where expressions could modify underlying KSP lists (thanks Whyren). Experiments from unsupported science mods won't show up - preventing them from showing up before the right tech has been unlocked. Added Asteroid Day experiment to experiment list (doesn't change behaviour, just quiets a warning).
  2. nightingale
    I took a peek at the SETI config and everything seems to be in order to me. What could be happening based on the bug in the linked thread is you're just changing the order of the agent loads to allow the stock ones to get loaded before the agent system explodes. Check for errors in your log similar to the ones in that thread. Oh and Yemo - congrats on the $100 million.
  3. nightingale
    I could've sworn that the science archives info was going to be available outside of R&D, but I couldn't find anything in the devnotes about it (I swear it had been in one of Romfarer's notes). Oh well, probably just wishful thinking on my part.
  4. nightingale
    Alright, that means, new version time - download now! Waypoint Manager 2.4.1 Correctly display name for "clustered" waypoints (Alpha, Beta, Gamma). Fix for duplicated waypoints (thanks Dr. Jet). Added Apply button to custom waypoint dialog (thanks 5thHorseman). And hello to all those upgrading from 2.3.2 because they didn't get a notification for 2.4.0 (I messed up the update to the version file, only just noticed when doing this release).
  5. nightingale
    Actually an Expression based parameter *could* be possible... but only if you have a specific use case that can't be better met in another way.
  6. nightingale
    I can't say I understand why this one is causing an exception, but at the very least I've fixed the Kerbal EVA boarding counting as a destroyed vessel - so that should prevent it this issue. The fix will be in Contract Configurator 1.5.4.
  7. nightingale
    Ah, I see. The biggest issue with that is the expressions get run at contract generation time, so the only way to set/create a waypoint with the rover coordinates at an arbitrary time is with a custom behaviour (ie. C# code). Otherwise the other option is to split it into two contracts, and have the second contract with a super-high weight and autoAccept turned on.
  8. nightingale
    Indeed... I think you just had bad RNG luck (or you were cancelling contracts of the wrong prestige level). Either way, glad it's working now!
  9. nightingale
    Yeah, I think I'll be rolling back most of my changes. You can hack something together with an ORBITING vessel < 70000 km, but anything where the semi-major axis ends up too low it just insta-dies when the vessel is spawned. I think the hack you figured out with the decoupler is actually the best bet.
  10. nightingale
    Nothing particularly unusual in that log. Do you have antennas and solar panels unlocked?
  11. nightingale
    Already supported. In the WaypointGenerator behaviour provide the parameter attribute (with the name of the parameter that is a prerequisite for displaying the waypoint). And it's always generated up front - just invisible until the parameter in question completes.
  12. nightingale
    Nothing special, it means my flying fix needs some more work. I'll get back to you on this one.
  13. nightingale
    I can see how CapCom would cause trouble... I'm guessing I'm picking up the waypoints before they are added to the contract, and I'm caching it for performance... at least that's my guess. Try this dev dll again and let me know if it resolves the issue. Cool! May regex needs a "restore to original" button or something though, that sounds like a lot of work to get it back. Anyway, you've got an apply button coming in 2.4.1.
  14. nightingale
    It's a known issue - I guess linuxgurugamer hasn't been around in a while to fix it.
  15. nightingale
    Really having trouble tracking this one down... I've got a dev dll here for you to try with a possible fix.
  16. nightingale
    Contract Configurator supports a few things related to this: Unlocking a tech node on contract completion Unlocking (purchasing) a part if part unlocking is enabled on contract completion Marking a part as experimental on start or completion (offers it temporarily) Unmarking a part as experimental on start or completion So pretty much all implemented already.
  17. nightingale
    Bing, bing, you've found the culprit. For some strange reason, MOLE appears to include the experiment definition file from the ZZZ-RadioTelescope, but no parts that use it. So my mod assumes that it's a partless thing. Report the issue on the MOLE thread, and you can probably remove GameData/WildBlueIndustries/MOLE/ExperimentData.cfg as a workaround.
  18. nightingale
    According to your logs, you don't have the RemoteTech contract pack (or any contract pack) installed!
  19. nightingale
    You can also install SCANsat, and then it will only offer contracts for bodies where you've done a biome scan. In general, I've tried to keep the contract text as spoiler free as possible.
  20. nightingale
    That type of behavior is almost always an exception, so I'd need to see a KSP.log file
  21. nightingale
    Hmmm... something was referencing it then... crowd sourced science perhaps? I've seen a bug with another mod where CSS would add a reference to the experiment.
  22. nightingale
    Hmmm.... it definitely is due to the fact that Kerbin has no moons. It's a bug in the contract pack, so it'll get handled under ContractPack-Tourism#12. In the meantime you can use the following module manager config to delete it: @[COLOR=#333333][FONT=Consolas]CONTRACT_TYPE[[/FONT][/COLOR][COLOR=#333333][FONT=Consolas]Tourism_Moons] [/FONT][/COLOR]{ @[COLOR=#A71D5D][FONT=Consolas]maxSimultaneous = 0[/FONT][/COLOR] }
  23. nightingale
    Oh one last question - are the waypoints in question coming from Contract Configurator, or stock contracts? Also, are you able to provide a log file? The reason I ask is that Waypoint Manager *shouldn't* really have anything to do with the waypoints being removed... but if it's throwing an error it could prevent them from being removed.
  24. nightingale
    Sounds like it's coming from ZZZ-RadioTelescope. Perhaps you installed it and forgot? Or installed it and uninstalled it only partially?
  25. nightingale
    Ohhhh, like the old Alternis. I didn't realize there was one out there like that. It's been in the back of my mind while doing those contract packs, but I'll have to verify. I doubt it's balanced for that scenario, but it... probably should work. I meant a log from a save where you could reproduce the original issue. 404 - no file. Yeah, most important is a log with all the errors that you had above... context and order will be very important here.
×
×
  • Create New...