Joseph...YOU ROCK!!! Your XML and instructions have save me as I spent $160 on the Logitech/Saitek Radio Panel only to find neither of them have gone to the trouble/effort to support the product on P3Dv5 and above. I am soon to also put up your fix on v6.1 and give it a try (am running both v5 and v...

FIXED in P3Dv6.1.
Am now able to use an "exclusion" rectangle to block out all default scenery items, including Taxiway signs. Tested this across multiple custom airports (mine...not 3rd party).
Thanks LM

FIXED!! in P3Dv6.1
Thank you!!!

I believe this was corrected in v6.035. I have experienced the problem you described prior to v6.035, reported same here and once the current release came out, both my "stock" and my "custom" airports have PAPI that are very visable. The Red and the White have been significantly ...

I totally agree! As for me, I continue to use the latest version of ADE, but point it to the P3Dv6 compiler and then recompile the v5 AD4. I have installed two(2) separate copies of ADE. The key is when installing a 2nd copy of ADE, do not configure it's MSFS folder where v5 is pointed to. I probabl...

The latest HF, with only a couple of exceptions, fixes the bleedthru of stock objects into custom. I only use ADE and as there are significant changes in v6 and the fact that Jon (Scruffyduck) has taken a well earned retirement. Some ADE functions have a problem with v6, but I feel its still the ver...

None that I know of. I have created it in v5 because the stock is very incorrect and moved it to v6 (for the same reason) with a full recompile.
Most willing to share, if it will help.

I believe if you get much closer and watch it rotate you will see it shine on the ground. From a distance is looks fine, but that because of the brightness. The actual "beam" for each light hits the ground around the tower it is installed on.

As of the latest HF, KBMQ remains incorrect as there are several items that bleed thru from the Stock Airport. I have attached (2) pics showing an incorrect Runway sign on the A1 taxiway. This runway sign is not formated as other taxiway signs in v6 (aka: on a cement platform and on legs). In anothe...

Default effects for the rotating airport beacon are incorrect (carryover from P3Dv5 and before). The default settings cause the light to shine on the ground around the beacon itself. The default MDL is located in "\Program Files\Lockheed Martin\Prepar3D v6\Scenery\Global\scenery\airport_objects...

Stock Airport Taxiway signage is not removable and is no longer "directly/evident" in the Stock BGL. These simply clutter airports that are enabled in the scenery library. The same is true of many STOCK Buildings that overlay or are additional when running a custom scenery (scenery library...

In v6, for any add-on airports (configured into the Scenery Lib), taxiway signs from the associated P3Dv6 stock airport overlay the airport configured in the scenery library. In most all cases, these taxiway signs are also incorrectly placed as the longitude/Latitude as well as the actual taxiway wi...

The current (and prior SDK versions) have a limit set of 256 aprons per airport. This has now become a problem as many large airports (KATL, KDFW, KSEA, etc.) exceed this limitation.
Can this limit be changed? (increased to maybe 512)
Thank you

Both runways at KAUS are incorrect. They are listed as 35L/35R and 17L/17R. The correct rwy designations are 36L/36R and 18L/18R.
All associated taxiway signage for these runways are also incorrect.

Vaughan, did you click on the link I placed in my earlier post? I just tried it and it worked. It does NOT however place the image in this reply chain, it simply allows you to download it to your local machine for viewing. I will try the other 2 methods that you suggested as well.
Thank you.