Forum Interference / Problems

[dl1812]

Some of the comments on here defy belief.
Do the posters on here understand exactly what a beta is, or realise the amount of programming required to acheive even a minor change to any software ?
Some comments have been spiteful, rude or unhelpful, rather than trying to achieve a better product by feeding back constructive comments.

Gentlemen, it is a FREE Beta; it's cost you nothing. If you can't understand the basic concept of Beta testing, then uninstall it and wait for the public update; give AirNav a break and some breathing space !

Sorry - just my 2p Worth....

[fatkat]

even with the odd niggle beta 3 is better than v2  ....just the fact its quicker outweighs all else !

thumbs up to airnav !

[mdobuk21]

i think its a fantastic update, the extra flight id`s is a massive improvement

Mark

[vruma]

An additon to the 'Low' bug list:

F9 key
The tools menu states the F9 key to call up the Myflight tab, but has no function.

Remark
The current online help manual says that the F9 key is assigned to call the 'Avoid overlap funtion' and F10 to call the 'Avoid navigational aids overlap'. I assume both functions happen automatically in the current software version, without need of manual initiation. That's why those two key assignments are used otherwise now: F9-MyFlights, F10-Network. Anyone please correct me if I am wrong on that.

[RodBearden]

I think you are correct, Vruma.

I've been nagging Development for ages about that. My nagging eventually got us the +/- keys for map zooming, so we might get F9 working sometime as well ;-)

Rod

[radarspotter10]

An additon to the 'Low' bug list:

F9 key
The tools menu states the F9 key to call up the Myflight tab, but has no function.

Remark
The current online help manual says that the F9 key is assigned to call the 'Avoid overlap funtion' and F10 to call the 'Avoid navigational aids overlap'. I assume both functions happen automatically in the current software version, without need of manual initiation. That's why those two key assignments are used otherwise now: F9-MyFlights, F10-Network. Anyone please correct me if I am wrong on that.

hi all
if i press f9 i get more aircraft must be overlap.
from pat using V3.0

[jmhayes]

Odd behavior just noticed: if you sort by ModeS and select a flight that subsequently times-out, the selected aircraft jumps and the list scrolls far away from where you were watching.  this is annoying if, for instance, you're wanting to keep a watch on a particular section of codes, like the border between one range and another.  Can't it just stay approximately where it was?

[swadeep]

how about releasing something that makes radar box runs on vista 64 bit first :) please please! been waiting for so long support! You gotta at least give us that and we can help with reporting issues with beta also. It's frustrating not being able to even install radar box.

[tarbat]

They should get a new beta team next time.  That will do some rigorous testing.

We tested what we were told was in the beta.  And regression tested.  I had no problems.  Maybe you'd have liked to spend hours diagnosing and helping develop the logic to received non-ADS/B FlightIDs.  Sorry, but you touched a nerve with that swipe at beta testers :(

And I was in such a good mood as well, having got back from 2 days on the north Sutherland coast in blazing sunshine.

[Allocator]

Tarbat,

I think that it has been established that CowboyNut was one of the trouble makers from before who had been banned, then registered under another name - hence the 18 Jun joining date and only 7 posts!

So, don't loose any sleep over it, he was just trying to wind people up :-(

[EMA]

Tarbat

You should know that you are a respected member of this forum, it is easy to see who wants to help and those that only complain. Thats forums for you ;-)

[Falcon]

I stand by what I have said. This issue seems a bit Alpha. Alerts worked in 2.01 but no longer work in V3 beta! How did that get past a closed beta test?

It didn't. They knew about it. I reported it :-) I imagine that since the software was going to be launched as a beta that they would take care of it at a later date and have even a larger user base give feedback about the software and get a more complete and comprehensive view of the issues, which does makes sense. After all who would ever go and install a beta and expect to have a stable system? I had a chance to see what one might consider Alpha and what you see now is no comparison to that. The new software is great and once all the bug fixes are implemented it's really going to be sweet.

Regards,
Falcon

[vruma]

An addition to the bug list:

No search function in the "Airline" section of the filter toolbar
If a criteria is entered into the field "Search for" the list does not update to show the matching entries.

(I'd categorize it minor)

Edit: here's a pic.

[jgrloit]

As the Airline field is a graphic, I am not surprised that there is not search on it.
The correct text field to search on would be the FlightID, with the generic first 3 characters.

To implement a search on the graphic would require reverse lookups from the logo to the FlightID, and could slow the system!!!!

[Andy Frost]

A minor issue that I had discovered in version 2.0 and forgotten about, which I see is also in version 3.0 Beta...If you click the Cancel button on the Welcome dialog (the one with the Start, Account and Cancel buttons on it) then on re-entering the program many of the previously chosen settings have been lost. For example, the Interface panel is now removed, the vertical tracking view F8 flight display reappears, Map/Aviation Signs/Station Labels/Name is now unchecked etc.

This might be desirable in some respects, e.g. "Restore Installation Defaults" (do we have that somewhere?) but at least there should be a warning on the button press.

Another issue following on from the one above: Having never tried Restore Desktop from the Window menu I assumed this would restore my settings to the defaults, so I clicked on it. This blanked my map area to grey and disabled all my toolbars, I also got disconnected from the network ("Get Flights From RadarBox Network" got unchecked). On retrying this the same occurred but I remained connected.

I see now, after reading the manual, that Restore Desktop is to be used in conjunction with, and importantly after Record Desktop.  Perhaps in this case Restore Desktop should be greyed until Record Desktop has been selected and as Restore Desktop follows on logically from Record Desktop it should perhaps be below it in the menu.