Jump to content

GoAHead

Members
  • Posts

    72
  • 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. Show previous comments  2 more
    2. Lisias

      Lisias

      Hi!

      I concluded the report:

      There's something fishy on the IT part config. Since I don't know the KSPIE PartModules, I can't say what, but hey… Now we know where and how.

      You will need help from the IT guys, and probably from the KSPIE's maintainer too in order to identify exactly why only IT parts are borking.

       

    3. GoAHead

      GoAHead

      thx @Lisias. i will let them know. i'm afraid there will be no support. .. but lets try

    4. Lisias

      Lisias

      Just to finish the report, as I had diagnosed things later and my last message here left implied that KSPIE and/or IT were at fault somehow:

      • It's a KSP's limitation : the IPartCostModifier uses float , and so are prone to loss of precision with really expensive (or cheap) parts.
      • KSPIE had no role in the problem, other than triggering it.
        • IT, ditto. It only happens that these parts are expensive enough to get screwed by the float squashing problem.
      • A new PartModule were added on KSP-Recall to handle the situation.
      • All the other problems detected were just noise, they didn't affected the outcome.
×
×
  • Create New...