An unknown user reported issue XSG-4251: hmmmm in reference to scenery pack 57227 on December 30, 2017 1:17 AM
Closed

aggghhh wish there was anh easy way of checking for those

  • Jan Vogel December 30, 2017 5:26 AM

    Suggest to put this one up for bug report of the year - unless you guys are not taking any entries for 2017 anymore!?

  • Julian Lockwood January 2, 2018 2:49 PM

    Jan has a point Issue unspecified.

  • mjrhealth January 24, 2018 1:53 PM


    cant even remember what teh issue was

luke173 commented on May 23, 2020 8:51 AM

This airport seems to have gotten a new runway: 13/31 I have the SID & STARS (Aerosoft), but not the runway.

CatonaPC reported issue XSG-10637: YBSU significant change in reference to scenery pack 57371 on June 30, 2020 2:57 AM
Closed

Runway 18/36 decommissioned.
Runway numbers 12/30 changed to 13/31

Please note: Navigraph data has already changed to reflect this. Awaiting charge to X-Plane's default apt.dat.

  • Coxy November 3, 2020 9:06 AM


    @CatonaPC how often does the apt.dat get updated?

  • Jan Vogel March 10, 2021 8:25 AM

    I have uploaded a new version just yesterday. It will be incorporated on the next update to XPlane which also includes an “Scenery Gateway airport injection”. This will also update the apt.dat, which will in turn enable all the GPS approaches to work again. These injections happen every few months, unfortunately not more often.

  • Robert Grant June 25, 2021 5:00 AM


    As a followup to this issue. While the new runways are there it appears the default apt.dat has not updated. So whenever a SID or STAR is loaded the GPS error comes up then CTD.
    I have manually changed my default apr.dat and it works fine. The default apt.dat needs to updated and checked because it obviously didnt happen with 11.55r1 or r2.
    I have submitted my update of YBSU to correct a few things and add the new aprons taxiways and markings.

AirWombat reported issue XSG-11654: Missing runway 13/31 in reference to scenery pack 83219 on April 2, 2021 1:02 PM
Closed

The new 2800m runway 13/31 was commissioned in June 2020 and 18/36 was decommissioned. Default and addon scenery has been updated to reflect this but nav data does not know about the runway identities or associated SIDs and STARs. They correct runways/SIDs/STARs are in Resources\default data\CIFP\YBSU.dat but some other data file doesn't know about them yet so default FMS/GPS cannot load runways or procedures.

https://engage.airservicesaustralia.com/sunshine-coast-airport-airspace-changes-runway-1331
http://www.airservicesaustralia.com/aip/current/dap/BSUAD01-166_25MAR2021.pdf

  • AirWombat April 2, 2021 1:11 PM


    Correction, custom YBSU.dat (from Navigraph) has the correct runway identities but default YBSU.dat does not.

  • Jan Vogel April 2, 2021 4:15 PM

    An updated version for YBSU is uploaded and pending injection in the next scenery update to XPlane. Until then the associated approaches wont work.

CatonaPC reported issue XSG-11959: Runway renumbered and anoth... in reference to scenery pack 83219 on May 12, 2021 1:03 PM
Closed

Need to update default X-Plane apt.dat for YBSU. Contains deactivated runway and runway 12/30 which is now runway 13/31. Error causes failure to load procedures in FMC which causes X-Plane to crash.

Reported to LR but they told me to report it here. Note: Errror is not with gateway scenery; it is correct.

See http://www.airservicesaustralia.com/aip/current/dap/BSUAD01-166_25MAR2021.pdf

  • Jan Vogel May 12, 2021 4:04 PM


    Hi CatonaPC,
    this will happen when the next update to X-Plane incorporates the new (improved) airports. X-Plane should not crash, though - just report an error that the "runway could not be found".
    There is a way to update the apt.dat manually, check on community forums for help on doing that.
    Cheers, Jan

  • CatonaPC May 13, 2021 12:30 AM


    X-Plane's FMCs rely on runway data in the default apt.dat found in the Resources folder. If there is a change to the runway number (as in YBSU's case, 12 to 13), Gateway might have the change long before X-Plane's apt.dat is ever updated. So too AIRACs which update monthly.

    I temporarily updated the default apt.dat as a workaround using YBSU from the Gateway.

    LR should re-work the FMC's so that they first check the Global Airports file for runway information. That's always the most up to date information.

    Thanks for getting back to me.

    Rick

That_Bald_Gamer commented on May 31, 2021 2:06 AM

Can you guys subscribe to my YouTube channel?

My YouTube channel is That Bald Gamer

mathoes commented on July 19, 2021 1:41 PM

Does anyone by any chance have a new custom version of the default apt.dat just for YBSU? - maybe as a short term fix I could just copy and paste that into it. I don't care if it gets overridden with some update and that update doesn't actually fix the issue, then I'll just reapply the fix again.

What's the chances of living somewhere, where the only two airports I care to use are having this issue (YBBN as well with it's updates) ergh.

I am currently raising this with x-plane support and discovering all this as well, I'm surprised the fix has been so long to get a default standard update since it has been raised.

If only there were a section of these fixes for this that could be done here instead of only scenery (but I do appreciate the amazing work people put into these!) like a tab for scenery updates and a tab for rwy updates, that'll be incredible!

!!!!@#$$ reported issue XSG-15160: rwy 13 in reference to scenery pack 99715 on February 20, 2024 5:54 AM
Closed

no rwy 13 for xplane11 scenery

  • AirWombat February 20, 2024 6:07 AM


    13/31 has been there since pack 83219 in March 2021. It was released with X-Plane 11.55.

  • Robert Grant February 20, 2024 6:27 AM


    Im not sure if the latest update will work properly with XP11 but when I did 85131 it was for XP11.

WilburPilot reported issue XSG-15645: Still have trees all over r... in reference to scenery pack 102170 on September 15, 2024 1:34 AM
Closed

Using Australian Scenery Ortho4XP. This problem has been there for me from previous versions. Even using "native" XP12.1.1 scenery does not get rid of the problem. Do I need to create exclusions or is there a different problem?

You must be logged in to participate in the discussion