• 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.

FSXA ATIS missing

S

supera380

Messages
95
Country
germany
Hi Folks,

Looking for some additional brain power here because mines all gone!! :confused:

I have 2 versions of the same airport, one a newer version with added aprons , objects plus some runway tweaks etc and an older version. I can consistently switch between the 2 versions and the older version always gives me ATIS comms (when I select the ATIS option from the menu) along the top of the screen in green. For the newer version, ATIS menu section appears but no streaming message or sound.

I have already checked that the ATIS Comms has the ICAO code only in the NAME field and in fact comparing Comms Lists in ADW shows the same info.

I also tried to re-add other modifications by opening all runways to both take offs and landings (some I had disabled) and also adding back in the runway starts which I had deleted for one runway, but so far nothing turns the ATIS back on!

Would any mods to the approach legs cause ATIS an issue? I did tinker with this when I built the newer version.

Any other thoughts?

Regards
Mark
 
Have the different ATIS the same Name?

Yes, I know, you have look at this.

But have a look again.

I have in the past looked at 10 Times and have no error found, but at the eleventh look
I found the Error.
 
Last edited:
Hi Sandra,

Yep! It looks like this. I even checked in Raw Data Mode but I did not see anything strange.

Capture.jpg


Thx
Mark
 
Hi Jon & team,

Well, after more investigative work, I believe I found the problem and fixed the missing ATIS service!

In one of my scenery updates I had decided to enter additional STARS in Approach Mode because my airport has multiple STARS per runway. So I used the suffix column for the ILS tag to indicate either "N" or "S" depending upon the position of the STAR from the runway. See screenshots below.

ATIS.jpg

Suffix.jpg


Well it looks like this Suffix used for the ILS name screws ATIS up. To fix this, I went back to the ILS table in the Approach Mode and removed the suffix by entering "0", the default value again. :confused:

I was able to fix this issue for 2 scenery updates which had the ATIS missing.:)

I am wondering if the Suffix field in the ILS Approach Mode is really enabled within ADE Approach Mode or if this is an FSX thing where the suffix for the ILS idnetifier name is not honored???

Do you have any thoughts on this and are you able to reproduce it? Not sure if this is really a FSX or ADE bug or not? I'll let you folks decide. Let me know if I should officially log this or not?

Regards
Mark

BTW - I had introduced this issue while using ADE v1.50 but it is also present in the v1.51.4528 Beta I am currently using.
 
While reading your original post, I simply thought it's one of the basic issues, but now I can see you are also walking on the fences of "area 51", where you can produce many unexpected results out from your experimentation's. I also bumped into something similar - whatever I tried, my results were far from expected. When walking on edge, don't expect much help from the others - they can't see or replicate your problem.
 
About a Suffix N or S at an ILS, I never read, but from Transitions with Suffix N,E,S,W to an ILS that i have read.
 
During the development of the Approach Mode Editor there were 2 key Documents used. The SDK and the ARINC 424 documents. When the SDK did not give enough data we then fell back on the ARINC 424 document which is the standard MS used for the Approaches.

The ILS is a precision approach to a specific runway so a Suffix cannot be used.

All other type approaches can have a Suffix letter and these are found on the Approach Plates. When the Suffix is used the runway must be numbered as R00.

Many non-precision approaches with a Suffix letter are not for any specific runway since the approach terminates at a Navaid Fix.



hope this helps
 
Last edited:
You must log in or register to reply here.
Back
Top