SAM
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
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' or 'no' and determines that this BuildingType is a SAM (surface to air missile launcher) and thus its weapons can only fire at AircraftTypes.
NOTE: this is unused in Red Alert 2 as the use of this means that the structure will not fire InfantryTypes,VehicleTypes with JumpJet=yes set or acquire them as targets - it will only target AircraftTypes.
(For YR only) Because the SAM tag has many limitations If you want give BuildingTypes (AA Tower) The fake SAM=yes effect can be used
I recommend that you use the Natural=yes tag for BuildingTypes (AA Tower)
And use the tag Unnatural=yes for InfantryTypes,VehicleTypes,AircraftTypes All that can fly.
Note
Aircraft designated as targets must not exist in the [General]►PadAircraft list;
- otherwise, the SAM will not even aim.
Aircraft designated as targets cannot have a valid building in their Dock list;
- 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.
At the same time, the frequency of re-locking and turret rotation in this case does not adhere to the weapon's ROF 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] > OmniFire=yes.
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 LandTargeting=1.
In other words, SAM targets can only be Aircraft that have AirportBound=yes, Dock=none, and have taken off.
Currently measured:
In the YR1.001+Ares3.0p1+PhobosBuild#45 environment
it is functioning normally.
In the YR1.001+Ares3.0p1+KratosPPv0.1.15 environment
the SAM building will be prohibited from acquiring targets
- (the author of KratosPP stated that this part was not modified at all, and the author does not understand this logic either).
In the YR1.001+Ares3.0p1+PhobosBuild#45+KratosPPv0.1.15 environment
the SAM can acquire targets normally
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.).