Is this not the issue of just contact detection jitter? Ie when you have multiple esm detection, say one of high quality, and then one of low quality, it jumps around from high detection to low detection. Ie you could have some high quality source that nearly nails it's exact location and the contact is updated, then a sat comes along with a low quality detection with massive ambiguity and the contact is updated to that low detection, and back and forth it goes.
Basically it doesn't know the prior detection were more accurate...and arguably information wise...that's probably right in the scene at that point, it shouldn't, and as annoying as it is it should jitter. Maybe it could mesh the last couple detections...but I think it already does.
WZ7 (generic sigint ~yr2000 #5731, -95 sensitivity, direction accuracy 2.0, precisionid capable:yes, loss: 10, scanrate: 20)
J-16D (esm #5798 -90 sensitivity (less sensitive), direction accuracy 1.0 (more accurate), precisionid capable: yes; loss: 10, scanrate:20)
J-16D (Generic Comms monitor 5260, -107.0 (extremely sensitive), direction accuracy 180.0, precisionid cap:yes,freq: 30-500mhz,loss:10,scanrate:20)
So the J-16D generic comms detection is stepping on the WZ-7's and J-16D's esm better overall detection, because the generic comms while more sensitive is _horrible_ at directional accuracy.
thewood is correct that if you destroy\remove the comms monitoring, then you will no longer see the problem, namely because the 5798 and 5731 sensors while different aren't THAT different and are not introducing wildly different positions to cause as much noticeable contact location jitter, though there may be little.
The following Comms Monitor flagged sensors that have 180 as direction accuracy numbers of 180 are, they also have the best sensitivity assuming -107 isn't a flag for behavior:
211 EN/Mk9000 Elnath [TRS-600] (90's)
1096 EN/Mk9500 Regulus [Comms Monitor] (20's)
5260 Generic Comms Monitor [Advanced] 2000s
5833 Generic Comms Monitor [Advanced] 1980s
5835 Generic Comms Monitor [Advanced] 1970s
6495 Generic Comms Monitor [Advanced] 2020s
6496 Generic Comms Monitor [Advanced] 2010s
All the rest in the database range from 1.0 to 10.
Unrelated there are 5 other sensors that have 180 for that field that are not comms monitors.
Maybe that's by design or 180 is a marker for handling things a certain other way i simply do not know.
If not perhaps...maybe those should be tweaked in not markers, particularly the later decades?
I tend to replace all generic comms monitors when it's important to the scene with #695's (-95, 30mhz to 2.5gig , and 3.0 direction), or remove them when comms detection and jamming is not a thing. I get tired of fighting the jitter and the database, even if I understand it, even if it's kinda real, because sometimes it seriously screw up initial targeting from second to second.
Kind of curious why the J-16D's ESM unit never picks the E-2 up.
Most likely because the J-16 ESM only detects D band (1-2gig) and above, and the APY-9 operates in band-C (500-1000mhz). Where as the generic sigint 2000 (wz7) detects band C, as does the generic comint just barely i it's 30hz-500mz ranges. Shame the in-game sensor page doesn't show bands for ESM's\comm monitors.
