I am with you there, sir! If I may rephrase it: Are WE the only ones? 🙂

Blessings, Patrick

I try to review almost every apt.dat update in the sim before I publish the data. Usually I just find minor ‘quality’ issues (which helps me maintain a subjective grading for each regular submitter!). It’s rare for me to totally reject a submission – if so, it’s usually because multiple users chose to work on the same airport in the same month. I spend more time correcting nav-aid irregularities (eg. mis-aligned ILSs) than apt.dat issues.

If we add objects to this mix, then the review process will become more complex & subjective. There may be no single ‘best’ version of an airport (eg. do you want lots of detail … or higher frame rate?).

Now an off-topic wish:
Am I the only one that is lacking a follow-me car in front of the plane helping me to find the correct gate and ground personnel helping me parking correctly the plane at gate?

Unknown. Probably an additional off-screen light to the left, but I don’t know for sure.

I thought it was because you were under the impression you were piloting a Cessna 172 (check out the screenshot filename). 😮

Re: coordination mechanisms for sharing 3-d ‘stuff’: we don’t know yet. At this point my main focus is on having a system _capable_ of sharing. Once we ship such a system, we’ll work out the logistics of actual sharing.

Naively, it seems to me that with proper automation, the act of vetting could be distributed even more easily than the act of creation. That is – what we need is a relatively automated way for users to submit a problem ticket for a given version of an airport.

Hi Ben,
Will there be any sort of vetting of these user submisions to the communal airport buildings resource? I can’t imagine Robin has the time to inspect all the apt-dat submissions too closely but there is at least the expectation that the submitter has used the 2d layout of the airport chart or aerial pcitures as reference. But plonking down 3d buildings has alot more scope for users to submit junk or outright fictional representations. At least now, with distribution as distinct scenery packages, the end-user has the option to pick and choose what to install but a global apt3d.dat (or whatever) doesn’t offer that choice.

Will there be a seperate exclusion type for these airport buildings or will the obj-exclusion handle these too?