Good afternoon,

 

I've been doing some work on my local airport for eventual inclusion in the master XP10 airport database. I've used only WED and the included object libraries to outfit a far more reasonable facsimile of T.F. Green Airport (KPVD) in Warwick, RI.

 

I need another set of eyes to check my work to make sure I'm following most X-Plane protocols and best practices for design. I'm pretty sure I've followed most reasonable and known steps, but since I'm brand new to this, I'm seeking some assistance. Knowledge of the airport itself isn't necessary - just knowledge of how an airport in X-Plane should look.

 

This requires X-Plane 10.10, as I used some of the new facade and library elements.

 

Here's the download link to fetch the ZIP with the scenery directory enclosed.

 

Your input is appreciated!

-Greg

It looks very good, you just need to work some on your Bezier (sp?) curves. It's actually not that hard here is a link to a set of video tutorials some guy did on how to quickly make nice curves. http://www.fbachian.com/xplane/

 

I recommend watching video3.mp4

 

Although the videos are in Portuguese (a language I don't speak), it's still fairly easy to follow along to get the gist of how to use the control points to create curves.

 

-CR

Hey C, great links, bookmarked!

I think I have a handle (*no pun intended) on the control points... I'm just not going to sit there and futz with them ad infinitum to achieve perfect symmetry at all junctions and intersections. One could be there for hours doing just that!

 

From a layout perspective, does it seem suitable, or are there any glaring omissions or items which I didn't take into consideration?

 

(Still working on the objects - locations, suitability, etc. etc.)

 

Thanks for the video links - I'll just mute it and see what it shows me...

-Greg

PM me if you want 3D modelling tips.

Thanks for the offer, but not just yet. :)

 

I'm aiming to make sure that anything and everything I create can be put into Robin's database, and thus into the native XP10 package. Custom buildings, like 3rd party libraries, are not allowed.

 

Down the road perhaps I'll dabble into some modeling, but for now, I need to bring my local airports up to a greater standard than the synthetically generated taxiways and such which they have now, and why not contribute the improvements for everyone to enjoy!

 

Cheers!

-Greg

Custom buildings, like 3rd party libraries, are not allowed!

 

I'm not sure I quite catch that, so just out out of curiosity...

 

"All data must be obtained from publicly available, freely redistributable sources. I cannot accept data extracted from commercially distributed database. If you are enhancing data previously submitted by another user then please obtain their permission first." - cited Robin Peel's X-Plane site.

 

...I take it libraries like OpenSceneryX is allowed (GPL), as with relevant other 3D freeware (?). Or are you referring to something ells when you speak of the "native xp10 package" ?

 

- Z.

Hmm ... there sees to be a misunderstanding here.

 

...I take it libraries like OpenSceneryX is allowed (GPL), as with relevant other 3D freeware (?). Or are you referring to something ells when you speak of the "native xp10 package" ?

 

Robin Peel is the current maintainer of the X-Plane/Flightgear Airport database. At this moment Robin is only collecting Airport layouts (taxiways & runways only) submitted to him by email. Almost all airport layout submission is fine, just as long as you didn't directly extract it from a commercial source, and to do that would require some programming knowledge. SO don't worry about the clause, it will not apply to 99% of people submitting airport layouts made in WED.

 

What Greg and I were discussing was that eventually (probably within the next several months), Robin is going to start accepting the rest of the airport scenery (the terminals, other buildings). BUT there is a catch, he will only be accepting airport scenery made strictly from just Laminar's default art assets. Airports scenery containing objects/facades from libraries such as OpenSceneryX will not be accepted.

Ok, thanks.

 

And from my experience of at least three misplaced heliports - as of the latest apt.dat and providing those areas counts as part of the "layouts" - it apparently seems needed. Otherwise I take it it's perhaps better to turn to the (freeware) community with such corrections - should you also happen to exceed that scope in the creative process. In terms of airport/area correction Robin will probably to 99% - and increasing - find what he needs there anyway (?). Though, If it's just the "layouts" (the "data") he's after then any "container" of it shouldn't really matter, should it? Well, whether GPL are behind his limits or not, the way I see it, it's just a matter of difference in contribution. No sweat.