OK, I wasn't planning on doing it right now, but it sort of grabbed me and held me.
I made an AI_ready AFCAD, placed some static planes and AI, and added a wind sock, a beacon and an NDB.
The sock confirms that there's something strange going on there about directions. The sock, a stock FS9 sock that's responsive to the wind, shows the wind blowing from the south, as it is in my default conditions, but when I go to the end of the active runway, facing almost directly into the wind, I'm on runway 35, which should be heading north, not south. Very strange!
Anyway, that's the runway I made active because the wind is south by default in my GW sim. That's because Old Rhinebeck Aerodrome, my fictional seadrome on Quabbin Reservoir, and my fictional dirt field in the open land near my home all like a south wind, so that's my default wind direction that I seldom think to change when I fly elsewhere.
The AFCAD is set up to make AI the arriving planes park facing the same direction as those already on the ramp, which meant arranging the apron routes such that the shortest route from the arrival runway has them enter their parking spaces from the proper direction. Changing the active to the reciprocal runway would mess that up. I mention that because I'm attaching a copy of the AFCAD for anyone who wants it.
The AFCAD only had the active runway; there's no deed for the others to be on it. AI planes will taxi on some segments of the inactive runways.
I have N2S's taking off and landing, plus a transient Curtiss R4C Condor and an NRAB Glenview SF-1 as static AI - they're AI planes but they never fly (unless you're up flying in GW at four o'clock in the morning on a weeknight.) There are a static J2F Duck and static SBC-4 Helldiver in NRAB Glenview livery, a static transient Lockheed RO-2, and several static N3N Yellow Perils.
The scenery is pretty complete and I didn't add much, just the beacon, wind sock and NDB. The base already has night lighting.
Here are a couple shots of the flight line: