14-06-2006, 08:40 AM
As posted before: in some destinations: WSSS VABB PANC etc. fsp doesn't detect correctly the destination.
You can easely check this, placing the plane in those airports: FSP will put NONE or another airport in the departure airport.
I've read that is a problem of afcad files, I was thinking that was a problem of add-on afcad, no is also a problem of default afcad files.
BUT other add-on as fs flight tracker detect perfectly those airports so this is not an afcad files bug BUT is a FSP
wrong way to detect airports.
Obiovsly this bug must be corrected, if you don't correct this error I'll pretend that you declare that your software is not working in all MSFS airports
And be carefull, because you have not declared this before, when many people have bought your software.
I'm a bit fed up about false declarations of incoming patches I hope that last one will be sincere and definitive.
Reguards
Fabrizio Maffioletti
Post Edited ( 06-14-06 10:47 )
You can easely check this, placing the plane in those airports: FSP will put NONE or another airport in the departure airport.
I've read that is a problem of afcad files, I was thinking that was a problem of add-on afcad, no is also a problem of default afcad files.
BUT other add-on as fs flight tracker detect perfectly those airports so this is not an afcad files bug BUT is a FSP
wrong way to detect airports.
Obiovsly this bug must be corrected, if you don't correct this error I'll pretend that you declare that your software is not working in all MSFS airports
And be carefull, because you have not declared this before, when many people have bought your software.
I'm a bit fed up about false declarations of incoming patches I hope that last one will be sincere and definitive.
Reguards
Fabrizio Maffioletti
Post Edited ( 06-14-06 10:47 )