bug in destruction mission

I am getting the following result:
Each armed attacker deals 349 damage.
Each armed defending attack soldier deals 267 damage.(10% penalty when defending against attack soldiers)

With 1,067,940 power remaining, attacker's army charges forward engaging defender's own offensive troops.
Defending Attack Soldiers return fire and inflict 410,192 damage to their opponents!

As a result of this 306 invaders have lost their lives!
History will tell that 310 defending attack troops will have fallen to attacker's force by the end of the battle. (10% penalty)
-----
Should defender not have lost 306 * (349/267) (ratio of my power vs. his, 2 max.) = 400 defending attack troops?
Same goes for weapon value.

Jiro wrote:I am getting the following result:
Each armed attacker deals 349 damage.
Each armed defending attack soldier deals 267 damage.(10% penalty when defending against attack soldiers)

With 1,067,940 power remaining, attacker's army charges forward engaging defender's own offensive troops.
Defending Attack Soldiers return fire and inflict 410,192 damage to their opponents!

As a result of this 306 invaders have lost their lives!
History will tell that 310 defending attack troops will have fallen to attacker's force by the end of the battle. (10% penalty)
-----
Should defender not have lost 306 * (349/267) (ratio of my power vs. his, 2 max.) = 400 defending attack troops?
Same goes for weapon value.

You are right. Not sure what might have caused this bug.
the defender should have lost 400 units.

Did the defender have any defending soldiers when this mission has been done?
maybe some attackers died in the first phase of the battle.

No, no defence

It is weird that this problem hasn't been found earlier.

It looks like it is comparing weapon level (with a 10% penalty for the defending party) between attacker and defender, ignoring all other things, like tech, pbp and yala bonuses. When attacking someone with submachine guns with my grenade launchers, I did destroy nearly 200% of his units.

Does this bug still exist or its solved?