Users will have to do this then with FSDT FlightBeam and MK Studios airports could be more to come.
There's nothing you should do with our AFCADs. We updated them all ( I think the only one still left to do is KFLL ), and they work perfectly as they are in both V4 and V5.
This because, since we use GSX Jetways, we don't need "micro-exclude" anymore, because the one and only reason to use micro-exclude, was due to a BUG that caused *standard* jetways to be Excluded even in the same scenery area, instead of only in the layers below as it should be. Because of this bug, developers had to come up with the micro-exclude method, which was cumbersome and caused lots problems if there was another non-default scenery below for the same airport, but it was the only way when using standard jetways.
But since we now use GSX L2 jetways for all our sceneries ( some still weren't until very recently, like the Hawaiian airports, which we just updated ), the micro exclude method is no longer required, so we now use normal "big" excludes, which are:
- faster for the sim to process ( way less areas instead of many small ones )
- more resilient to bleed-through from other non-default sceneries in the area
- don't require to provide different AFCAD for P3D V4 and V5 *just* because they neeed to micro-exclude different versions of the default underlying airport.
That's why we CAN ( and it's the proper choice ) supply with the same AFCAD that works with V4 and V5: we don't need different micro-excludes for each sim, because we use GSX jetways.
If an airport doesn't require 8.33 frequency separation and doesn't have Sloped runways ( which come with a cost in performance ), there's no need to create a "V5" AFCAD, once you solved the exclude problem, which we surely have.
Yes, of course, if you want to MODIFY our AFCAD, then you must know how to use ADE, but it's not required at all, unless you want to change parking assignments for AI.
