• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Lost approach data and other strange things in FSX

D

duckbilled

Messages
53
Country
us-michigan
Over the past few months I have come across several anomalies that I am sure are the result of either bad add ons or my half baked modifications of add ons (or both, user error more likely). These are the results/anomalies:

1. ILS Approach data in the GPS but assigned a visual approach for an ILS RWY. Last night I was assigned the visual approach for 16L at KSEA. I am using ORBX PNW.

2. No approach data in the GPS and assigned a visual approach for a RWY that should have an ILS.

3. ATC just forgets about me. It stops vectoring me and eventually cancels my IFR flightplan. This has happened a few times but the one that sticks in my mind is being vectored over Cuba and forgotten on a approach in to FSDT's KFLL.

Clearly I have probably messed things up but I can't say that I have tried to modify every airport that I have had trouble with. When I have modified something, it was usually in AFX and it was just parking codes or wingspans. Of course, I never over wrote anything with AFX when I received their warning message about incompatible features.

Anyway, I'm going to start digging though the ADE manual again to see if I can get these things sorted out but I was wondering if someone could give me a few pointers.

I am particularly wondering if I can get the approach information back and the steps to get it done. For example, If I open up ADE_FTX_PNW_KSEA_Seattle-Tacoma_Intl and switch to approach mode, it does show the ILS runways. How do I get ATC to recognize them again?

Thanks for you help. Sorry for the long explanation.

-Jeff
 
A first check is to go into Approach Mode (Button at top right) and then Lists > Approaches. If none are listed - click the same button at top right (will now say Airport Mode). Then Tools > Load Stock Data. In the dialog check Approaches and Import. Now you should have the approach code back. How it got lost may take a bit more investigation but if you did not start with a stock airport but with an addon airport then that could cause the problem

If you have the approaches listed in the project file then we need to think further
 
Thanks for the quick response.

The approaches for KSEA are in the approach lists.

I did have Ray Smiths KSEA files installed but I removed them (three files) after installing PNW
 
BTW, I was able to import the approach data for FSDT's LAS. I'll have to test the new .bgl later to see if it came out right.

This whole quest was spawned by a discussion in the FSDT forum where I had no approach data for their new DFW after installing an alternative ADE file.

They explained that they do not include approach data in their ADE files and rely on the stock data. When an ADE bgl is modified, it will turn off the stock data resulting in no approach data. They said the workaround was to edit the .xml data - a process that I am not familiar with yet. I am hoping that I can repair some of these by just adding it back in like I did with LAS.

As for ATC not recognizing approach data when it is listed in the .bgl, I am not sure what to do. Sounds like I need to do something with the .xml data? If so, is there a tutorial somewhere?
 
If the approaches are listed in the project file then ADE will compile them. If you still have problems then it is possible that there is another bgl file containing the airport that is turning them off.
 
You must log in or register to reply here.
Back
Top