reported earlier Issues with static object Tank 2 & 3

[Giskvoosk]

As of now there're two issues with Tank 2 and Tank 3 under the Warehouses category of the static objects

a) a disconnection between 1)what's represented visually  2)the log event and the actual destruction registration

b) secondary attack is required no matter what absurd amount of explosive is used in the first run. The object seems to have 2 lives

 

Test 1,

Engaged with 65k/mk84/gbu24, all appear as dead visually and in the log, however still intact on f10 view

 

Test 2,

Set of with explosion action at the highest allowed value of 10000, and message to all action is set to be triggered once the tank is dead. Tested with all units under Warehouses category

same symptom, appeared on log but no registration

 

Test 3,

2 explosion each value set to 250, survived first and manage to register in second one.

Destruction Test_2.miz Destruction Test_3.miz

 

Please take a look into the issues, thanks!

Edited June 16, 2022 by Giskvoosk

[Flappie]

I had this issue reported last year, but I hadn't noticed these units could actually die after a second strike. I updated the initial report.

Thanks for the heads up.

[Giskvoosk]

4 hours ago, Flappie said:

I had this issue reported last year, but I hadn't noticed these units could actually die after a second strike. I updated the initial report.

Thanks for the heads up.

You are correct Flappie. 

Tested on one with 4x blu109 the 2k lb penetrator, again failed to knock down these buggers.

Secondary attack might be improper wording from me. Here I was referring to using the explosion action offered by ME, rather than with aerial weaponry. Could be of a different mechanism; also not sure what unit of measurement does the volume variable use.

 

Edit:

Went again with the blu109 jdam, basically you'd have to land on wreckage's bullseye to have a slim chance to kill it.

Killable but ridiculously buggy still.

Edited June 20, 2022 by Giskvoosk