[REPORTED]"Unit Hits" Trigger Condition no longer functioning

The "Unit Hits" Trigger Condition in the Mission Editor appears to no longer function. I created a test mission (attached) with three AI planes in front of the player F-16 (screenshot 1); An A-10C, an F-5E-3, and an F-5E (to test a non-playable aircraft unit). I've set a trigger for each AI aircraft to display a text message when a "hit" is recorded (screenshot 2).

Test variations:

1) AI targets set to "Immortal ON" | Trigger Condition: Unit Hits | Result: Text message not received

2) AI targets "Immortal OFF" | Trigger Condition: Unit Hits | Result: Text message not received

3) AI targets "Immortal OFF" | Trigger Condition: Unit Dead | Result: Text message received

I tested variation 3 just to make sure that changing the Condition to something different verified the trigger itself was functioning correctly.

_______________________

I would also like to report that this trigger condition hasn't been working for some time for client aircraft in multiplayer, while it worked for the host. For example, I created a series of dissimilar air combat missions for myself and a group of friends, in which the AI aggressors would be evaluated as "killed" whenever any bullet or missile impacted their aircraft, after which they would disengage and fly away. However, the "kills" were only announced whenever the person hosting the mission would hit the AI aggressor. Any client that had joined would fire missile after missile (or guns) into the aggressors, and no "kills" would be recorded.

This caused me to abandon the Multiplayer version of the missions, and instead focus on the Singleplayer versions. But now those versions no longer function correctly either due to this Trigger Condition not working. (I don't know which patch caused this, since the last time I played these missions was several months ago)

[Unit Hits] Test Mission.miz

Just tested this in DCS OpenBeta 2.5.6.55363, and this trigger condition appears to be working again. Not sure if this just didn't make it into the changelog, or if whatever caused it to quit working in the first place was rectified or changed.