Radar - Revision history

76561199025325593: /* Burn-through sweep */

2026-09-10T06:22:37Z

Burn-through sweep

← Older revision		Revision as of 06:22, 10 September 2026
Line 76:		Line 76:

	Anything the burn sweep detects will me marked as a purple circle, which will be called a burn track. These burn tracks are similar to regular radar tracks, and carry both position and velocity data (velocity data is not displayed in game but attacks fired on the track will account for it). Note that burn tracks are only a single snapshot, and do not update unless another burn sweep is performed. This means that burn tracks will become progressively inaccurate if the target moves away.		Anything the burn sweep detects will me marked as a purple circle, which will be called a burn track. These burn tracks are similar to regular radar tracks, and carry both position and velocity data (velocity data is not displayed in game but attacks fired on the track will account for it). Note that burn tracks are only a single snapshot, and do not update unless another burn sweep is performed. This means that burn tracks will become progressively inaccurate if the target moves away.

			These tracks serve to update the range memory of jamming LOBs.

	Burn tracks last for 30 seconds. They will replace ELINT tracks, but are in turn replaced by regular radar or vis tracks		Burn tracks last for 30 seconds. They will replace ELINT tracks, but are in turn replaced by regular radar or vis tracks

	Ships can detect when they are hit by a burn sweep, and will display an indicator when it happens.		Ships can detect when they are hit by a burn sweep, and will display an indicator when it happens.

	=== Signature radius & bloom ===		=== Signature radius & bloom ===
	[wip]		[wip]

76561199025325593: /* Return Power Density */

2026-09-10T06:21:38Z

Return Power Density

← Older revision		Revision as of 06:21, 10 September 2026
Line 22:		Line 22:
	=== Return Power Density ===		=== Return Power Density ===

	Given the [[radar_cross_section\|radar cross section]] of an enemy ship <math>\sigma</math> at a distance <math>d</math>,		Given the [[radar_cross_section\|radar cross section]] of an enemy ship<ref>varies by ship angle</ref> <math>\sigma</math> at a distance <math>d</math>,
	The returned power density, <math>P_r</math> is calculated by:		The returned power density, <math>P_r</math> is calculated by:

76561199025325593: /* External Links */

2026-09-10T06:20:05Z

External Links

← Older revision		Revision as of 06:20, 10 September 2026
Line 211:		Line 211:

	== External Links ==		== External Links ==
	* [https://docs.google.com/spreadsheets/d/~~1p1lTyz8AxL-o0jM2H24vJnjHVAHhPZjBz4y4dN-SCSA/~~ NotSoLoneWolf's Radar Calculator V7] - ~~A tool to~~ simulate radar and comms jamming ~~performance~~ across a wide variety of parameters		* [https://docs.google.com/spreadsheets/d/1O_mt6tBeqcxT7Cev86FiRHMAyLMbpVUZki_svteVXBk NotSoLoneWolf's Radar Calculator V8.3] - can simulate radar and comms jamming across a wide variety of parameters

	== Notes ==		== Notes ==
	<references />		<references />

76561198132370687: Wording clarification on velocity inaccuracy (SensorMath.UpdateActiveSensorTrack(...) )

2026-03-10T23:49:41Z

Wording clarification on velocity inaccuracy (SensorMath.UpdateActiveSensorTrack(...) )

← Older revision		Revision as of 23:49, 10 March 2026
Line 162:		Line 162:
	Each radar lists a position and velocity error stat, <math>10\delta_r</math> and <math>10\delta_v</math>. That is, divide the values you see in-game by 10 to use the formulas below, then take your final answer and multiply by 10 again to get back to meters.		Each radar lists a position and velocity error stat, <math>10\delta_r</math> and <math>10\delta_v</math>. That is, divide the values you see in-game by 10 to use the formulas below, then take your final answer and multiply by 10 again to get back to meters.

	Velocity inaccuracy is not a constant value despite what the game uses for the unit. The true error in velocity is <math>\frac{\text{v}\delta_v}{2}</math>, where <math>\text{v}</math> is the target's true velocity, and <math>\delta_v</math> is 1/10th of the listed value. This error is then pointed in a random direction and added to the actual velocity.		Velocity inaccuracy is not a constant value despite what the game uses for the unit. The true error in velocity is <math>\frac{\text{v}\delta_v}{2}</math>, where <math>\text{v}</math> is the target's true velocity, and <math>\delta_v</math> is 1/10th of the listed value. This error is then pointed in a random direction and the full value is added to the actual velocity. For example, velocity error listed as 5m/s can be translated to 0.5x or 50%, so a track moving at 15m/s will have 7.5m/s of velocity inaccuracy.

	Position error is more complicated. First: each radar has its own deviation curve which gives a deviation <math>\delta_d</math>.		Position error is more complicated. First: each radar has its own deviation curve which gives a deviation <math>\delta_d</math>.

76561198132370687: clarified snr term, some clarification on sensitivity cap

2025-08-25T15:13:16Z

clarified snr term, some clarification on sensitivity cap

← Older revision		Revision as of 15:13, 25 August 2025
Line 35:		Line 35:
	Effective radar range is most often limited by Noise		Effective radar range is most often limited by Noise

	~~In normal conditions, return~~ power is compared against ambient background noise. if the Return Power is less than the background noise <math>P_r < 1\times 10^{-7}</math>, the target is not seen. Note that this is unaffected by noise filtering, which means noise filtering cannot bring the overall noise below ambient background noise ~~for search radars~~.		Return power is always compared against ambient background noise. if the Return Power is less than the background noise <math>P_r < 1\times 10^{-7}</math>, the target is not seen. Note that this check is unaffected by noise filtering, which means for search radars, noise filtering cannot bring the overall noise below ambient background noise.

	If jamming is present, a radar has to be able to distinguish a real signal from the jamming noise.		If jamming is present, a radar has to be able to distinguish a real signal from the jamming noise.
Line 45:		Line 45:
	'''Search radars''' require higher return power than the felt noise <math>P_r > N </math> to see targets. If the return signal from the target also beats signal loss (see below), the target ''is'' seen, and a track appears.		'''Search radars''' require higher return power than the felt noise <math>P_r > N </math> to see targets. If the return signal from the target also beats signal loss (see below), the target ''is'' seen, and a track appears.

	'''Fire control radars''' require a higher '''return power to noise ratio (SNR)''' than the minimum SNR required to lock:		'''Fire control radars''' require a higher '''signal (return power) to noise ratio (SNR)''' than the minimum SNR required to lock:

	<math>10\log_{10}\left(\frac{P_r}{N}\right) > \text{SNR}_\text{min} </math>		<math>10\log_{10}\left(\frac{P_r}{N}\right) > \text{SNR}_\text{min} </math>
Line 61:		Line 61:
	If sensitivity is less than signal loss <math>S < S_L</math> then the target is seen.		If sensitivity is less than signal loss <math>S < S_L</math> then the target is seen.

	This means that sensitivity reaches its maximum benefits at -40dB, as that point where search radars are limited by noise ~~from ambient noise~~ instead.		This means that sensitivity reaches its maximum benefits at -40dB, as that point where search radars are limited by background noise floor instead.

	'''Fire control radars''' do not have a sensitivity stat, and therefore are not affected by signal loss.		'''Fire control radars''' do not have a sensitivity stat, and therefore are not affected by signal loss.

76561198132370687: added note that radar checks for new target every frame, but only updates every 0.25s

2025-07-30T19:11:46Z

added note that radar checks for new target every frame, but only updates every 0.25s

← Older revision		Revision as of 19:11, 30 July 2025
Line 29:		Line 29:
	On a burn-through sweep, <math>P_t</math> is multiplied by the Burn-Through Power Mult. stat.		On a burn-through sweep, <math>P_t</math> is multiplied by the Burn-Through Power Mult. stat.

	Return Power is factored into both Noise and Signal Loss calculations to determine effective ~~radar~~ range		Return Power is factored into both Noise and Signal Loss calculations to determine effective sensor range. Sensors will check every frame for new targets, but will only update and recalculate existing targets every 0.25s (round down to nearest frame)

	=== Noise ===		=== Noise ===

76561198132370687: clarification on sig radius, specifically to separate it from radar signature as a general term

2025-03-10T22:02:15Z

clarification on sig radius, specifically to separate it from radar signature as a general term

← Older revision		Revision as of 22:02, 10 March 2025
Line 83:		Line 83:
	[wip]		[wip]

	Some signatures (such as ships), have a "sig radius" (calculated from half the max component of the signature's boxcollider) that can allow radars to detect the signature beyond the radar's nominal max range. Under normal conditions, this sig radius is a small value, ranging from 39.5m (sprinter) to 138m (solomon). This means that by default, every radar actually has slightly more range than their listed max range. ~~Note that every radar based sensor~~ can take advantage of this~~, including the locking mode on multi mode radars~~ (~~e.g. parallax) and~~ radar ~~seekers on~~ missiles.		Some signatures (such as ships), have a "sig radius" (calculated from half the max component of the signature's boxcollider) that can allow radars to detect the signature beyond the radar's nominal max range. Under normal conditions, this sig radius is a small value, ranging from 39.5m (sprinter) to 138m (solomon). This means that by default, every radar actually has slightly more range than their listed max range. Both search radars and fire control radars can take advantage of this (but radar guided missiles will not)

	Any modifier that increases signature size will "bloom" radar sig, multiplying the sig radius by the same amount. For example, a +1500% sig increase (for a total of 1600% signature) will increase the sig radius from 135m to 2160m, so search radars can detect ~~them~~ ~2km farther than their max range.		Any modifier that increases signature size will "bloom" radar sig, multiplying the sig radius by the same amount. For example, a +1500% sig increase (for a total of 1600% signature) will increase the sig radius from 135m to 2160m, so search radars can potentially detect it ~2km farther than their max range.

	~~Any component~~ that ~~applies a percentage modifier to~~ the ship's signature will factor into this, such as masquerades, EWAR emitters, raider engines, etc, but the radius difference is usually too minor to notice except for very large sig increases from components like railguns or mass drivers.		Components that modify the ship's signature will also factor into this, such as masquerades, EWAR emitters, raider engines, etc, but the radius difference is usually too minor to notice except for very large sig increases from components like railguns or mass drivers.

	Sig Radius is also affected by signature ~~decreases~~ (eg, prowler, radars off), ~~but this~~ cannot reduce the sig radius below the default.		Sig Radius is also affected by signature reductions (eg, prowler, radars off), which can be used to counteract sig bloom from other sources.<ref>This cannot reduce the sig radius below the default, but in practice this limit is irrelevant since default sig radius is very small, and ships with signature reductions are not likely to be detected at max range anyway, making sig radius irrelevant. </ref>

	Note that ~~this~~ only increases maximum range; radars ~~will~~ still have to pass the noise and signal loss checks to detect a target ~~even with~~ signature bloom.		Note that sig radius only increases maximum range; radars still have to pass the noise and signal loss checks against the target's return power to detect a target, so radars may not always be able to make full use of the signature bloom if it can't detect the signature at max range.

	=== Radar Illumination ===		=== Radar Illumination ===

76561198132370687: added link for illum to ewar page

2025-01-22T18:57:34Z

added link for illum to ewar page

← Older revision		Revision as of 18:57, 22 January 2025
Line 92:		Line 92:

	Note that this only increases maximum range; radars will still have to pass the noise and signal loss checks to detect a target even with signature bloom.		Note that this only increases maximum range; radars will still have to pass the noise and signal loss checks to detect a target even with signature bloom.

			=== Radar Illumination ===
			See [[Electronic_Warfare#Radar_Illumination\|EWAR page]]

	=== Track Quality ===		=== Track Quality ===

76561198132370687: corrected snr calc for inaccuracy

2025-01-17T18:19:51Z

corrected snr calc for inaccuracy

← Older revision		Revision as of 18:19, 17 January 2025
Line 163:		Line 163:
	Position error is more complicated. First: each radar has its own deviation curve which gives a deviation <math>\delta_d</math>.		Position error is more complicated. First: each radar has its own deviation curve which gives a deviation <math>\delta_d</math>.

	For search radars, the deviation scales with SNR<ref>This is calculated by dividing the return signal by the recieved noise, and then taking the log ~~base 10~~ of the quotient</ref>; at 0 dB SNR or below, <math>\delta_d</math> is 100% of the listed error in-game, <math>\delta_r</math>. The curves extend to 30.0 dB, where error hits a floor at various amounts between roughly <math>0.1\delta_r</math> and <math>0.3\delta_r</math> depending on the exact radar. See the component pages for each radar to see their curves (not implemented yet).		For search radars, the deviation scales with the natural logarithm of the SNR<ref>This is calculated by dividing the return signal by the recieved noise, and then taking the natural log of the quotient</ref>; at 0 dB SNR or below, <math>\delta_d</math> is 100% of the listed error in-game, <math>\delta_r</math>. The curves extend to 30.0 dB, where error hits a floor at various amounts between roughly <math>0.1\delta_r</math> and <math>0.3\delta_r</math> depending on the exact radar. See the component pages for each radar to see their curves (not implemented yet).

	For fire control radars, the deviation is based on the ratio of the target distance to the radar's max distance.		For fire control radars, the deviation is based on the ratio of the target distance to the radar's max distance.

76561198132370687: Fixed redlink, note that capitalization matters

2024-11-09T08:40:10Z

Fixed redlink, note that capitalization matters

← Older revision		Revision as of 08:40, 9 November 2024
Line 190:		Line 190:

	== Radar Jamming and Counter Jamming ==		== Radar Jamming and Counter Jamming ==
	For more information on this section, please refer to [[~~electronic_warfare~~\|EWAR]].		For more information on this section, please refer to [[Electronic_Warfare\|EWAR]].

	== ELINT ==		== ELINT ==