RadarBox Software Update

[Runway 31]

Well Bratters at my time in life I reserve worrying for things which really matter

Alan

[chewycanes]

Hi
Over the year that we have been waiting for a new issue i have lost track of what we may expect to be resolved.

Can AN at least give us a list of the bugs that they are going resolve in the next issue so that we are happy none are missed.

I am not asking for new innovations or requests for certain niceties but just known bugs.

Thanks
Brian

[carras320]

Any news if MLAT will be implemented in this update??

Cheers!

[DaveG]

The sad thing is...

By the time they get around to doing the "bug" fixes, the hardware is now well dated and all other virtual boxes are providing more (and mostly for less £).  So even with fixes done, possibly still be lacking.

As for Mlat, think it was said sometime back, the current hardware will not support mlat and that would be a new feature not a bug fix.

[Tramline]

01 Dec - Surely its time for the latest news regarding development timescales for ANRB.  Come on Air Nav please tell us the latest information and how much further Shiptrax has slipped again just when we all thought it was so close........   I wasn't taken in over a month ago either BTW.....

[Tramline]

Hello?  Anyone in?

[AirNav Support]

Work is progressing for ANRB as well at the moment, AirNav Dev will provide details on ShipTrax soon.

We won't give any timescales for ANRB yet as we do not want to work to pressure from deadlines rather work to a product which we think matches our customers needs and demands.

[Marpleman]

We won't give any timescales for ANRB yet as we do not want to work to pressure from deadlines rather work to a product which we think matches our customers needs and demands.

So let's put this to the user community and once and for all identify what these needs and demands are, to avoid you guys wasting valuable time on issues that we're non plussed about?

Regards

Rich

[tarbat]

So let's put this to the user community and once and for all identify what these needs and demands are, to avoid you guys wasting valuable time on issues that we're non plussed about?

Good idea.  Here's the current list of what I have as a bugs list.  Anything to add?

[Marpleman]

Good start Tarbat!

Could I suggest, that priority is given to helping the Updaters, after all they've put so much effort into improving the users enjoyment?

I'm sure there's dialogue from them with the "powers that be", but let's sort their plight out first to give them a better platform,or whatever else they may need.

Personally,for what it's worth, I'd rather see work directed to fixing known problems before expanding on the capabilities with things such as MLAT etc

Rich

[chewycanes]

Hi
Thanks Tarbat for the list.

This is basically what i was asking AN for so that every one can make sure all bugs are addressed.
I hope everyone takes time to check the list an post if they think any are missing.

Thanks
Brian

[tarbat]

This is basically what i was asking AN for so that every one can make sure all bugs are addressed.
I hope everyone takes time to check the list an post if they think any are missing.

And you can be assured that my final list is what Airnav will be using.  Just keen to ensure that all the significant bugs are included in the list, so feedback welcome.

[orkney]

Hello

The serious issue of ADS-B Aircraft taking a long time to appear in the 2D map after they are first received when you are activated for 3D (The 3 buttons are visible on the top right of the screen) is not included in the list.

Andrew

[ACW367]

I agree with all above, the first priority should be for airnav to create a 4.03 patch to cure the bugs.  In my opinion this patch is already 18 months overdue.  This will tide us over whilst prolonged development and alpha/beta testing of whatever version comes next goes on. 

Will look at my detailed list of bugs at home over the weekend, you have the black hole bug in twice.  Here are some more that I can think of while at my workdesk. 

 - The Diacritical mark bug:
The fonts used next to the photo does not support diacritical marks. All diacritical marks in the Navdata corrupt when shown next to the photo.
http://www.airnavsystems.com/forum/index.php?topic=5633.msg64557#msg64557

 - The 'Via' routes bug:
Where the 'via' destination is shown as the final destination of a route, and the real final destination is not displayed
http://www.airnavsystems.com/forum/index.php?topic=6527.0

 - The same flightnumber/different day bug:
If you pick an aircraft up on seperate days using the same flightnumber as it had on the last day you recieved it, then the starttime/endtime for that flight in mylog show as being the full 24/48/72hour period and the flight does not go into reporter. 

 - The ICAO code not coming from server with other updater information bug:
If aircraft are downloaded from server, the updater team entered ICAO code is corrupted by the server.

 - Local alerts not working if aircraft previously on network Bug:

Good start Tarbat!

Could I suggest, that priority is given to helping the Updaters, after all they've put so much effort into improving the users enjoyment?

I'm sure there's dialogue from them with the "powers that be", but let's sort their plight out first to give them a better platform,or whatever else they may need.

Rich

Rich
Us updaters have the tools we need, what is falling down is the information we are creating is corrupted in the way it is presented to users either as it passes through the server, or is interpreted from the updater created information held in Navdata.

The various bugs listed above and on tarbats sheet highlight that ICAO codes, diacritical marks and photo links which we have control of are corrupted at various stages and are not presented to users in the manner which we have created it. 

Regards
ACW367

[tarbat]

Thanks Andrew and ACW367.  All added to the list.