Version 3.02?

[dumpty]

Dear Airnav

Is version 3.02 a bugless(hopefully) version of 3.01  or are there any new features to look forward to.

Keep up the good work

Simon

[itzikl2]

hello
were is the link do download the new version 3.02

thank you

itzik

[EMA]

It is not available for public download because it is final beta testing.

It won't be too long now.

[tarbat]

itzik, v3.02 is in closed beta testing, so not currently available to the public.  Simon, It is a bug-fix of v3.01.

[Fenris]

itzik, v3.02 is in closed beta testing, so not currently available to the public.  Simon, It is a bug-fix of v3.01.

And are you happy with the degree of bug fixes in 3.02? Personally I have seen little wrong with 3.01 beta (don't use the network much) and seem to have working alerts in the main.

I was wondering if these problems have been fixed OK.

If you can't say anything, no problem.

[AirNav Development]

Those two have been fixed. We are waiting for 3 minor corrections to be done so we can release V3.02 to the public.

[John Racars]

Hi Support,

Are problems like you can see below also been fixed? As you can see the given route-information can not be correct.

Exemples like this I see verry much, and every time when I am running RadarBox.....

For your information: the network was switched off all the time!

[RodBearden]

Hi John

That route information looks good to me - granted that it's picking it up from the Flight ID.

Could it be that the Piper is wrongly broadcasting that ID?

Rod

[John Racars]

Hi Rod,

Are you serious or are you joking? This ridiculous information I showed in the above screenshot is not an isolated case.

It swarm with.

I am verry surprised until sofar that nobody noticed problems like this.

[RodBearden]

John - I'm not joking - RadarBox is correct in that KLM1115 IS EHAM - ESSA, and PH-PAD is the Piper Archer. I see that Airframes.org has the same information as RB is displaying for you - PH-PAD doing flight KLM1115 (don't know where they get their info from, though).

So either RB is mixing up two flights, or PH-PAD is transmitting the callsign in error. Anyone else out there with a different explanation?

I've certainly never seen anying similar in RadarBox myself.

Rod

[DaveReid]

That route information looks good to me - granted that it's picking it up from the Flight ID.

Could it be that the Piper is wrongly broadcasting that ID?

It's not the Piper.  According to my database, KLM B737 PH-BGG is intermittently sending the code that belongs to PH-PAD.

RadarBox is innocent, on this occasion  :-)

[RodBearden]

Thanks, Dave - I was hoping you were around :-)

Rod

[John Racars]

I've certainly never seen anying similar in RadarBox myself.

OK Rod, thank you for your reaction.

As I reported before: the route information on the screen and  in the Interface as well are in much cases NOT correct.

I am verry sorry to say.

[tarbat]

KLM  PH-BGG = ModeS 484966
Piper PH-PAD = ModeS 484967
Would suggest that one of the transponders on the KLM jet has it's ModeS hex code out by one!!

It's always worth checking airframes.org when you see funny's like this.  Many times RB is correct, it's the aircraft transmitting wrong information.

[John Racars]

Ok Tarbat,

Thank you for your explanation. I must have sleep all the time. I always have thought that a ModeS-code was unique.

It still "swarm with it" over here.