Jump to content

nightingale

Members
 View Profile  See their activity

  • Posts

    4,137

  • Joined

  • Last visited

 Content Type 

Everything posted by nightingale

  1. nightingale
    Not for that type of parameter. Use the OrbitGenerator behaviour and ReachSpecificOrbit parameter instead.
  2. nightingale
    Next build tonight to get the 32/64 bit stuff cleared away. And yeah, not debugging 1.3.4 Yeah, dropbox is being stupid. It just cycles endlessly on my PC, but I can see it find on my phone. I'll see if I can do anything with this one...
  3. nightingale
    No screenshot in the folder. Can I get a log?
  4. nightingale
    Can you post a full log file for this issue?
  5. nightingale
    Can I get a screenshot too so I can correlate?
  6. nightingale
    Awesome, thanks! Since it's a pure parts mod using the stock science stuff, it'll work just fine. The only ones that cause trouble are the ones that use their own custom part module (which makes it hard for me to know when it's the part has been unlocked) or ones that have coded experiment availability restrictions.
  7. nightingale
    Alright, based on the feedback so far I think I'll reenable the 64-bit support with warnings. Look for that in the next relesae.
  8. nightingale
    DMagic Orbital Science is supported. MkerbIncScienceParts I have never even heard of, and a search only results in your post (typo? needs actual spaces?). If you provide a link to the mod, I can look into support for you.
  9. nightingale
    Are you using 64-bit windows KSP? Are you using Contract Configurator without issues? Which contract pack(s)? Are you sure there's no issues (no odd exceptions in the log)? If I am able to get confirmation from you and others that it is working completely correctly for at least some people, then I will consider releasing the next patch with re-enabled Win64 support with the addition of a nag screen, and in-line warning messages for every exception (because to be honest, that's usually all I get in bug reports - count how many logs were posted without having been specifically asked for, versus the number of exceptions-as-posts). - - - Updated - - - Missed this part. A null vessel is programmer-speak for a empty vessel record (in the global list of vessels, in this case). It shouldn't happen unless something went really wrong, so really nothing you can do to fix. Let me know what it looks like on the 32-bit install... that'll help me come to my final decision on Win64 support. - - - Updated - - - Not really, because then I miss out on what might've been legit bug reports.
  10. nightingale
    Alright, new version with wider support for science mods for Field Research. Also I'm testing the waters to see what the reaction is if I disable Win64 support, because I've spent all week debugging impossible to reproduce issues and have enough reason to believe there's a link. Anyway, download link here. Contract Configurator 1.4.0 Move extra science experiment definition to configuration files. Add support in science modules for Station Science. Add support in science modules for Solar Science. Add support in science modules for N3h3miah's science mods. Add additional experiment validation. Fix possible NRE in vessel expressions (thanks Mulbin). De-support buggy Win64 hacked version until Unity5.
  11. nightingale
    Wait, what's the title of that contract? None should be that bad - the experiment one could potentially be (and I'll clean it up a bit under [#4]), but the one you're showing just seems random.
  12. nightingale
    Same issue that I fixed. I'll release it very soon. Yeah, I think I'm actually going to go so far as to disable Win64 support, because if that is the reason it is pretty rediculous the amount of wasted time it has caused me. Hmmm, nothing unusual, and I still haven't been able to reproduce. Let me know if there's any change with no/fewer mods...
  13. nightingale
    That is an entirely different (and easy to fix) error. Still concerned as it implies issues/exceptions elsewhere in KSP (as it means there's a null vessel in KSP's list of vessels).
  14. nightingale
    Everything looks fine. Can you tell what contract it's coming from (the agency should give you a hint). Maybe provide the save file and I'll look at that.
  15. nightingale
    Shouldn't be related to that. This one has been frustrating as it's not something I've been able to reproduce... we'll see if Mulbin comes back with anything or not.
  16. nightingale
    Can you provide a full log file? The only reason I can see that happening in the code is if there are some major problems in the stock experiments being missing.
  17. nightingale
    Ah, then perhaps the problem was really USS all along (I was trying to reproduce with KSS). Let me know if you find anything useful..
  18. nightingale
    No need, fixed in 1.3.4. The root cause is having both KSS and USS installed. At some point I'm going to add a feature that will allow a pop up error if both KSS and USS are installed to prevent this...
  19. nightingale
    Congrats on your selection for Modding Monday!
  20. nightingale
    I'm actually starting to work on the science system right now to add in configuration to make setting this type of stuff up easier. Raised [#3] to track the specifics for mods. It's completely KSP's fault - it doesn't give a stock mechanism to limit science experiments in the way that mods mod authors want - so they have to do things their own way, which is a nightmare for compatibility. So you'll have to report the issue to [x] Science and Science Alert individually - those mod authors will need to add special code for handling Solar Science (as will I).
  21. nightingale
    New version, fixes all those exceptions! Download now! Contract Configurator 1.3.4 Added support in parameters for completedMessage. Fixed NRE in ContractVesselTracker (thanks Morashtak). Fixed loading of duplicate Contract Types (thanks jakkarth). Fixed issue where random orbits aren't so random (thanks KerbMav). Fixed exception loading SpawnKerbal (thanks mega_newblar).
  22. nightingale
    I'll have to look into this one - it shouldn't happen (but obviously did!)
  23. nightingale
    Nothing obvious in the log. Do you have the same issue on a new save? Sounds like something or other is corrupted. If it's still occurring in a new save, get a log that covers going to the tracking station where you see the issue. It means that I need to do more performance fixes for this soon. Tracking under [#240]. Looks like something different, since they don't have Field Research installed. I didn't see any logs - just a massive 300 meg download of their entire GameData directory. Unfortunately, I don't have a lot of free time right now, so If you can get me a log (KSP.log as it has timing info), I'd rather start there. Thanks, fixed for next release.
  24. nightingale
    Known issue - fix is coming in the next patch. There is no "randomizer" - you have to tell it what the target body is. You can try one of the following for what you are looking for: targetBody = AllBodies().Where(b => b.HasSurface()) targetBody = OrbitedBodies().Where(b => b.HasSurface()) Using the OrbitedBodies() above is better than a requirement saying the body has been orbited, as using the requirement will reduce the changes of a contract showing up, as you have correctly guessed.
  25. nightingale
    Thanks, fixed for next release. As always, pre-release available here for testing.
×
×
  • Create New...