>>AvareX has the ability to change the traffic range used, look in the lower right corner there is a switch for S, M, & L this controls the range for ADS-B traffic.
>>S = 20 entries, +/- 3000ft , and 10nm
>>M = 200 entries, +/- 6000ft, and 50nm
>>L = is almost unlimited
-----
Oh my goodness it's what many of us have been waiting for!
"Medium" seems perfect for operational needs and balancing the processing demands of current tablets and smartphones.
Jeff, that was a quick catch and thanks for pointing it out... I was just about to delete my post and post an updated retraction of my previous complaint about traffic range limits!
I now see that this was incorporated with v0.0.68 (Thank you so much, Zubair!) and I have not had a chance to test this yet since its commit (poor flying weather around me this time of year). I'm really excited to try this out with my Stratux on my next flight.
In regards to your question about the operational needs of displaying traffic beyond an arbitrary 15 miles +/- 3000 feet, it's definitely an operational need beyond those numbers when flying in remote areas. If you fly up here in the northern plains USA near me you might be talking loud-and-clear-5x5 to someone on the same CTAF frequency who is 40nm away from you, 4,000 feet above you, going in to the same airport as you, and being the only other ADS-B target within 50nm. There's been multiple instances of a situation like this when I've been out flying this year (especially headed to fly-in events/gatherings) where previous versions of AvareX limited out distant traffic and I would have to switch apps to the Stratux web interface map page to get a rough idea of whether that aircraft was showing ADS-B out on the map and whether they appeared to be where they were saying they were over the radio. There have also been multiple flights where I've heard an aircraft beating up the pattern and self-announcing radio calls just outside/above/below the range of the previous 10nm - +/-3,000' limit which made it tough to discern if Mr. BillyBob BugSmasher over there was outside of my AvareX ADS-B limit or if he was just still non-ADS-B-equipped.
Thanks for the update Jeff and thanks for the development, Zubair!