Jump to content

CaptSmollett

Members
  • Posts

    10
  • Joined

  • Last visited

Posts posted by CaptSmollett

  1. 8 hours ago, Caerfinon said:

    It may be that your issue is related to the Contract Configurator BiomeDataDefault.cfg file.

    Thanks, this did the trick! I was focused on a particular issue and didn't think to check the more generic new biome instructions for Contract Configurator.

    I had to return the contract and then restart the game before Field Contracts would restart the contract. It led me to some other spot on Kerbin which did fulfill the contract.

    I also checked the new BiomeData.cfg (which I did not have previously) and it properly references the Cold Ocean biome so hopefully that should solve future issues as well.

  2. I have an issue that I've searched the thread for and I'm puzzled how it's been missed so I've probably done something wrong. I have a conflict between this mod and the Field Contracts mod. I don't think this is a log issue but I can provide one if provided.

    Specifically, the Cold Ocean biome which I believe this mod applies (I traced it in the config patch) overwrites some of the biome waypoints in Field Contracts. Basically you land in the cold ocean at the contract waypoint and the contract doesn't recognize the "water" biome.

    I did some searching but couldn't find anything in either threads but I might have missed something. I can supply the waypoints and I think the same issue may have a knock on effect for Waypoint Manager and ScanSAT if the Cold Ocean biome is new.

    Is there an easy way to revert this to the "water" biome?

    Thanks the mod and hopefully I've done something stupid and this is easy to fix.

     

  3. I have the same issue but I don't have the mods you've listed. My particular issue started when I updated KSP Recall and Contract Pack Research Advancement Division. I have space stations which are  >20 parts and a sat that is ~20 parts that seems to exhibit this behavior.

    I'm going to roll back those mods but given you are having the same issue, it might be something that isn't fixed with a rollback?  If you have Recall or the other one let me know so we can write a problem ticket.

     

  4. I have the engine issue too, the log is far too large for a free pastebin so I found the error reports and put it here:

    https://pastebin.com/HTUNMNxB

    To confirm what was noted earlier, it looks like ModuleManager picks up these 8 errors and 1 warning (probably because I'm naughty and use old mods). I removed the physics.cfg to see if it clears the problem, but did not work. I will reload mechjeb when I have time to see if that works.

    With a very amateur eye, it appears something in the ModuleManager physics is no longer linking up. The Intake resources aren't getting found in the general physics file.

    Hope this helps.

    S

     

  5. Wolderado,

    I was digging around trying to do the same thing without much luck. It appears there is code for a couple of different versions but I'm a novice level DLL worker.

    What exactly did you do by "reset the incompatible array"?

    Of course if I've missed something that is in a tutorial somewhere please point to it. I'd like to figure out a little more about how stuff like this is made. :P

    S

×
×
  • Create New...