search

Portree-Kid / flightgear-airports

GNU General Public License v3.0
6 stars 1 forks source link

v0.0.33 Missing Pushback Routes #143

Open BecOzIcan opened 3 years ago

BecOzIcan commented 3 years ago

At UUEE, 4th cycle of testing ie Groundnet has been updated, checked, exported and run in FG multiple times

Noticed AI Aircrafts parking ahead of their designated position which is known signal the parking postion does not have any pushback route (known Traffic Manager Issue)

image

image

Parking Position 109 and 110 have pushback routes in FGA, ending respectively on nodes 870 and 873

image

The groundnet XML [parking] tags confirms the relationship between parking positions and final nodes in pushback routes

image

The groundnet XML [arcs] tags does not have any matching arc nor any node ID larger than 869

image

Using Search for find node 873, FGA hangs

On forced shutdown / restart and a new cycle of of Save / Check / Close-Save, the nodes are suddenly renumbered .... The routes now end on 861 and 864

image

Looking at the updated XML, the lat/lon of any of the points above has not changed (aside from the decimal precision, shorten to 4) ie only the pushback route nodes and arcs records have been updated, no node has been added to the table.

image

I had observed the same issue at EPWA (See #134 ) in v0.032. in both cases some mysterious combination of actions forced the correct renumbering of pushback routes but I can't seem to reproduce the exact sequence.

Portree-Kid commented 3 years ago

Pushbacks are always set on save. Maybe they were older ones with bugs. If you have examples it would be great

BecOzIcan commented 3 years ago

I ll see if I have the same issue with EIDW.

LGBudd commented 2 years ago

Had the related situation at KMIA using v0.0.32 where aircraft when in reverse on taxiways. Unfortunately, I have changed the rwyuse I used when this happened. Of course, there was probably a Save cycle as noted above in FGA, so the rwyuse may be totally unrelated.

BecOzIcan commented 2 years ago

Correct. the issue is with groundnet.xml not rwyuse. This means if you have not changed your groundnet since its upload, the version in terrasync contains the corrupted data.