Dynamic threat/ detection zones in the mission editor

[upyr1]

I'm sure I have brought this up I would love to see the size of the detection and threat zone grow and shrink based on the selected aircraft. 

For example, when you have nothing selected you will see the maximum range

then if you select an aircraft the range will shrink based on the RCS, altitude, and the like. Right now the RCS is a fixed figure but if ED can do them more realistically then for this feature to work it would either have to be based optionally on the average RCS or the worst RCS 

 

[Exorcet]

Static rings are fine. Missile range nor radar range can be pinned down to a precise figure. The rings are there to give you an indication of when you might be in danger, not to tell you the exact distance you can fly at to avoid being fired on. Radar detection itself is probabilistic. This is why radar ranges are often paired with a detection probability, like range at 50% chance of detection.

I guess for experimenting, adjusting rings might be nice, but they're not all that practical for an actual mission.

[upyr1]

2 hours ago, Exorcet said:

Static rings are fine. Missile range nor radar range can be pinned down to a precise figure. The rings are there to give you an indication of when you might be in danger, not to tell you the exact distance you can fly at to avoid being fired on. Radar detection itself is probabilistic. This is why radar ranges are often paired with a detection probability, like range at 50% chance of detection.

Your rcs and altitude can alter the ranges where you would be in danger. 

[draconus]

12 hours ago, upyr1 said:

Your rcs and altitude can alter the ranges where you would be in danger. 

You want radar simulations being calculated in ME?

[upyr1]

2 hours ago, draconus said:

You want radar simulations being calculated in ME?

Basically. I have always thought the ME needs to provide as much information as possible. I also want to see the old mission classification system get brought back

[Exorcet]

23 hours ago, upyr1 said:

Your rcs and altitude can alter the ranges where you would be in danger. 

Yes, but even if threat estimates were adjusted you still couldn't treat the adjusted line as a safe boundary. Things also get tricky as RCS gets reduced because then you have the situation where if you do get detected you're in the NEZ for the missile, and if detection is probabilistic there is no way of knowing exactly when you'd be detected anyway. This makes it so you kind of end up with a fixed ring anyway, or one that doesn't adjust that much.

Intelligence should also be taken into account, exact threat positions might not be known (if we're talking about information shown in mission briefings or on the F10 map).

All of that said thinking about it more there could be some uses for dynamic rings, but the current fixed rings shouldn't be removed as an option if dynamic ones are added.

[upyr1]

2 hours ago, Exorcet said:

Yes, but even if threat estimates were adjusted you still couldn't treat the adjusted line as a safe boundary. Things also get tricky as RCS gets reduced because then you have the situation where if you do get detected you're in the NEZ for the missile, and if detection is probabilistic there is no way of knowing exactly when you'd be detected anyway. This makes it so you kind of end up with a fixed ring anyway, or one that doesn't adjust that much.

There are two ways to handle the probability side of the threat zones, one the rings are simply smaller the other you have you have color coded rings. Either  The main idea is that if you are building a flight plan, you'll know how to thread the needle.  

2 hours ago, Exorcet said:

Intelligence should also be taken into account, exact threat positions might not be known (if we're talking about information shown in mission briefings or on the F10 map).

All of that said thinking about it more there could be some uses for dynamic rings, but the current fixed rings shouldn't be removed as an option if dynamic ones are added.

There should be a dynamic/static check box.