0 Members and 1 Guest are viewing this topic.
I've read through the previous 16 pages of posts on this topic so apologies if I've missed this...Has anyone else noticed this problem with 3.01 ?I'm happier than a pig in manure with the latest version - ATRs, Embraers and bizjets are all throwing up flight numbers and routes (because that box is ticked), something that wasn't available on my previous versions.However... and this is the bugbear from previous versions... I input the full details for N407BV an A320 due Shannon tonight prior to it's pickup on the box. I have 'Auto Populate Aircraft Data' and 'Download Aircraft Photo' ticked in the preferences box but when the aircraft was picked up, Database Explorer was populated (overwritten ! :-( ) by 'Tie up extracted from Country Sequence' in the A/C Name field. This has happened on so many occasions now that I have a real pain in my breasts with the problem. I also find that for 90% or so of new aircraft picked up that the 'AT' field is populated as three dots in Database Explorer, all other fields correct. Apart from that I'm really happy with V 3.01 and I don't really want to untick the 'Autopopulate' box as it was a real pain updating the dB manually prior to his.Speaking of 'untick' can we not have an 'opt in' rather than 'opt out' option for 'Share Data' in Preferences/Radar Box. If Ryanair can do it, surely to God Airnav can do it also ?
I output data from port 30003 to PlanePlotter servers and since installing V3.01 beta my RB has been sending spurious aircraft data to the PlanePlotter servers, causing them to ban me from sharing.
This seems to be tied up with the problem I have. I output data from port 30003 to PlanePlotter servers and since installing V3.01 beta my RB has been sending spurious aircraft data to the PlanePlotter servers, causing them to ban me from sharing.
Now that it is compatible, have you tried telling PlanePlotter to expect SBS-format output ?