KDCA Washington National MSFS

[emersonbattle]

I'm running KDCA Washington National MSFS and Washington Landmarks v2 on MSFS 2020 and try as I might... I cannot get the default KDCA to go away. Drzewiecki Design DCA IS showing up, but the default airport is showing through as well. Does anyone know what I need to disable to fix this issue?

Thank you,
Emerson

[Martin_Starski]

Please do some basic steps as below. If it does not help, please share more info (sim & scenery version) and some screenshots.

-> Clear SceneryIndexes Cache - the simulator will rebuild the indexes automatically during the next start.
-> Set the scenery priority - the MSFS Package re-order tool can move the add-on to the highest priority, which might solve some conflicts between different add-ons (for example buildings or terrain issues).
-> Isolation of conflicting add-on - go to the 'Community' folder and move all add-ons except the one suspected conflicting one to a temporary folder. You can de-activate individual add-ons or groups of add-ons and then figure out whether the conflict is solved or not.

[emersonbattle]

Please do some basic steps as below. If it does not help, please share more info (sim & scenery version) and some screenshots.

-> Clear SceneryIndexes Cache - the simulator will rebuild the indexes automatically during the next start.
-> Set the scenery priority - the MSFS Package re-order tool can move the add-on to the highest priority, which might solve some conflicts between different add-ons (for example buildings or terrain issues).
-> Isolation of conflicting add-on - go to the 'Community' folder and move all add-ons except the one suspected conflicting one to a temporary folder. You can de-activate individual add-ons or groups of add-ons and then figure out whether the conflict is solved or not.
Top

I figured it out. I had to go even more basic than that... turns out I didn't have City Update IX installed. When reinstalling Washington Landmarks V2, it called out this, and two World Updates. I thought I had them installed, but when I verified this, I realized I had uninstalled the City update at some point. Thank you for your help nonetheless. Cheers.

[alex_saha]

Hi,

The two sets of PAPI lights are intentional and correct. If you check the official airport charts, you’ll see that each one uses a different glideslope angle.

We’ll definitely look into the crash issue you mentioned, although we haven’t been able to reproduce it during our own testing. Gates with static aircraft should not be available, so could you please confirm that you don’t have another KDCA scenery installed and let us know which specific gate(s) you’re seeing this on?

Unfortunately, static aircraft can’t be removed in the Marketplace environment. That’s also why any gates occupied by static aircraft are meant to be blocked from user and AI traffic.

[AVGA157]

Hi,

Really love this airport ... functionality and design are amazing. So glad I purchased it.

One question I have is whether AI aircraft are automatically placed on various stands and gates, even if MSFS 2024 settings have traffic off, and FSTL injector is off.

Asking because I use SayIntentions for live traffic (with all other potential sources turned off), but when I activate a flight from KDCA, there are parked aircraft that I cannot remove, resulting in planes doubling up in the same spaces when I start SI. SI customer support asked me to ask you whether the scenery itself is placing AI aircraft, as they verified it is not due to my settings.

Thank you.

Len

[DD Stanislaw]

Hi Len,

Thank you for the clarification — let’s break this down carefully.

First, regarding how this works in MSFS:

• Our scenery may include static aircraft as normal scenery objects (purely visual models).
• MSFS itself can generate parked aircraft based on its internal traffic settings.
• The airport layout (parking logic, sizes, airline codes, etc.) is what MSFS uses to determine where sim-generated aircraft can appear.

In our package:

• Stands occupied by our static models are normally excluded from active parking logic to prevent conflicts.
• If aircraft are doubling up, it usually means they are being injected by the simulator itself (or another traffic source), not by the scenery.

To identify the source:

• Please compare what you see with the official screenshots:
  https://www.drzewiecki-design.net/prodKDCA_MSFS.htm
• If the aircraft look identical to those shown there, they are our static models.
• If they are different types or liveries (generic aircraft, unexpected airlines, etc.), they are most likely MSFS-generated traffic.

In MSFS 2024, please verify:

• Options -> General Options -> Traffic
• Set Aircraft Traffic Type to Off (or do not use AI/Live modes)
• Set Ground Aircraft Density to 0
• Set AI Offline Traffic to Off
• Set Live Real-Time Traffic to Off

The most important setting for parked aircraft is:

• Ground Aircraft Density (must be set to 0)

If possible, please attach a screenshot showing the affected stands at KDCA. With that, we can immediately determine whether these are our static models or simulator-generated aircraft.

Best regards

[AVGA157]

Hi,

Thanks very much for the information. I am pretty sure what I am seeing is the static aircraft from your scenery, as I definitely have all MSFS traffic set to off -- and am not launching the FSTL injector, either. If I'm right, is there a way to tell the KDCA scenery not to deploy any static traffic as objects ... or should that not happen if MSFS traffic is set to off? It's not a huge problem if the scenery-generated static traffic can't be turned off. Just results in Say Intentions placing its live traffic (parked aircraft) on top of the scenery-generated aircraft. Would prefer to avoid this, though.

Also, with regard to MSFS 2024 settings, I believe all traffic settings are now located in the Graphics menu. They removed the separate "Traffic" menu a short while ago.

Thank you again.

Len

[DD Stanislaw]

Hi Len,

Thank you for the additional details.

First, an important clarification regarding how our airport layout works:

• Stands occupied by our static aircraft are removed from active parking logic.
• This means MSFS should not assign AI traffic to those specific stands.
• Therefore, under normal circumstances, there should be no conflict between our static models and simulator-generated traffic.

A conflict can only occur if:

• An external traffic system uses its own custom airport layout, or
• Another add-on is overriding the airport’s parking configuration.

Now regarding static aircraft removal — this depends on where the product was purchased:

MSFS – Custom Installer (external stores):

• All custom installers include an option to remove static aircraft.
• You can re-run the installer and deselect static aircraft.

MSFS – Marketplace (PC):

• Static aircraft cannot be removed due to Marketplace packaging limitations.

MSFS – Marketplace (Xbox):

• Static aircraft are not included by default.

If this was a Marketplace (PC) purchase and you would prefer a no-statics version:

• Some stores allow license transfers from Marketplace to external versions (after verification).
• In that case, you would need to contact the store directly to confirm eligibility.

Thank you again for the detailed feedback.

[Daniel Strzymiński]

Dzień dobry.
Kupiłem w ORBX lotnisko w KDCA zauważyłem, że po instalacji mam wersję 1.4.0 a u tutaj widzę że dla tego lotniska jest już wersja 1.5 Czy sklep ORBX nie zapewnia aktualizacji waszych produktów ?

[Martin_Starski]

1.5 to byla tylko aktualizacja instalatora do MSFS2024 - jeżeli Orbx daje taką możliwość instalacji, to jest to najbardziej aktualna wersja.