Jump to content

GoAHead

Members
  • Posts

    74
  • Joined

  • Last visited

Reputation

35 Excellent

Profile Information

  • About me
    The Thing from far behind
  • Location
    Vienna

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Single Status Update

See all updates by GoAHead

  1. Hi!

    I have some news for you on Recall's thread:

    Not the news you would like, I still don't know whats happening - I could only confirm this is not a problem being caused by Recall neither TweakScale.

    I'm trying to figure out what to do next.

    1. GoAHead

      GoAHead

      hi @Lisias!. anything i may help with?

      so tweakscale isn't the cause?. i thought it was cause it was only happening after resacling the part. should i report it to the IT thread?

    2. Lisias

      Lisias

      Nope. TS is the trigger for the problem, as it changes the mass and cost of the part.

      I was thinking perhaps a missing use case on KSP-Recall, but apparently it isn't neither.

      Apparently it's something on the part config itself, I'm guessing some missing or improper value on something that, so, misbehaves on that part only and then induce KSP-Recall to bork - whatever is happening, is screwing with `Refunding` in a way that I still didn't understood.

      My best guess, at this moment, is that whatever is getting screwed, is screwed while its code for the IPartCostModifier is being called and so when `Refunding` calls it to calculate the part costs it gets a bogus value.

      Now my problem is to understand what and how (as when it appears to be obvious) and then see if there's something I can do on code, or if I will need to publish a patch for IT.

    3. Show next comments  3 more
×
×
  • Create New...