I'm afraid not I think you might be asking if, when viewing a receiver's feed that is also being merged into a merged feed, there is a relationship between the aircraft plotted for the receiver and the aircraft tracked on the merged feed? If so then no, there is no relationship - separate aircraft lists are maintained for each receiver and the merged feed. The aircraft lists are what drive the web site display. The aircraft list for the receiver doesn't know anything about the merged feed aircraft list.Skibox wrote:Am I making any sense here?
The number of aircraft shown in the feed list on the main display is the number of aircraft being tracked. Aircraft remain tracked for several minutes after their last message, long after they are removed from the display - hence the disparity.Skibox wrote:my merged feed shows 200 A/C in feed stats, but only 150 in the web server list
The merged feed is a BaseStation feed, regardless of the format(s) of the constituent feeds. VRS can't convert BaseStation to AVR, but pass-through should work (although the output will be BaseStation format). I keep meaning to add an item to the bug tracker to put validation in for the rebroadcast format to stop people selecting formats that won't work and I keep forgetting - I've added it nowSkibox wrote:1. Rebroadcast server on merged feed of Beasts does not work if set to "AVR" or "Pass-through".
Under Windows the feeds have heartbeat timers on them, if there's nothing on the feed for 30 seconds then it starts sending heartbeat packets to the server and reconnects if there's no reply. Under Linux I can't set the heartbeat timers so it just drops the connection and reconnects if there's no data after x seconds. I can't remember what the timeout is offhand.Skibox wrote:please add a check for incoming data
I can't reproduce this, when I change port on a feed it closes the old connection and opens a new one. Only the new feed is visible on netstat, but my netstat does take a minute or so to complete. By default netstat will show TIME_WAIT connections, are you seeing those? Or are you seeing CLOSE_WAITs? On which side of the connection are you running netstat?Skibox wrote:3. When changing an active feed's properties (IP or port), VRS connects with the new settings, but the old feed is not closed, it's just invisible and can be seen with netstat.
I can't reproduce this either. When a connection to the rebroadcast server is closed it gets removed from the GUI's list.Skibox wrote:4. Closed/abandoned rebroadcast server connections are not erased from list.
It's supported. What was the exception?Skibox wrote:5. Got an exception error when using a DNS name instead of an IP adress for an RX. Is this supported?
Are you running under Windows or Mono?