SAM: Difference between revisions

Revision as of 09:07, 12 April 2025

Flag:	SAM
File(s):	Rules(md).ini
Values:	Boolean values: yes or no, true or false, 1 or 0
Default:	no
Applicable to:	BuildingTypes

Can be set to yes in order to restrict a defensive structure to being a SAM (surface to air missile launcher) site. When enabled, the weapons can only fire at aircraft and not at hovering/flying vehicles, nor at airborne infantry.

In Red Alert 2

This tag is unused in RA2, since the many Jumpjet units (like Kirovs) would be untargetable, but is perfectly valid. Adding it to a Patriot battery or Flak gun would drastically reduce their effectiveness, and other units or defenses would be required to fire at the targets the SAM won't. It is generally better to use armor for target filtering.

In Yuri's Revenge

With the addition of Natural=yes tag to defensive structures or AA units, a kind of inbetween scenario can be achieved. TechnoTypes with Natural will not attack others with Unnatural=yes. With some clever application a modder can more finely tune which targets are valid for a defender.

Bugs/Side-Effects/Unexpected Limitations One quirk of the way AA weapons are handled, is that paradropped infantry cannot be fired upon by the defender, unless it has LandTargeting=1, and the weapon has AG=yes on their projectile. This seems to be because the falling infantry is still considered a 'ground' unit.

While SAM=yes functions well on homing-missile based AA units/buildings, the same can't be said for gun based ones like the Flak Cannon. Making the Flak Cannon a SAM will cause it to rotate to follow the airborne target, but not fire unless the trajectory is just right for that rotation. This leads to a case where firing is inconsistent and far below it's expected ROF.

@@ Line 20: / Line 20: @@
 With the addition of {{f|Natural|yes|link}} tag to defensive structures or AA units, a kind of inbetween scenario can be achieved. [[TechnoTypes]] with <tt>Natural</tt> will not attack others with {{f|Unnatural|yes|link}}. With some clever application a modder can more finely tune which targets are valid for a defender.
-==Note==
+{{bugs}}
-Aircraft designated as targets must not exist in the [General]►{{f|PadAircraft|link}} list;
+One quirk of the way AA [[Weapons|weapons]] are handled, is that [[Paradrops|paradropped]] infantry cannot be fired upon by the defender, unless it has {{f|LandTargeting|1|link}}, and the weapon has <tt>AG=yes</tt> on their [[Projectile|projectile]]. This seems to be because the falling infantry is still considered a 'ground' unit.
-*otherwise, the SAM will not even aim.
-Aircraft designated as targets cannot have a valid building in their {{f|Dock|link}} list;
+While <tt>SAM=yes</tt> functions well on homing-missile based AA units/buildings, the same can't be said for gun based ones like the Flak Cannon. Making the Flak Cannon a <tt>SAM</tt> will cause it to rotate to follow the airborne target, but not fire unless the trajectory is just right for that rotation. This leads to a case where firing is inconsistent and far below it's expected [[ROF]].
-*otherwise, the SAM can only rotate its turret but cannot actually fire.
-However, even so, the SAM can only fire its weapons normally when the target aircraft is in a hover state. Once the aircraft moves, it will only occasionally fire a few shots under specific conditions and the frequency of re-locking and turret rotation in this case does not adhere to the weapon's {{f|ROF|link}} settings, nor is it a fixed value. Even the aforementioned situation of suddenly firing two rounds can occur without facing the target, even if there is no [Weapon] > {{f|OmniFire|yes|link}}. Additionally, SAM enforces attacks only on aerial targets, meaning it cannot fire at targets that have landed on the ground, even if they do not have {{f|LandTargeting|1|link}}.
-In other words, SAM targets can only be Aircraft that have {{f|AirportBound|yes|link}}, {{f|Dock|none|link}}, and have taken off.<br>
-Currently measured:<br>
-In the YR1.001+Ares3.0p1+PhobosBuild#45 environment<br>
-it is functioning normally.<br>
-In the YR1.001+Ares3.0p1+KratosPPv0.1.15 environment<br>
-the SAM building will be prohibited from acquiring targets<br>
-*(the author of KratosPP stated that this part was not modified at all, and the author does not understand this logic either).<br>
-In the YR1.001+Ares3.0p1+PhobosBuild#45+KratosPPv0.1.15 environment<br>
-the SAM can acquire targets normally<br>
-but firing will immediately trigger a Fatal Error, and the EIP address is not in gamemd.exe (the record doesn't really mean much, hence it's not included in the EIP page.).<br>