you will find a near-infinite number of airports in X-Plane with this "problem" - the sole reason is that X-Plane requires a "Tower" to have AI aircraft working. So users (this one here is guilty for it as well) have simply made up a tower frequency to enable AI traffic at airports.
So yeah, one could argue that this is a bug - or a workaround for a bug/limitation (no AI at non-towered aircraft).
I gotta start by saying I'm in awe of this build and BruceBuilds skills. Having built exactly one airport so far with nothing more than a single grass runway, I can appreciate all of the work that has gone into this one. Still, I noticed something, so I thought I'd bring it up in case it is a quick fix (and you deem it worth undertaking).
I was using WEDbot's 6-year-old stock build that rolled out with 11.41r1 and on a night flight, I rolled out onto 32 after having been cleared on 35. There really wasn't any signage on the WEDbot version, so I was hopeful a newer version would have better signage.
At the south end of runway 35 of scenery ID 75812, the signs on either side (see snapshots) seem to indicate that runway 14 is nearby, when really the start is for runway 32, not its reciprocal.
There also appear to be two signs right next to each other (though maybe this has to do with my install, as I just dragged the folder into the Custom Scenery folder and restarted).
Again, really great work - this is a TOTAL nitpick.
I checked out the latest KSLC version of BruceBuilds to salvage it so it can be accepted on the Gateway. Unfortunately it has too many errors for me to fix quickly, the runway sign you mention is just the tip of the iceberg. Just fixing the - ahem - very creative use of taxiway centerline lighting would take me a good day. As an airline pilot I can not bring myself to submit totally made up colour code and flashing lights options. It needs a bit of aviation convention logic knowledge to make realistic airports, unfortunately.
So until I or someone else has the time to fix this, it will have to sit on the Gateway unaccepted.
andrewnasson
commented
in reference to scenery pack
75812on April 28, 2020 9:07 PM
Going to look at working on the AI Aircraft routes. No download button though so I'm not sure how to get the most up to date airport?
flying the RUGGD1 SID out of SLC today I saw some odd mountain feature. I think its the sim trying to draw the peak in the wasatch mts. if you fly the SID from HERTS to PERTY you can't miss it. log and scn.ini attached with some screenshots.
Hard to tell without a screenshot - but most likely a small airport in the mountains that was uploaded with the “always flatten” switch ON and a wrong MSL elevation. The simulator will then create a plateau to accomodate that.
Folks, I'm doing ATC Taxing for this Airport, but in the process, I'm making list of suggestions to make this process more user-friendly to artists. See Attachment.
To make sure I'm using the proper moderator-accepted terminology, are the ATX taxiing segments in the capture ID'ed with an "N" called nodes (or otherwise)? If so, then what are their connecting end points called? Would appreciate an email reply so I can submit my list of suggestions. Thanks, Bruceflys77@yahoo.com
Julian,
Your link above did not load in YouTube. Please try again.
Also, I need to know how to repair RWY connection Out of Bounds errors. The problem is the error only lights up a node end point, but not the node segment. Therefore, the artist does not know which node section needs fixing the ones on the RWY of the taxiway connection. This will be part of my report. The Gateway will not allow me to submit KSLC without fixing these validation errors. Otherwise, the build appears okay.
FAA Charts say there is no tower (ATC) at this facility. XP-11.10 says it has tower and ground ATC. Skyvector listing and WED screenshots attached.
Jan Vogel January 18, 2018 12:22 PM
Hi Matt,
you will find a near-infinite number of airports in X-Plane with this "problem" - the sole reason is that X-Plane requires a "Tower" to have AI aircraft working. So users (this one here is guilty for it as well) have simply made up a tower frequency to enable AI traffic at airports.
So yeah, one could argue that this is a bug - or a workaround for a bug/limitation (no AI at non-towered aircraft).
Cheers, Jan
XP11.11r2 - The RNAV RWY 35 approach is not aligned with the actual runway, has you aligned to the right over the airport buildings.
I gotta start by saying I'm in awe of this build and BruceBuilds skills. Having built exactly one airport so far with nothing more than a single grass runway, I can appreciate all of the work that has gone into this one. Still, I noticed something, so I thought I'd bring it up in case it is a quick fix (and you deem it worth undertaking).
I was using WEDbot's 6-year-old stock build that rolled out with 11.41r1 and on a night flight, I rolled out onto 32 after having been cleared on 35. There really wasn't any signage on the WEDbot version, so I was hopeful a newer version would have better signage.
At the south end of runway 35 of scenery ID 75812, the signs on either side (see snapshots) seem to indicate that runway 14 is nearby, when really the start is for runway 32, not its reciprocal.
There also appear to be two signs right next to each other (though maybe this has to do with my install, as I just dragged the folder into the Custom Scenery folder and restarted).
Again, really great work - this is a TOTAL nitpick.
Jan Vogel March 8, 2021 8:49 AM
I checked out the latest KSLC version of BruceBuilds to salvage it so it can be accepted on the Gateway. Unfortunately it has too many errors for me to fix quickly, the runway sign you mention is just the tip of the iceberg. Just fixing the - ahem - very creative use of taxiway centerline lighting would take me a good day. As an airline pilot I can not bring myself to submit totally made up colour code and flashing lights options. It needs a bit of aviation convention logic knowledge to make realistic airports, unfortunately.
So until I or someone else has the time to fix this, it will have to sit on the Gateway unaccepted.
Going to look at working on the AI Aircraft routes. No download button though so I'm not sure how to get the most up to date airport?
flying the RUGGD1 SID out of SLC today I saw some odd mountain feature. I think its the sim trying to draw the peak in the wasatch mts. if you fly the SID from HERTS to PERTY you can't miss it. log and scn.ini attached with some screenshots.
Jan Vogel May 9, 2020 5:29 AM
Hard to tell without a screenshot - but most likely a small airport in the mountains that was uploaded with the “always flatten” switch ON and a wrong MSL elevation. The simulator will then create a plateau to accomodate that.
jkennebeck May 29, 2020 5:38 PM
screenshot here
Jan Vogel March 9, 2021 8:34 AM
Never was able to see the screenshot here - I believe that future upgrading to the scenery (mesh) will fix these type of issues.
There is a 14,600 foot tall pinnacle where none exists approximately 50 nautical miles east of Salt Lake City.
See attached
Jan Vogel March 11, 2021 2:39 PM
This spike seems to be a data problem with the default mesh. It is located at 40.759 -110.70.
Hopefully new mesh data in the next Xplane version will fix this.
Folks, I'm doing ATC Taxing for this Airport, but in the process, I'm making list of suggestions to make this process more user-friendly to artists. See Attachment.
To make sure I'm using the proper moderator-accepted terminology, are the ATX taxiing segments in the capture ID'ed with an "N" called nodes (or otherwise)? If so, then what are their connecting end points called? Would appreciate an email reply so I can submit my list of suggestions. Thanks, Bruceflys77@yahoo.com
Julian Lockwood October 19, 2020 5:00 PM
See: https://www.youtube.com/playlist?list=PLGRsg_6rB1D4vm0UHvHm6J-rvIyUBGN_K
R Erwin October 19, 2020 6:22 PM
Julian,
Your link above did not load in YouTube. Please try again.
Also, I need to know how to repair RWY connection Out of Bounds errors. The problem is the error only lights up a node end point, but not the node segment. Therefore, the artist does not know which node section needs fixing the ones on the RWY of the taxiway connection. This will be part of my report. The Gateway will not allow me to submit KSLC without fixing these validation errors. Otherwise, the build appears okay.
R Erwin October 19, 2020 6:23 PM
Typo correction to the above: ...RWY or the taxiway connection.
Airport is in dire need of an overhaul. New terminal layout for one.
I saw that the pack was updated for XP12 recently. but is the current pack also still compatible with XP11
NO ILS AVIALABLE AT KSLC TUNED RADIO NEVER RECIEVED LOOKED AT INSTRUCTORS STATION AT LOW IFR NO ILS AVAILABLE AT KSLC
Jan Vogel October 4, 2023 6:51 AM
Tested at KSLC, ILS visible and working.