Menu

#179 Issues with engine changes and base number of heatsinks

Stable
closed
None
fixed
1
2015-06-01
2015-04-23
mitt
No

I'm having a hard time pinning this one down, but with some mechs changing the cockpit to small sets the free engine heat sinks to 0. Happens on Flamberge D, Avatar OJ, Cauldron Born Prime but not Annihilator C, Anvil 5M, Lament-4RC as examples from some random checking.

Discussion

  • Hammer

    Hammer - 2015-04-23

    Ok, been playing around with this one. Pretty sure the issue is with the Base(omni) HS box and it getting reset to 0 in certain conditions.

    All the mechs in the first part of the post have the Omni box checked. If I change the cockpit the Base(Omni) resets to 0, and Engine Free changes to 0.

    Also if I touch the move it resets them to zero.

    I think if the move changes it should recalculate the Free sinks, and the cockpit part it shouldn't rest the Free Sinks to Zero.

     
  • Nicholas Walczak

    • summary: Issues with small cockpit --> Issues with engine changes and base number of heatsinks
    • assigned_to: Nicholas Walczak
    • resolution: none --> accepted
    • Milestone: Post-Stable --> Stable
     
  • Nicholas Walczak

    The problem is that, when the resetEngine() method is called, it doesn't remember the base number of heatsinks, and so they get reset down to 0. I'm going to change the subject to better reflect the issue.

     
  • Nicholas Walczak

    Fixed in [r1535]. I just updated StructureTab.resetEngine() so that it updates the new engine with the old engine's base number of heatsinks.

     

    Related

    Commit: [r1535]

  • Nicholas Walczak

    • resolution: accepted --> fixed
     
  • Dylan Myers

    Dylan Myers - 2015-06-01
    • Status: open --> closed
     

Log in to post a comment.