terraGIT/Objects is terrasync objects(date?) + project3000(version 11/2015)
No. That's not how it works.terraGIT/Objects contains multiple sources of files
see the readme:
https://github.com/FGMEMBERS-TERRAGIT/e ... /README.mdthe objects can be
1) Project3000 --now last version you gave me in tgz as here:
https://github.com/FGMEMBERS-SCENERY/Project30002) terrasync objects -- currently updated to Dec 08/2016
3) Objects from customs Scenery packages in FGMEMBERS-SCENERY
(not all imported yet, but working on doing them one at a time)
In general several of these packages have already been imported to terraGIT, and do not have similar content in terrasync
this includes both static objects as well as shared objects worldwide
4) JMaverick AirBase Shared objects and its locations worlwide
5) Objects that I build and I add directly to terraGIT. I don't bother anymore to beg the terrasync gatekeepers to accept my contributions.
6) Objects other build and send pull requests to terraGIT for inclusion. I dont' care if these are not distributed anywhere else. More importantly contribute objects individually and massively to terraGIT is much easier than filling the terrasync form and our requirements for inclusion are no way near that stringent either. Example: we allow shared textures, baking maps, larger textures, multiples objects per ac file (like multiple buildings in a larger ac) etc.
(if it works for FG it works for terraGIT)
Not related to Object path
7) The "Airports" directory has a few dozen changes of mine, and thousands of changes of P3000 now as well)
8) The Terrain directory is now a complete new rebuild
9) I am finishing details to include a NavData/apt.dat configuration to perfectly matches the available airport layouts build
10) I am working on terrain v2.5 to get rid of the nasty bugs that v2.3 has
That, I think sums it up
So basically everyone thinking that the objects or terraGIT are only those in terrasync + Project 3000 is heavily confused.