Component:strob-core: Difference between revisions
Trinitavia (talk | contribs) added page (copied lore from nebfltcom) |
m →Stats |
||
| Line 26: | Line 26: | ||
| Power || <span style="color:#FF4040;">'''-150'''</span> (kW) | | Power || <span style="color:#FF4040;">'''-150'''</span> (kW) | ||
|- | |- | ||
| Modifier: Jamming LOB Accuracy || <span style="color:# | | Modifier: Jamming LOB Accuracy || <span style="color:#90EE90;">'''+30%'''</span> | ||
|- | |- | ||
| Broadcast Jam LOB to network? || Yes | | Broadcast Jam LOB to network? || Yes | ||
Latest revision as of 07:51, 30 September 2026
In Game Description
A dedicated processing subsystem for radars, allowing them to more finely determine the direction of an incoming jamming strobe as well as broadcast the resulting LOB to the sensor network. Once a jamming LOB is in the sensor network it can be crossed with other bearings to determine a fix.
Gameplay usage
Stats
| Adaptive Radar Receiver | |
|---|---|
| Cost | 15 pts |
| Dimensions | 2x2x2 |
| Hitpoints | 40 |
| Hitpoints to Function | 10 |
| Damage Threshold | 10 |
| Mass | 4 Tonnes |
| DC Priority | Low |
| Power | -150 (kW) |
| Modifier: Jamming LOB Accuracy | +30% |
| Broadcast Jam LOB to network? | Yes |
Notes
Lore
Frankly, it's pretty damn easy to pick out jamming in a sweep, you just need to compare signal intensities to what you already know, it's elementary. The hard part is determining the distance and precise direction which- even with our tech- is algebraic, you feel me?
Correlators automatically snag any signal intensities over a given threshold and stores that in a table. The next signal it picks up will compare the timing, the general bearing of the signal relative to the receiver, and then perform math that is far too complex for me to think about. A little bit of time here and there and it'll give you a basic 'look here' where the jamming source or anomaly is located but don't expect miracles, it's still working off a whole bunch of false data.
- I. Parker, CMC
