How to see if helo unit is dead or shot down and crash landed

[LostOblivion]

Hey,

 

I have tried using unit dead rule, but this does not become true if the helicopter is shot to pieces but doing an auto rotation landing. I want the same text to appear on screen if the helo is dead all together or having crash landed.

 

Cheers, Lost.

[Geert Hooghe]

Maybe the "unit damaged rule" will work for you...

[LostOblivion]

I've considered DEAD or (UNIT DAMAGED and UNIT SPEED LESS THAN 1 and UNIT ALTITUDE LESS THAN 1 and UNIT OUT OF ZONE [the takeoff and landing airport/FARP]). Cannot think of another way.

 

Also, am I right in that PART OF GROUP IN ZONE does not work for aircraft?

[S77th-ReOrdain]

I believe "unit altitude less than" looks to the terrain directly below the unit, so if you use less than 1 and the unit is in the mountains or anywhere else above the terrain, your unit is not below 1 (not sure if it is meters or feet). So, if you remove that condition, it should work. Alternately, check for terrain elevation in the proposed crash area, and make the unit less than approximately 10 meters below that altitude. Since it is difficult to predict where he'll land/crash, it's probably easier to just stick with DEAD or (UNIT DAMAGED and UNIT SPEED LESS THAN 5).

 

Haven't tested partial group in zone for aircraft yet.

[Geert Hooghe]

I've considered DEAD or (UNIT DAMAGED and UNIT SPEED LESS THAN 1 and UNIT ALTITUDE LESS THAN 1 and UNIT OUT OF ZONE [the takeoff and landing airport/FARP]). Cannot think of another way.

 

Also, am I right in that PART OF GROUP IN ZONE does not work for aircraft?

If think "partial group in zone" only works with "switched condition"

[LostOblivion]

Hm, that is weird, Geert. I know it works for groups of ground units. Lots of things that need fixing.

 

S77 do you mean that the physics engine won't necessarily put a landed aircraft into a resting state at an AGL < 1?

[S77th-ReOrdain]

It's not that the physics engine won't allow you to place a landed object in a resting state, it has to do with the Mission Editor not allowing you to place an object below the physical surface of the terrain.

 

Even though you can specify an AGL or MSL altitude for aircraft within the flight plan, you can not make it fly below the terrain. The editor doesn't allow you to specify AGL vs. MSL within a triggered condition, therefore the editor only cares about what value you input within it's known coordinates.

 

Try this. Open the editor and place your curser over the "X" target range SW of Kobuleti. I use imperical, so the altitude reads 33 feet in the editor. At that particular location, units won't spawn below 33 feet. If you place an aircraft at that location and reduce its altitude to 0 feet, the editor will change that value to the lowest altitude at those coordinates, or, 33 feet as soon as you click something outside of that input box. In other words, if you want a trigger to activate at that location for altitude below 1 foot, you would have to put UNIT ALTITUDE LESS THAN 34 at that location. That's because you can't put UNIT ALTITUDE LESS THAN 1 AGL.

[Grimes]

Could use triggers that work off of several assumptions to be made with the behavior of the AI.

 

Unit speed less than 2 m/s, set flag 1

Unit Speed higher than 2 m/s clear flag 1

 

Time since flag 1 is true is 60 seconds and unit damaged, the unit must have landed.

 

Additionally one could check if the unit is in a zone or not to decide whether they landed where they were supposed to or crash landed in a field.