KDCA Washington National MSFS

[Gollum65]

No response from pcaviator and 1.4 is still the newest version available on their site.

[Martin_Starski]

Unfortunately, we don't get any response either. I've just sent the reminder.

[Gollum65]

I think it's becoming clear that pcaviator isn't going to do anything about this. They haven't responded to either of us or updated their website. I suspect it may be a dead site running on autopilot. I'd really like to fly Washington National again. As I've stated previously I'm happy to provide proof of purchase. What can we do at this point?

[Martin_Starski]

Please follow this procedure - viewtopic.php?t=422 - but I'm not sure if we can use it for the store, which is still active.

[noahharget]

any update on a fix to this issue? It is still very much occurring in MSFS 2020

I have uninstalled DD KDCA to trace down which update may have broken the scenery, here are notes from various installs. If this is an Asobo issue, I am unsure of how to have it handled But, with some pointers I'll submit to the appropriate channels. I own the products through Orbx, which is showing v1.4, not v1.5 as others have mentioned. I am using MSFS 2020, so I am unsure if this issue is present in 2024.

Default MSFS 2020 Scenery
Issue does not occur in default scenery

Default KDCA w/ Landmarks v1 Installed
Issue does not occur

Default KDCA w/ Landmarks v2 Installed
Issue DOES occur. Attempting a fix with Landmarks V2 to be higher priority.
High priority Landmarks v2 does not fix the issue.

DD KDCA w/Landmarks uninstalled
Issue does not occur

DD KDCA w/Landmarks v1 Installed
Issue does not occur

DD KDCA w/Landmarks v2 Installed
Where I first noticed the issue yesterday, so that one is confirmed.

Here is a link to some photos that I cannot upload here that show the issue points. Click the info button as I have added descriptions.
https://photos.app.goo.gl/XCytuh9Ck7shQM3TA

CONCLUSION --- Landmarks v2 may or may not be the issue in conjunction with Asobo updates. I have all current World & City updates installed as required. Although there was a minor update yesterday when I started the sim, and that is when this started, so I do believe the recent updates may have contributed to this issue. If y'all could look into this before I submit something to Asobo, it would be so appreciated.

Will just continue to use Landmarks v1 until this is resolved