Menu

#842 Unable to Repair Destroyed Leg (limb?)

Stable
closed
Taharqa
repair (13)
Duplicate
2015-08-20
2015-03-08
scjazz
No

MHQ 0.3.12

Probably related to this...
https://sourceforge.net/p/mekhq/bugs/837/

OPFOR unit gathered from Salvage with Destroyed leg.
The leg was unrepairable after salvaging necessary parts. The must salvage everything warning kept appearing even though everything was ready.

This only occurred with newly gathered OPFOR Unit. All Player units with destroyed parts seemed repairable. However, no Player units were missing a leg.

Restarting MHQ fixed the problem.

Related

Bugs: #890

Discussion

  • stopcomplaining2

    Reported this a while back as well : https://sourceforge.net/p/mekhq/bugs/805/

     
  • Taharqa

    Taharqa - 2015-08-01
    • assigned_to: Taharqa
    • Resolution: None --> Accepted
    • Milestone: Undetermined --> Stable
     
  • Taharqa

    Taharqa - 2015-08-01

    This sounds like the same problem that I fixed in Bug [#890] but that was induced by using the GM Edit Damage Dialog while it sounds like this might be a more general problem with all enemy units collected as salvage. I want to try testing this out and seeing if I can reproduce it the same way before I close it.

     

    Related

    Bugs: #890

  • Taharqa

    Taharqa - 2015-08-19

    See some additional notes in Bug [#890] about this issue. I was unable to replicate the problem with scenario resolution using manual resolve from mul files.

     

    Related

    Bugs: #890

  • scjazz

    scjazz - 2015-08-19

    Use auto resolve... the problem here as it has always been is that this is a Run Time bug. If you play Battle, Resolve in MHQ you will see it. If there is any save/reloads occuring you won't.

     
  • Taharqa

    Taharqa - 2015-08-20

    Well, manual resolve didn't involve any saving reloading of the campaign. But I will still see if I can try it out with auto-resolve.

     
  • Taharqa

    Taharqa - 2015-08-20
    • labels: --> repair
    • status: open --> closed
    • Resolution: Accepted --> Duplicate
     
  • Taharqa

    Taharqa - 2015-08-20

    Okay, Bug [#915] actually had some data that allowed me to reproduce this bug, or at least what I think is the root cause of the bug. Read there for more details, but it is now fixed and I am closing this one as a duplicate. Please open a new bug if the problem persists in release 0.3.17.

     

    Related

    Bugs: #915


Log in to post a comment.

MongoDB Logo MongoDB