Washington XP
Latest version: v1.3 (2020)
- DD Stanislaw
- Administrator
- Posts: 6301
- Joined: Monday 15 May 2006, 10:07
- Name: Stanisław
- Location: Warsaw, Poland
Washington XP
Washington XP by Drzewiecki Design
More info at/Więcej na: http://www.drzewiecki-design.net/prodWash_XP.htm
More info at/Więcej na: http://www.drzewiecki-design.net/prodWash_XP.htm
- DD Stanislaw
- Administrator
- Posts: 6301
- Joined: Monday 15 May 2006, 10:07
- Name: Stanisław
- Location: Warsaw, Poland
Hi. Regarding the hills, this is wherecity flatten ends. In FSX/P3D it was possible to make an almost invisible connect between it and the mesh itself however it is not possible yet with XP available tools. Lets hope there will be more mesh-related X-Plane tools available in the future.vipers95 wrote:I am new here and this has nothing to do with Warsaw Chopin Airport.
I did purchase your Washington for XPlane today . I loaded it and if you would be so kind to look at http://forums.x-plane.org/index.php?/fo ... nt-1144948
I posted photos there and thought someone could give me an answer if I did something wrong.
Thanks.
Effects to other airports
I purchased and installed the Washington DC scenery. Everything in the scenery area seems to behave correctly, but if I have custom airports outside of the area, it seems to create a double scenery.
Phil
- DD Stanislaw
- Administrator
- Posts: 6301
- Joined: Monday 15 May 2006, 10:07
- Name: Stanisław
- Location: Warsaw, Poland
So far it seems to be airports that are from my Custom Scenery's folder. I'm seeing both the custom and the default scenery. Specifically I've tried KMSP and KIND, both of which I had been working until today.
I did try KORD, which I don't have a custom scenery for, and it looked correct, but that may be because of only have the defaults.
I've taken a look at my scenery_packs.ini as well as the logs.txt, and nothing stands out so far.
I do have some ortho4xp generated scenery for these areas, as well as I have the entire US worth of HD Mesh v3.
Thanks for any help you can give!
[ Added: Wed Mar 29, 2017 10:08 ]
I have also now tried a couple of other airports that have worked in the recent past (couple of weeks). KDEN and KSFO both do not show custom scenery at all, even though they are loaded according to the log.
I did try KORD, which I don't have a custom scenery for, and it looked correct, but that may be because of only have the defaults.
I've taken a look at my scenery_packs.ini as well as the logs.txt, and nothing stands out so far.
I do have some ortho4xp generated scenery for these areas, as well as I have the entire US worth of HD Mesh v3.
Thanks for any help you can give!
[ Added: Wed Mar 29, 2017 10:08 ]
I have also now tried a couple of other airports that have worked in the recent past (couple of weeks). KDEN and KSFO both do not show custom scenery at all, even though they are loaded according to the log.
Phil
Same issue here for me. Happened right after installing the DC scenery. 2 flying buddies of mine that purchased and installed at the same time as me ran into the same issue. It seems that any airport in the custom scenery either doesn't appear at all or it doubles up with the default scenery. I can confirm this happening with all my MisterX6 scenery for sure (KBOS, KLAX, KSAN, KSFO, KPDX, KPHX).
PJ Pilot and I were also discussing this briefly over on the x-plane.org forums. Deleting the scenery_packs.ini and letting it rebuild itself solved the problem for me, but did not work for him. It would appear that the global airports are loading on top of the custom airports, even though the scenery_packs.ini says otherwise.
Overall, a great looking product though! Great job!
PJ Pilot and I were also discussing this briefly over on the x-plane.org forums. Deleting the scenery_packs.ini and letting it rebuild itself solved the problem for me, but did not work for him. It would appear that the global airports are loading on top of the custom airports, even though the scenery_packs.ini says otherwise.
Overall, a great looking product though! Great job!
After a bunch of restarts and tinkering, I have a possible solution. I modified the order of the scenery_packs so the Global Airports is below all of the other custom airports.
I don't remember ever having to make this modification before, but it does make some sense. The only airport that I tried before that worked was KDCA, which in the new Washington XP pack is prefixed with 'DD', putting it before the Global Airports.
I don't remember ever having to make this modification before, but it does make some sense. The only airport that I tried before that worked was KDCA, which in the new Washington XP pack is prefixed with 'DD', putting it before the Global Airports.
Phil
Rough Runways at KDCA
I am having an issue where the runways and taxiways at KDCA are rough. You can see the asphalt pavement but when you taxi, take off, or land, the aircraft bounces and is loud like when you land on a grass strip or you run off the runway.
I tried everything I can think of, re-arranging of the scenery_packs.ini file, and re-installing the Washington XP scenery (including complete removal and re-downloading the installer file).
Am I missing something?
Thanks team!
I tried everything I can think of, re-arranging of the scenery_packs.ini file, and re-installing the Washington XP scenery (including complete removal and re-downloading the installer file).
Am I missing something?
Thanks team!
Re: Rough Runways at KDCA
I acknowledge this error. Today-Tomorrow will be fixed!nmcgee wrote:I am having an issue where the runways and taxiways at KDCA are rough. You can see the asphalt pavement but when you taxi, take off, or land, the aircraft bounces and is loud like when you land on a grass strip or you run off the runway.
I tried everything I can think of, re-arranging of the scenery_packs.ini file, and re-installing the Washington XP scenery (including complete removal and re-downloading the installer file).
Am I missing something?
Thanks team!
[ Added: Sun Apr 02, 2017 15:50 ]
Fixed! Please confirm that!
For instal extract archive to Custom Scenery with replace!
https://drive.google.com/file/d/0BxQMlD ... sp=sharing
Re: Rough Runways at KDCA
Moter wrote:I acknowledge this error. Today-Tomorrow will be fixed!nmcgee wrote:I am having an issue where the runways and taxiways at KDCA are rough. You can see the asphalt pavement but when you taxi, take off, or land, the aircraft bounces and is loud like when you land on a grass strip or you run off the runway.
I tried everything I can think of, re-arranging of the scenery_packs.ini file, and re-installing the Washington XP scenery (including complete removal and re-downloading the installer file).
Am I missing something?
Thanks team!
[ Added: Sun Apr 02, 2017 15:50 ]
Fixed! Please confirm that!
For instal extract archive to Custom Scenery with replace!
https://drive.google.com/file/d/0BxQMlD ... sp=sharing
That worked! Beautiful scenery! Thanks so much! I love this scenery. So much hard work and detail went into the Washington DC area and no frame rate drops!
-
- 2-4 posts
- Posts: 2
- Joined: Sunday 02 Apr 2017, 21:00
- Location: South Africa
Hi, I purchased Washington XP today and installed to XP11 as instructed. There is a problem with DD Washington XP Layer 2 loading. It seems to be missing some object files that it references.
Here is the relevant part of my log file. Your input is appreciated. Thanks!
0:01:52.158 I/SCN: DSF load time: 38757 for file Custom Scenery/DD Washington XP Layer1/Earth nav data/+30-080/+38-078.dsf (0 tris)
0:01:52.158 E/SCN: Failed to find resource 'objects/2c22933b444f3bb807b49a8d836497c6-DCA_term2.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/2c22933b444f3bb807b49a8d836497c6-DCA_term2.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/Hmil1_GND-Wash_Hmil.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/Hmil1_GND-Wash_Hmil.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/Hmil1_GND-Wash_Hmil-1.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/Hmil1_GND-Wash_Hmil-1.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/Hmil1_GND-Wash_Hmil-2.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/Hmil1_GND-Wash_Hmil-2.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/Hmil1_GND-Wash_Hmil-3.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/Hmil1_GND-Wash_Hmil-3.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/2c22933b444f3bb807b49a8d836497c6-DCA.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/2c22933b444f3bb807b49a8d836497c6-DCA.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/2c22933b444f3bb807b49a8d836497c6-DCA_term_glass.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/2c22933b444f3bb807b49a8d836497c6-DCA_term_glass.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/2c22933b444f3bb807b49a8d836497c6-DCA1.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
Here is the relevant part of my log file. Your input is appreciated. Thanks!
0:01:52.158 I/SCN: DSF load time: 38757 for file Custom Scenery/DD Washington XP Layer1/Earth nav data/+30-080/+38-078.dsf (0 tris)
0:01:52.158 E/SCN: Failed to find resource 'objects/2c22933b444f3bb807b49a8d836497c6-DCA_term2.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/2c22933b444f3bb807b49a8d836497c6-DCA_term2.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/Hmil1_GND-Wash_Hmil.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/Hmil1_GND-Wash_Hmil.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/Hmil1_GND-Wash_Hmil-1.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/Hmil1_GND-Wash_Hmil-1.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/Hmil1_GND-Wash_Hmil-2.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/Hmil1_GND-Wash_Hmil-2.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/Hmil1_GND-Wash_Hmil-3.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/Hmil1_GND-Wash_Hmil-3.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/2c22933b444f3bb807b49a8d836497c6-DCA.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/2c22933b444f3bb807b49a8d836497c6-DCA.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/2c22933b444f3bb807b49a8d836497c6-DCA_term_glass.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/2c22933b444f3bb807b49a8d836497c6-DCA_term_glass.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/2c22933b444f3bb807b49a8d836497c6-DCA1.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
Hmmm... very strange. Try to reinstall scenery.budgiesmith wrote:Hi, I purchased Washington XP today and installed to XP11 as instructed. There is a problem with DD Washington XP Layer 2 loading. It seems to be missing some object files that it references.
Here is the relevant part of my log file. Your input is appreciated. Thanks!
0:01:52.158 I/SCN: DSF load time: 38757 for file Custom Scenery/DD Washington XP Layer1/Earth nav data/+30-080/+38-078.dsf (0 tris)
0:01:52.158 E/SCN: Failed to find resource 'objects/2c22933b444f3bb807b49a8d836497c6-DCA_term2.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/2c22933b444f3bb807b49a8d836497c6-DCA_term2.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/Hmil1_GND-Wash_Hmil.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/Hmil1_GND-Wash_Hmil.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/Hmil1_GND-Wash_Hmil-1.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/Hmil1_GND-Wash_Hmil-1.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/Hmil1_GND-Wash_Hmil-2.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/Hmil1_GND-Wash_Hmil-2.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/Hmil1_GND-Wash_Hmil-3.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/Hmil1_GND-Wash_Hmil-3.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/2c22933b444f3bb807b49a8d836497c6-DCA.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/2c22933b444f3bb807b49a8d836497c6-DCA.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/2c22933b444f3bb807b49a8d836497c6-DCA_term_glass.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
0:01:52.158 E/SCN: Custom Scenery/DD Washington XP Layer2/Earth nav data/+30-080/+38-078.dsf:
0:01:52.158 E/SCN: Unable to locate object: objects/2c22933b444f3bb807b49a8d836497c6-DCA_term_glass.obj
0:01:52.158 E/SCN: Failed to find resource 'objects/2c22933b444f3bb807b49a8d836497c6-DCA1.obj', referenced from scenery package 'Custom Scenery/DD Washington XP Layer2/'.
-
- 2-4 posts
- Posts: 2
- Joined: Sunday 02 Apr 2017, 21:00
- Location: South Africa
Thank you for your fast reply.
OK! I reinstalled and it works now! The only difference I made was to leave no blank lines in the updated user_nav.dat file and also to also copy the 'Washington XP documents" file to my XP11 custom scenery folder. So, it must have been one or both of these changes.
The scenery is really impressive. I bought it because I spend a month a year in DC and know the city well. There is also very little effect on frame rates.
I will certainly be buying more of your products. Thank you!
OK! I reinstalled and it works now! The only difference I made was to leave no blank lines in the updated user_nav.dat file and also to also copy the 'Washington XP documents" file to my XP11 custom scenery folder. So, it must have been one or both of these changes.
The scenery is really impressive. I bought it because I spend a month a year in DC and know the city well. There is also very little effect on frame rates.
I will certainly be buying more of your products. Thank you!
-
- 5-12 posts
- Posts: 6
- Joined: Sunday 02 Apr 2017, 10:12
- Location: United States
Hello, I have looked around and cannot find anyone posting about this problem, so I hope it's okay to ask here.
I purchased and installed Washington XP two days ago, and it seemed to work fine. (I'm on Windows 10 with XP11rc1, I think.)
HOWEVER, the installer broke KDCA for all ILS approaches on RWY 01 and for the LOC approach on RWY 19. Both are failing miserably.
It turns out, even after I removed the Washington XP scenery and went back to the default airport for KDCA, this problem happened -- so at first, I thought it wasn't Drzewiecki Design's fault.
The problem was, not only didn't the LOC work correctly for horizontal navigation within ~20 nm of the runway 01, but vertical navigation via G/S never worked at all! In fact, on some places such as the x737 EADT v5, pressing the APPR button after finally getting LOC to acquire (thought it never worked right, either), the entire approach would be cancelled altogether (back to manual navigation).
After wasting a full day troubleshooting and re-downloading scenery and earth_nav data from X-Plane, I saw the problem: your Washington XP installer for Windows is adding a custom "user_nav.dat" file to the .../XPlane 11/Custom Data/ folder.
That file is somehow breaking everything! Even when not using your scenery. Because X-Plane 11 uses that as the source of truth for all navigation data when it's present. Thus, I think something is broken with your user_nav.dat file in XP11.
Once I removed your user_nav.dat file, all worked perfectly again!! Both with your scenery, and with global/default scenery.
So please:
(a) don't install a custom user_nav.dat file; you don't need to, I don't understand why you do, and
(b) at least *tell* the users you're installing it, because I was VERY confused and couldn't figure out where it came from. I certainly didn't install it intentionally.
Thanks.
Steve
I purchased and installed Washington XP two days ago, and it seemed to work fine. (I'm on Windows 10 with XP11rc1, I think.)
HOWEVER, the installer broke KDCA for all ILS approaches on RWY 01 and for the LOC approach on RWY 19. Both are failing miserably.
It turns out, even after I removed the Washington XP scenery and went back to the default airport for KDCA, this problem happened -- so at first, I thought it wasn't Drzewiecki Design's fault.
The problem was, not only didn't the LOC work correctly for horizontal navigation within ~20 nm of the runway 01, but vertical navigation via G/S never worked at all! In fact, on some places such as the x737 EADT v5, pressing the APPR button after finally getting LOC to acquire (thought it never worked right, either), the entire approach would be cancelled altogether (back to manual navigation).
After wasting a full day troubleshooting and re-downloading scenery and earth_nav data from X-Plane, I saw the problem: your Washington XP installer for Windows is adding a custom "user_nav.dat" file to the .../XPlane 11/Custom Data/ folder.
That file is somehow breaking everything! Even when not using your scenery. Because X-Plane 11 uses that as the source of truth for all navigation data when it's present. Thus, I think something is broken with your user_nav.dat file in XP11.
Once I removed your user_nav.dat file, all worked perfectly again!! Both with your scenery, and with global/default scenery.
So please:
(a) don't install a custom user_nav.dat file; you don't need to, I don't understand why you do, and
(b) at least *tell* the users you're installing it, because I was VERY confused and couldn't figure out where it came from. I certainly didn't install it intentionally.
Thanks.
Steve