Taxi instructions with third party airports

I purchase great-looking third-party airports that someone took a lot of time and effort on. The letdown comes when you go to taxi, and ATC can’t give you taxi instructions because the scenery wasn’t programmed with the data. How accurate is the experience when you don’t have taxi instructions? I don’t know where the shortcoming comes from. The developers lack of knowledge, or the developers think the airport is done when the scenery is done. Would you please let me know?

Might be worth mentioning which scenery. Does the scenery developer have a website or a support forum that you can go to? I have a few payware airports as well that look really good but have terribly afcads.

Two airports:

KLGB
PAUN

KLGB:

HOMEPAGE: http://www.skyline-simulations.com
SUPPORT: info@skyline-simulations.com

PAUN:

HOMEPAGE: http://realworldscenery.com
SUPPORT: realworldscenery@outlook.com

The problem is I shouldn’t have to contact developers. A Proper afcad with your airport should be a standard and not something you must beg the Developer to add. Afcad is not something you can see before you buy the airport. Taxi instruction is just as crucial to realism as night lighting.

1 Like

I hear you… about the only thing we can do as end users is reach out to them and let them know what’s going on. I stick with just 4 developers for airports and tend to stay away from others but even the ones I buy from can have an issue here and there.

1 Like

Happens with freeware too, I’ve been trying to work out why. Do those airfields share a ground & tower frequency?