In 2017.2.0 nightly build as of April 20, 2017, absolutely clean install, (removed EVERYTHING from previous installs)
Airports do not render buildings, but do render numerous pointed objects with seemingly unrelated text in them.
Steps to reproduce:
Expected Result:
Airport renders on a relatively light background with buildings visible.
Actual Result:
Airport renders on a very dark background with small pointed objects scattered around, filled with text.
Expected Result:
As above.
Actual Result:
Airport renders as light green with dark bands with numerous small pointed objects.
I do not know this to be true, but I suspect that the pointed objects with the text represent either aircraft parked at what should be the terminals, terminal gates and/or jetways, or something similar. Some ofthese ogjects seem to be parked away from what would be terminals.
Previous installations showed aircraft buildings.
Additional note, According to James, there should be data saved in a FlightGear folder in the user's home directory located at %USERPROFILE%\FlightGear (C:\Users[username]\FlightGear)
In this installation, at first launch and after first run (showing aircraft on runway), this folder was not created.
As a test, I created the FlightGear folder, installed aircraft and my entire copy of Terrasync that I bought on DVD - including airports, etc. No change.
I am going to try to attach pictures of several airports and enlarged views.
Respectully submitted,
Jim "JR"
These arrows are the parking stand markers, they're a feature, not a bug :) The bug is that for many airports, rather than having useful names, they are all called 'A1111' or similar - I don't know why.
You can see these in the parking positions combo box at the bottom of the screen also.
WHat I think you might be calling the missing 'buildings' is the taxiway / pavement data, which gives the outline of the airport apron (it's not the buildings but usually the building define some edges of the pavement so your description kind of fits)
The taxiway / pavement data comes from the same source as everything else, so it's strange that it's missing. Some airports are missing that data but reinstalling should not have affected it.
The pavement rendering is tracked as [#2628]. So changing the present issue to track the many incorrect parking position identifiers that is still unresolved.
Related
Tickets: #2628
With the new WS3 scenery we can finally update our airports (and subsequently groundnets), so that should fix this issue.