Current status of corrections:
--------------------------------------------------
>-The Execute a file box is still always ticked in alerts.
Corrected.
--------------------------------------------------
>-Flights on the network grid still jump around but not as bad as in the last exe...or so it seems so far.
We are still working on this one.
--------------------------------------------------
-Sometimes an Alert warning will force RadarBox to jump to the front of all windows. RadarBox jumping to the front still seems to happen randomly for other reasons that I can't figure out yet.
It will take more than 1 week to investigate this one in detail so as it is being reported by only one beta tester and no users reported it on the forum we will go ahead with V3.0 Patch 1 public beta to check the output from the rest of the community.
--------------------------------------------------
-I'm experiencing the same issue. When first started network flights are normal, however when "Show All" is selected all of the flights from the MyFlights grid appear in the network grid.
Corrected.
--------------------------------------------------
-The Flight ID Alerts and squawk alerts do not work at all, either with a specific ID or code entered or with a wildcard entries.
Only one alert will be sent per mode-s received. So for example you set an alert for A380, SIA001 and mode-s of the aircraft, only one alert will be triggered for the aircraft. So if the the first alert in the in range one, no more alerts will be triggered for that aircraft. This explains the "error" above.
--------------------------------------------------
>Also do you use the email function to notify you of an alert?. On the alerts that do function correctly, when I receive an email only one line (whatever was identified to alert on) is sent. In previous versions I would get additional flight details such as Flight ID, Aircraft type, speed, heading etc. Those details still show in a pop up window but are not transferred over to the email notification as in past versions.
You will receive all the details available when the alert is triggered. We have confirmed this and it working properly. If only one detail is available then the alert is sent only with this one.
--------------------------------------------------
-When an alert is generated and an email is generated, only the feature that is alerted on is transmitted in the email. For example, a registration alert only shows the registration that is alerting. Previous versions would also include the Flight ID, Registration, Aircraft Type, Route Altitude and Speed, for an alerted aircraft if any of those fields had information.
Explained above.
--------------------------------------------------
-The problem with old routes is still present - see attached gif - Dev was going to show the old route if no update was available, but it's still not showing.
We have tested this one several times and it worked. In resume if you have on your local database, for example, flight ABC123,EGLL,KDFW older than 6 months, it tries to contact the server. If nothing is retrieved then the local data, even if old, will be used. Any other beta testers experiencing this problem?
--------------------------------------------------
-the '*' symbol for new contacts is still not working
Corrected.
--------------------------------------------------
-I still get a very large number of "Flight does not have positional information' messages when double clicking on flights in the grid even with the NA flights removed.
Corrected. If no position is known or it is expired the flight will not appear on the NW grid.
--------------------------------------------------
-The * symbol only appears in reporter for codes with no Reg/Serial. When these update the * does not appear in reporter like it used to for new contacts like it used to.
Corrected.
--------------------------------------------------
>SmartView showing flights with status NA
Corrected.
--------------------------------------------------
