I found out the hard way that it is best to break up large terminals into adjoining sections when the airport is on hilly/slopy terrain. That way the large building will conform to the ground better. Also make sure to have node 1 on the lowest part of the terrain to avoid floating.
Product= XPlane
Version= 11.3 b4
OS= Windows
Summary= KDEN Airport
Description= Before this update, the default scenery of the airport included the white capped buildings that Denver International is known for. Upon reading your update notes it state that you had updated over 1000 new airports. Eager to see DIA, I was let down to find that the main building with the white canopy's were no longer there. If you could please get on adding them back that would be great. Thank you!
Steps= -Run version 11.3 b4
-Boeing 737 Delta livery
-KDEN Airport
-Graphics high
Consents to storing personal data= Yes
Possibly the reporter had some sort of custom scenery installed that may not show anymore. The default KDEN could never have had the white “tent” roofs, they are not supported in the default Laminar library objects.
Unable to import scenery: WED stops responding when attempting to import this airport. Issue appears to be with the associated .dsf file.
System: Apple Studio M1 Max, macOS Ventura 13.3
WED version 2.5r3
I also tested by downloading the actual scenery pack. The apt.dat file imported ok, but WED froze when attempting to import the .dsf file. Same results with WED 2.4r2.
Update: I decided to let the system sit after WED went into No Response mode. After about 8 minutes it ate up all available memory to the point my entire system locked up. Rebooted and tried again with same results.
Update: Thanks Jan. I reimported KDEN from gateway via WED 2.4r3 on my Windows machine and received a message about corrupted contents being removed. I saved and reopened the package on the mac machine and all went well so far. A screenshot of the message is attached.
I would need the WED_Log.txt to do anything based on that.
At first sight it looks like a duplicate of https://x-plane.atlassian.net/browse/WED-1455, though. A fix for that will be in WED 2.5.1 next week or so.
You run the windows binary under paralles, i.e. in a VM on a M1, i.e. also involving rosetta.
This one seems to get just garbage in the file downloaded from the server. As the same windows binaries have no problems like that for that very airport running native under windows - I can just suspect its an VM issue, possibly networking related, possibly a permissions issue. But not much more I can see from the log.
In the version where you run the arm64 binary native on the M1 its as you said not getting to the point where it flushes the buffers, so the log is of little help.
But given the issues in the Log from parallels - if it gets garbage back from the gateway there as well, it wouldn’t be surprising if the file reader goes into some endless loop due to the random data it might ingest.
We do have plenty of folks running either the macOS x86 binaries or the arm64 binaries under macOS without a hitch. So I can just suggest to
try running the Apple version under rosetta, i.e. the macOS x86_64 binary.
try downloading some other airport
check that your file system is set to be case-insensitve for file names. The current WED versions still require this under OSX.
Is there anyway you can add the tents and mustache building? Pretty please!
5443322
commented
in reference to scenery pack
66838on August 26, 2024 2:49 AM
pls, remove road lamp posts on apron
aspec
commented
in reference to scenery pack
104621on November 21, 2024 5:34 PM
Some updates just for awareness:
Updated the new extended taxiway P7 texture orientation to match real world.
Didn't realize the two-way ground truck routes has trucks driving on either side of the line, so updated the route to be in the middle (on the line between the lanes).
Added a few ground objects between RWY 35L and RWY 35R.
Updated some of the taxi signs that have a rectangular base to use the terrain_FX taxi sign base.
You must be logged in to participate in the discussion
Buildings of the terminals dont follow the curve of the new terrain heights in XP 11, should be easy fix in new WED
bkeith December 27, 2016 3:04 AM
I will have to wait for that to come out to fix it.
Jan Vogel December 27, 2016 5:49 AM
I found out the hard way that it is best to break up large terminals into adjoining sections when the airport is on hilly/slopy terrain. That way the large building will conform to the ground better. Also make sure to have node 1 on the lowest part of the terrain to avoid floating.
Cheers, Jan
Michael Minnhaar December 27, 2016 12:41 PM
Yup, had to do that at VHHH a while ago, too.
Jan Vogel February 23, 2021 7:19 PM
Several updates to this airport since then - this report can be closed.
Product= XPlane
Version= 11.3 b4
OS= Windows
Summary= KDEN Airport
Description= Before this update, the default scenery of the airport included the white capped buildings that Denver International is known for. Upon reading your update notes it state that you had updated over 1000 new airports. Eager to see DIA, I was let down to find that the main building with the white canopy's were no longer there. If you could please get on adding them back that would be great. Thank you!
Steps= -Run version 11.3 b4
-Boeing 737 Delta livery
-KDEN Airport
-Graphics high
Consents to storing personal data= Yes
Jan Vogel February 28, 2021 2:29 PM
Possibly the reporter had some sort of custom scenery installed that may not show anymore. The default KDEN could never have had the white “tent” roofs, they are not supported in the default Laminar library objects.
This report can be closed.
Unable to import scenery: WED stops responding when attempting to import this airport. Issue appears to be with the associated .dsf file.
System: Apple Studio M1 Max, macOS Ventura 13.3
WED version 2.5r3
Mark Goodman February 19, 2023 1:46 AM
Installed system memory: 32 GB
Jan Vogel February 19, 2023 5:37 AM
The Scenery Gateway airport imports just fine on my side (Windows computer)
Mark Goodman February 19, 2023 6:24 AM
I also tested by downloading the actual scenery pack. The apt.dat file imported ok, but WED froze when attempting to import the .dsf file. Same results with WED 2.4r2.
Mark Goodman February 19, 2023 6:44 AM
Update: I decided to let the system sit after WED went into No Response mode. After about 8 minutes it ate up all available memory to the point my entire system locked up. Rebooted and tried again with same results.
Mark Goodman February 19, 2023 7:48 AM
Update: Thanks Jan. I reimported KDEN from gateway via WED 2.4r3 on my Windows machine and received a message about corrupted contents being removed. I saved and reopened the package on the mac machine and all went well so far. A screenshot of the message is attached.
Michael Minnhaar February 21, 2023 9:04 PM
I would need the WED_Log.txt to do anything based on that.
At first sight it looks like a duplicate of https://x-plane.atlassian.net/browse/WED-1455, though. A fix for that will be in WED 2.5.1 next week or so.
Mark Goodman February 21, 2023 10:17 PM
Here's the WED log. I had to force quit the application in order to prevent a macOS system crash due to available memory depletion.
Mark Goodman February 21, 2023 10:26 PM
Here's the WED log from WED on Windows 11.
Mark Goodman February 21, 2023 10:47 PM
Update: Sorry. I just realized WED (Win 11) was not completely shut down before attaching second log.
Mark Goodman February 21, 2023 10:47 PM
Here ist is for Win 11
Michael Minnhaar February 21, 2023 10:54 PM
So there is two separate issues:
You run the windows binary under paralles, i.e. in a VM on a M1, i.e. also involving rosetta.
This one seems to get just garbage in the file downloaded from the server. As the same windows binaries have no problems like that for that very airport running native under windows - I can just suspect its an VM issue, possibly networking related, possibly a permissions issue. But not much more I can see from the log.
In the version where you run the arm64 binary native on the M1 its as you said not getting to the point where it flushes the buffers, so the log is of little help.
But given the issues in the Log from parallels - if it gets garbage back from the gateway there as well, it wouldn’t be surprising if the file reader goes into some endless loop due to the random data it might ingest.
We do have plenty of folks running either the macOS x86 binaries or the arm64 binaries under macOS without a hitch. So I can just suggest to
Mark Goodman February 21, 2023 10:56 PM
Thanks for the followup. KDEN is the only scenery, so far, where I get this error on mac and windows. All others import without issue.
Mark Goodman February 21, 2023 11:04 PM
Here's a WED log created after importing KDEN based on 60800 scenery pack. No issues with imoporting this one one same mac.
Mark Goodman February 21, 2023 11:18 PM
Made another attempt at importing KDEN (66838) on Windows and all went well this time. Seems I had WED pointing to the wrong X-Plane folder.
Is there anyway you can add the tents and mustache building? Pretty please!
pls, remove road lamp posts on apron
Some updates just for awareness: