Closed Honu4 closed 3 years ago
To add a little background, I think https://github.com/Portree-Kid/groundnet_checker/issues/1 has a lot to do with this but v0.20 doesn't show the circle so it's difficult to see the radius intersecting.
this is why i had so many KCLT uploads today...
Most Auto Tests are missing from v0.20. Please Hold on to your submissions and spend more time on testing your work directly in Flightgear
speaking for myself: i've been testing mine since before i first wrote an issue saying that i was working on them... i've been working on KRDU for a few years and am still not happy with it but i'm getting there... i haven't listed it, yet, though...
i don't know how you got all those craft at KCLT and/or KCHS to go off across the grass but whoa... it might have had something to do with my attempts to make travis happy... that was my main goal at the time, anyway... once travis is happy with the file and the groundnet/groundweb is in place, then i can clean it up a more as needed...
Satisfying Travis tests is not an indication your groundnet will be functional (but opposite is true) Only your own extensive testing in real conditions can achieve that. Refer to : https://github.com/terrasync/main/issues/414
Moving to Travis Test
Groundnet Test now matches in V1.14
Check results show no errors. But pull request check finds overlapping parking positions.
Is it possible to have FG-airports check the same radius as GroundNetTest.testIntersectingParking in the pull request check?