V6.035 Some airport objects can't be deleted

[mpni]

Hi LM
Using ADE, some airport objects can't be deleted in v6.035.
For example with the PAPI. For deleting the PAPI it is necessary to deseable the PAPI in the runway.
But, If you want having the light without the boxes, an general exclude have no effect.
Same with the approach ramp, flashlight at the beginning of the runway, ...
This is a problem for two reasons:
- impossible to use personnal boxes.
- on a slopped runway, the boxes are not at the ground surface but at the runway altitude.
Regards
Michel

[mpni]

https://royalefrenchnavy.restauravia.fr ... 6/PAPI.jpg
https://royalefrenchnavy.restauravia.fr ... v6/RWY.jpg

[Clifton Crane]

Hi Michel,

The new lighting system does not use the exclusion system. Instead, there is a VisualModelBinding element to configure which models are used for the Airport. This can also be used to disable a light's model:

https://prepar3d.com/SDKv6/sdk/world/sc ... delBinding

There can be more than one <VisualModelBinding> within the <Airport> element. If a light fixture is disabled, it will fallback to the legacy sprite based placement.

Hope this helps.

Regards,
Clifton

[mpni]

Hi Clifton
Your answer helped me perfectly.
If I modify a GUID in AirportVisuals.xml, all terrains are affected by the model change.
But if I add :
<VisualModelBinding
type="VASI"
name="54892084-eab2-4e2d-a010-04a27348c88f"/>
in the <airport> section of the airport afcad xml, only this airport is affected by the model change.
This is exactly what I wanted, but I think I will keep your VASI models which are better than mine that I used for v4 and v5.
However, I will have to adjust the slope of the terrain so as not to have holes or bumps where the boxes are located.
Thank you again for your response.
Regards
Michel