Again wrong destination

[DanSteph]

fabrytnix wrote:
If you won't use the word "bug" I'll use" wrong analysis".

I'll welcome with pleasure any degree you have in programming and MSFS mastering
to juge this.

fabrytnix wrote:
The philosophy of your sofware has a basical concept, the arcade event begins from A and ends at B.
If A or B are not correctly detected, all fall down.

Howe much flights do you flown how much wrong dest did you get ? if you don't use airport "penalty"
wich is optionnal nothing fall down.

fabrytnix wrote:
You have a wrong way to detect airports, this way doesn't certify that dep or dest are correctly detected.
You must correct this analysis error, because there is a way to detect dep and/or dest. without probability. of error.

probably it work on 97% of 30'000 airports of MSFS doesn't seem too bad for a wrong way
also getting detection that count for point in report is optionnal.

fabrytnix wrote:
I see, for instance, 2 solutons:
build a database of airports coords (DAFIF has it already builded)

And ? what if two airports are close wich is the source of error with GPS ?
Same problem... if at landing you're closer from the center of a small airport
near the one you intended to land you'll have exactly the same issue.

fabrytnix wrote:
manage a gap from those coords (verified in beta test) with a parameter value, put that value in more_option, so people can manage it if
lt like Make a documentation that it explains how to change those coords if some scenery is wrong

if they are exported "as they are" with a utility you're back to problem #1.
I hope you don't expect us to test the 30'000 airport one by one ?
Solution is to eliminate small airport in this case those airport would
not be detected at all.

I tested VABB and WSSS by a strange coincidence there is a small airport really
close to them wich is exactly the problem we try to explain to you since the start.


Dan