Missiles: Difference between revisions
(→Missile Mechanics: added launching section) |
(updated heading levels for missile mechanics added wall thickness section) |
||
Line 74: | Line 74: | ||
Programming time is the amount of time it takes to program the channels. Programming time can be reduced by the strike planning center, the missile parallel interface module, or by the Fast Startup missile support module. | Programming time is the amount of time it takes to program the channels. Programming time can be reduced by the strike planning center, the missile parallel interface module, or by the Fast Startup missile support module. | ||
==== Mixed Salvos ==== | |||
Ships with VLS can create and fire mixed salvos of missiles by pressing the "+" icon next to the missile in the weapon menu. Mixed salvos will remain in the weapon menu for reuse until a new mixed salvo is created. When creating mixed salvos for formations, the missile has to be present on every ship in the formation in order to add it into the mixed salvo. | Ships with VLS can create and fire mixed salvos of missiles by pressing the "+" icon next to the missile in the weapon menu. Mixed salvos will remain in the weapon menu for reuse until a new mixed salvo is created. When creating mixed salvos for formations, the missile has to be present on every ship in the formation in order to add it into the mixed salvo. | ||
==== MLS Launcher ==== | |||
MLS launchers exclusive to OSP need to reload between salvos, but do not need to program missiles, and will launch instantly upon order. Programming time has no effect on MLS, but ammo elevators will decrease MLS reload time. | MLS launchers exclusive to OSP need to reload between salvos, but do not need to program missiles, and will launch instantly upon order. Programming time has no effect on MLS, but ammo elevators will decrease MLS reload time. | ||
MLS will not fire defensive missiles automatically. | MLS will not fire defensive missiles automatically. | ||
=== Defensive Missiles === | |||
Also known as anti-missile missiles, or AMMs. Missiles set to "defensive" in their avionics and placed in VLS tubes will be fired by the ship for point defense. | Also known as anti-missile missiles, or AMMs. Missiles set to "defensive" in their avionics and placed in VLS tubes will be fired by the ship for point defense. | ||
Line 89: | Line 89: | ||
Multiple ships with AMMs and comms on will communicate with each other to "deconflict" AMM launches, which means only one of them will fire a salvo against incoming missiles rather than all of them firing individual salvos. Note that this will only work if the ship has full communication with the rest of the team, if comms are cut (by combat damage, comms jamming, or intentional emcon), then the ship will not participate in deconfliction and will fire AMMs at all applicable targets | Multiple ships with AMMs and comms on will communicate with each other to "deconflict" AMM launches, which means only one of them will fire a salvo against incoming missiles rather than all of them firing individual salvos. Note that this will only work if the ship has full communication with the rest of the team, if comms are cut (by combat damage, comms jamming, or intentional emcon), then the ship will not participate in deconfliction and will fire AMMs at all applicable targets | ||
==== Doctrine ==== | |||
Doctrine decides how defensive missiles are fired against incoming missiles. | Doctrine decides how defensive missiles are fired against incoming missiles. | ||
Line 126: | Line 126: | ||
| [[File:Rocket Container Icon.png|25px]] CM-400 Container || 3 || 150 || 4x || 20 || 4 || 125-225 || 20-35 || 2562-34875 || 6.4-12.8 || 1.0-3.6 || 0.1-3.3 || 1600m<sup>2</sup> / 4000<sup>2</sup> || 1 || [[File:OSP Roundel.png|25px]] | | [[File:Rocket Container Icon.png|25px]] CM-400 Container || 3 || 150 || 4x || 20 || 4 || 125-225 || 20-35 || 2562-34875 || 6.4-12.8 || 1.0-3.6 || 0.1-3.3 || 1600m<sup>2</sup> / 4000<sup>2</sup> || 1 || [[File:OSP Roundel.png|25px]] | ||
|} | |} | ||
==== Wall Thickness ==== | |||
Missile wall thickness is armor for the missile, though unlike ship armor, missiles use a far simpler system. | |||
If the AP of the incoming attack is less than the wall thickness, it will only deal half damage to the missile. | |||
=== Payload === | === Payload === |
Revision as of 17:41, 22 June 2024
Missiles are the most powerful weapons a ship can carry but they have limited ammunition, can be shot down and fire slower than other weapons. The number of missiles that can be prepared to fire at the same time depends on the ship's maximum salvo size.
Missile Mechanics
Targeting
Target Selection Cycle
Most seekers choose targets with a lottery. Every 0.5 seconds, the seeker sweeps its cone for targets and adds them to a list. Note that this list is not stored between search cycles, the only thing the missile remembers is the "current target".
- Each target is given an initial score based on its power, how strong the signal is. All powers fall off with distance, so closer targets are usually scored higher initially.
- ACT and SARH power is based on the radar return power density. Also, targets further from the center of the missile's view are scored lower, down to 50% at the edge. ACT power is based on the distance from the missile to the target while SARH is based on the distance from the illuminator to the target and the offset angle between the missile and the illuminator
- For the EO seeker, ship size does not matter; ships give off the same "optical" power, modified only by their distance to the seeker.
- If the missile has an active validator, the validator checks each target and marks it as valid or invalid (this is not saved between seeker cycles for validators other than [ARAD], which has a 30 second memory)
- If the missile has multiple validators, every validator will check each target.[1]
- If the seeker is set to accept unvalidated, and at least one target is valid, then every invalid is removed from the list. If no targets are valid, then the validator is ignored.
- If the seeker is set to reject unvalidated, invalid targets are always ignored.
- The scores of the targets are then modified based on a few factors
- If the missile has a current target, and that target appears in the list again, then:
- If the current target is closer than the seeker's Lock Current Target Distance stat (500 m - 2500 m for different seekers), the seeker is guaranteed to choose this target again.
- Otherwise, if the current target is not a decoy, its score is multiplied by the Target Affinity stat of the seeker (10x for most seekers, 3x for WAKE).
- If the seeker is EO, and it was fired at a track with intel, all targets matching the same ship class have their scores multiplied by 250.
- If the missile has a current target, and that target appears in the list again, then:
- Select a random target weighted by the scores of the targets remaining in the list.
CMD seekers do not undergo this process as their only target is the track they were fired on.
If the seeker is under jamming, the target's return power has to exceed the combined jamming power felt by the seeker to detect the target and add it to the lottery. Note that this is slightly different from the search radar calculations, as the combined jamming power is compared directly without converting it to noise first. As a result, missile seekers are not affected by ambient noise at all.
If the seeker is jammed and cannot see any targets, it will follow a fake target, therefore causing the missile to veer off target. This fake target is placed 1km away from the missile, at a random point up to 4 degrees off the nose with a velocity of 10m/s in a random direction, and changes once every second. Equipping the missile with any validator and setting the seeker to reject unvalidated will push the fake target out to 50km, preventing premature staging if the seeker can detect range.
Validation
All seekers can be set to validation mode. When a seeker is operating in Validation mode, it does NOT provide its original function. Instead, it validates target tracks spotted by the targeting seekers, and tags them valid or invalid.
The validator checks every track spotted by the targeting seekers, ignoring the validator's default range and seeker cone. These targets are tagged valid if the validator can also see it, and tagged invalid otherwise. Validators otherwise spot targets in the same way as if it was a targeting seeker.
Validator reliability is the chance that the validator will provide accurate info. The seeker rolls its validator chance once on launch. If the check fails, the validator will always be wrong (eg, an invalid target will be tagged valid, and a valid target will be tagged invalid).
Validators can negate some secondary effects of jamming when paired with a targeting seeker set to reject unvalidated (assuming the validator itself is not jammed). The seeker will not follow the fake targets produced by jamming (unless the validator is also affected or attracted to the jamming source), and seekers will not stage early due to jamming (unless the seeker cannot detect distance, as the way this is achieved under the hood is just by pushing the fake target from 1km to 50km). Both of these effects are not affected by validator reliability. Note that validators otherwise do not improve the seeker's ability to acquire targets through jamming; the targeting seeker will spot targets at the same range regardless if it has a validator or not.
Validators will apply to all targeting seekers in the missile, even if the targeting seeker is placed behind the validator.
Backup Seeker
Seekers in targeting mode placed in slots behind other seekers will function as backup seekers. They will only activate if the seekers ahead of them do not see a target. If a seeker has an active backup behind it, it can automatically turn itself off in the event of jamming, preventing early staging and following fake targets, and allowing the backup seeker to take over. However, note that the backup itself will not turn itself off when jammed, even if the primary has a clear view; the backup will only turn off if it also has another backup.
Backups will also utilize any existing validators, regardless of position.
Launching Missiles
Missiles may be launched in one of two modes which behave differently based on the avionics/guidance package of the missile
Track mode (TRK)
Firing missiles in track mode is accomplished by right clicking an enemy track and selecting the weapon from the list. This will create a red firing vector and the volley confirmation window. When moused over a track you will see the number of missiles to be fired, the volley count, the distance to target, and the estimated intercept time. ALT will add missiles to the volley one at a time while SHIFT+ALT will add one volley worth of missiles (based on the firing ships missile programming channel count). Right click will remove missiles one at a time and escape cancels the firing selector entirely. Note that while Track mode automatically assigns one missile to the original track, subsequent missiles can be assigned to other tracks. Track mode is useful for quickly getting missiles launched but care should be used both to confirm the correct target and to ensure that the target will not move beyond the seeker cones range by the time the missiles near the target.
Missiles fired in track mode will try to plot an intercept using the reported position and velocity from the sensor network unless the track is moving toward the shooter (within a 30 deg margin), where they will then default to shooting straight at the target instead.
Cruise missiles fired in track mode can also make use of TRP waypoints while in the mode. TRP waypoints are selected with CTRL while in track fire mode and can be used to route cruise missiles around obstacles or to put them on advantageous strike angles.
Position mode (POS)
To position fire a missile right click on open space and select the weapon from the list. This will pull up the sphere widget and and show a red cone representing the missiles primary seeker detection cone. Unlike track fire mode every missile fired in position mode must be individually vectored (Volley size and time to the position are also available in the tooltip). Although more cumbersome than track firing there are number of advantages to position firing even for direct guidance missiles. It's possible to create a "spread fire" pattern with volleys of missiles if the whereabouts of the target are not certain. Also, if the target is moving quickly position fire can be used to lead the target based on its predicted path. Keep in mind unlike track fire mode the final left click confirmation while in position fire mode will add one additional missile to the volley fired.
- Direct missiles fired in position mode will proceed straight on course with seeker active. Care should be used in the sphere tool because if a small sphere is used (adjustable with CTRL), even a few pixels distance between each missile vector will result in a large spread at distance. Note that the seeker will be active as soon as the missiles launch.
- Cruise missiles fired in position mode receive a unique ability. While in position fire mode holding SHIFT and left clicking will create a waypoint for the missiles and move the sphere tool to the location selected. From there a further waypoints can be created. Using this method it is possible to create incredibly complex flight paths for cruise missiles which dodge or even curve behind obstacles. Once the final waypoint is chosen, individual or multiple missiles can be fired using the sphere tool. If multiple missiles are fired in a volley they will travel together to the final waypoint, then follow their individual vectors from there. Care should be used when creating cruise waypoints as the missile seekers are only activated upon reaching the final position from the final waypoint. It is possible to fly inactive cruise missiles directly past enemy fleets exposing them to PD fire.
If the target is too close to the launcher, a "too close" warning will be shown. This warning does not prevent firing. The specific range where the warning is shown depends on the seeker, (1000m for most seekers, 500m for Wake). A missile with multiple seekers will use the longest "too close distance" for the warning.
Programming
Missile launches out of VLS tubes are affected by Programming Time and Programming Channels.
Each ship has a default number of programming channels available, which can be increased with Bus/Bus Array modules. No matter how many missile launchers are on the ship, only a set number of missiles up to the number of channels can be programmed at one time. If you queue more missiles to launch than there are channels available the remaining missiles are queued to program after the first salvo fires.
Programming time is the amount of time it takes to program the channels. Programming time can be reduced by the strike planning center, the missile parallel interface module, or by the Fast Startup missile support module.
Mixed Salvos
Ships with VLS can create and fire mixed salvos of missiles by pressing the "+" icon next to the missile in the weapon menu. Mixed salvos will remain in the weapon menu for reuse until a new mixed salvo is created. When creating mixed salvos for formations, the missile has to be present on every ship in the formation in order to add it into the mixed salvo.
MLS Launcher
MLS launchers exclusive to OSP need to reload between salvos, but do not need to program missiles, and will launch instantly upon order. Programming time has no effect on MLS, but ammo elevators will decrease MLS reload time.
MLS will not fire defensive missiles automatically.
Defensive Missiles
Also known as anti-missile missiles, or AMMs. Missiles set to "defensive" in their avionics and placed in VLS tubes will be fired by the ship for point defense.
When fired automatically, AMMs have no programming time (only limited by the time it takes to open the tubes), and their seekers are automatically set to only detect small targets and will not lock onto ships.
Multiple ships with AMMs and comms on will communicate with each other to "deconflict" AMM launches, which means only one of them will fire a salvo against incoming missiles rather than all of them firing individual salvos. Note that this will only work if the ship has full communication with the rest of the team, if comms are cut (by combat damage, comms jamming, or intentional emcon), then the ship will not participate in deconfliction and will fire AMMs at all applicable targets
Doctrine
Doctrine decides how defensive missiles are fired against incoming missiles.
Missile Construction
Missiles can be designed and colored in the fleet editor. If a design is deleted it will be removed from all missile launchers in the fleet.
Selecting a missile's engine will show the engine configuration triangle, allowing the engine to be focused on Top Speed, Maneuverability or Turn Rate.
Wall Thickness
Missile wall thickness is armor for the missile, though unlike ship armor, missiles use a far simpler system. If the AP of the incoming attack is less than the wall thickness, it will only deal half damage to the missile.
Payload
The payload determines how a missile inflicts damage. The exact damage type depends on the size of the missile.
Avionics Package
The avionics package determines how the missile is controlled. It has the following configuration options:
- Weapon Role sets how the missile may be launched:
- DEFENSIVE: Missiles can be launched manually and by the point defense system.
- OFFENSIVE: Missiles can be launched manually.
- Launch Type sets the behavior immediately after launching:
- HOT: The missile's engine will ignite immediately, good for getting the missile moving quickly when fired in range of enemy point defenses.
- COLD: The missile will maneuver around the launching ship with thrusters until it has an unobstructed line to the target or first waypoint before igniting the main engines.
- Target Lost Behavior sets what the missile will do if it loses the target:
- RESUME SEARCH: The missile will search for a new target.
- SELF DESTRUCT: The missile will self destruct.
- Terminal Maneuvers sets what evasive maneuvers the missile will perform on its terminal approach to the target:
- NONE: No evasive maneuvers.
- WEAVE: Missile will weave from side to side.
- CORKSCREW: Missile will spiral towards the target.
- Trajectory Preference sets the approach angle the guidance system will try to maintain.
- FREE APPRAOCH: Missile will fly directly towards the target.
- MINIMUM ANGLE: Missile will try to avoid getting between the launch ship and the target.
Seeker
The seeker determines the method the missile uses to track its target. Most seekers can choose whether to ignore small targets such as other missiles or not. If a missile has two seekers the secondary one (the one not placed at the nose of the missile) can be set to a Seeker Mode:
- TARGETING: Secondary seeker will be used to acquire a target if the primary seeker does not find any.
- VALIDATION: Secondary seeker will be used to validate targets. Missile will favor targets validated by both seekers, greatly reducing the effectiveness of enemy decoys.
Auxiliary
Auxiliary components can be used to grant a bonus to the missile. They can only be used on missiles that include at least 4 components.
- ↑ It can be assumed that the final result will either require all validators or only one validator in order to count as passed, but there appears to be a bug where the pass/fail status is set by an assignment operator rather than a bitwise operator, making each validator overwrite the previous one, resulting in only the last validator in the list having an impact.