Some airports in the philipines are updated in terraGIT
Code: Select all
git pull
install/tile e120n10
Airports
RPLI
Terrasync
TerraGIT
RPLC
Terrasync
TerraGIT
RPVM
Terrasync
TerraGIT
RPUL
[b]Terrasunk
TerraGIT
Code: Select all
git pull
install/tile e120n10
SHM wrote:See this is why the core-clowns are doing a mistake with their stupid terrasync methods!
Look how much more development would happen if its done the way terraGit does it.
Richard wrote:This is indeed a good point and would be better without the insults. The work that is going on here and in other places to improve airports is a very good thing in terms of the content.
TerraSync is not a scenery storage method it is a distribution method.
It would be very nice if terraGit supported the Terrasync protocol (via HTTP); as that would avoid having to download the whole lot and the changes could be picked up as you're flying along.
I believe changes submitted to the scenery website (except airports) will be picked up and added to TerraSync - I'm not sure if these will get pulled through into terraGit - Israel can advise us about this.
However what doesn't currently work is airport changes; and this is because this bit was never automated. There is a method for manual updates but it's quite complex to prepare the data in the right format.
Lots of this will change when Pete gets V3 finished and the entire world is regenerated from the PostGIS database - which is why it's important to submit the airport buildings (and possibly other things) to the scenery models website - there are rules for inclusion which affect the objects and texture sizes that need to be followed - which may exclude certain custom models or textures that cannot be made to fit within the rules.
Ideally to future proof any scenery development most things need to go into the scenery database as otherwise they'll be lost when the world is regenerated for V3.
Users browsing this forum: No registered users and 1 guest