AirNav Systems Forum

AirNav RadarBox and RadarBox24.com => AirNav RadarBox and RadarBox24.com Discussion => Topic started by: DaveG on August 07, 2007, 08:12:18 PM

Title: Duplicate Aircraft on screen (Beta Patch Report)
Post by: DaveG on August 07, 2007, 08:12:18 PM
Hi There,

Seem to have found an issue of duplication of aircraft displaying on map (see image attached)

You'll notice I have ringed the ones in question and included the list to compare with. 
Timeout is set to 32 & 35 seconds.  But as you can see some of the aircraft in question have not timed out and even if they had the distance between pairs is longer than 35 seconds.

Nothing in program would solve, had to close and restart program.

Cheers
Dave

(http://www.cougarvirtual.com/miscdg/1.jpg)
(http://www.cougarvirtual.com/miscdg/2.jpg)
Title: Re: Duplicate Aircraft on screen (Beta Patch Report)
Post by: AirNav Support on August 07, 2007, 08:16:59 PM
Thanks for this report. Its very helpfull. Anyone else having a similar issue?
Title: Re: Duplicate Aircraft on screen (Beta Patch Report)
Post by: Allocator on August 07, 2007, 09:32:51 PM
I don't recall seeing duplicate tracks, however, network aircraft are hanging around much longer than they should be.  This seems to happen when they fly out of network coverage, which includes landing at an airfield.

I've just watched UPS214 fly across the UK from east to west and it stopped moving about 15 minutes ago, however, it's still showing frozen in space off the NW coast of Wales.

(http://farm2.static.flickr.com/1096/1043687740_26bb31a73a_o.gif)

I get the same problem around Manchester (EGCC) airport with a whole group of aircraft at about 600 ft and 130 knts which just won't go away.

(http://farm2.static.flickr.com/1147/1043687728_49f9202e17_o.gif)

My settings for Timeout are 30 seconds and hide 30 seconds, although I did change hide to 1 second to see if the aircraft disappeared - they didn't.
Title: Re: Duplicate Aircraft on screen (Beta Patch Report)
Post by: AirNav Support on August 07, 2007, 09:35:33 PM
Ok it is a confirmed bug and we are working on it. Bear with us.