Tracked Target Mis-information

[Kyle Sanders]

I am posting here in General because it does not seem to be RADAR client specific as it happens if I am using VRC, vERAM, or vSTARS

 

Over the past month or so the following bug seems to haunt me almost every controlling session.

.

 

Controller A reaches out to me and asks me to drop my track on a target.

 

I look at the track FDB and it says that it is being tracked by Controller B (and sometimes Controller A that is trying to GET the target track).

 

Just to make sure, I do a .own command on it and it confirms that Controller B or another controller has track on the target.

 

Controller A says that the FDB and .own both say that I own that track.

 

Controller B does a .own on the target and sometimes it shows that either Controller A or I have track on the target.

 

Nobody can manipulate the FDB or flight data of this aircraft.

 

As you can imagine, this makes things very difficult to handle coordination during event level traffic so a look into the flight data servers that track things like who owns a target track would be appreciated.

[Ross Carlson]

3 hours ago, Kyle Sanders said:

As you can imagine, this makes things very difficult to handle coordination during event level traffic so a look into the flight data servers that track things like who owns a target track would be appreciated.

There is no tracking of flight ownership on the server. It's all a peer-to-peer message exchange between clients. It can very easily get out of sync, especially when the various controllers in question have different vis ranges and radio ranges.

[Kyle Sanders]

Ah... so there is no easy way to avoid this?

[Ross Carlson]

I would have to know more about the circumstances that give rise to this issue before I could suggest how to avoid it.