I am still training myself on this beauty, no full flights yet just take off, run a long circuit and come back to the same airport (www.virtual-aviation.net).Anyway, today I didn't have time for the 45 minute checklists so I did that quick stuff for an approach to Asuncion, Paraguay (SGAS). I set NAV1 to VAS 115.90 with 109.50 (LOC) on standby, set CRS to 203 degrees and finally the ADF1 to ASU 360.00.During the base leg I configured myself for ILS approach tuning on the localizer (was on standby) and then pressed the VOR/LOC button to get the proper display on the EHSI. I then turned to the final leg. The problem I saw/noticed was that while I could see that I was getting horizontal guidance (The VOR needle AND the localizer left/right guidance), the glideslope indicator was ALWAYS in the middle.NOw, I am relatively experienced in ILS approaches, I like them but I am certainly NOT an expert to have tracked the glideslope from base to finals remaining on the GS without deviation. I chcked it and as I said, the horizontal (magenta) bug moved left or right dependeing on my horizontal deviation but the GS bug always stayed in the middle as if I never went over or under. I know I went above the GS because I got the 3 and 4 yellow VASI lights but even then the bug was still in the middle.Am I missing something else here? as I said, I was properly configured (CRS, LOC on NAV1, VOR/LOC pushed until I got the right mode.

Confirm that the old data in FSX is using the same ILS freq, easily done by opening the map and drill down to the airport and click on it.Normally you would expect the GS needle to indicate below glideslope until intercept as you suspected. However, the MSFS ILS information includes a range that is set to an aritificially low number so if you were way out there you won't get the GS alive until closer. I don't remember the range but it is somewhere around 10 nm.

Hi Dan, That is precisely how I got the ILS frequency, looking up the ILS feather on the FSX map, for SGAS (Asuncion, Paraguay) it had 109.50 with 203 degrees heading.As for the other part, that GS needle never moved from the center, not from afar, not when close, it was just stuck there in the center so I had to use the approach lights as sole vertical guidance.Maybe someone can try it out and see what results they get.

Confirm that the old data in FSX is using the same ILS freq, easily done by opening the map and drill down to the airport and click on it.Normally you would expect the GS needle to indicate below glideslope until intercept as you suspected. However, the MSFS ILS information includes a range that is set to an aritificially low number so if you were way out there you won't get the GS alive until closer. I don't remember the range but it is somewhere around 10 nm.

Does the aprroach have a GS? Some are LOC only.

Theoretically, if the GS was inoperative for some reason, there should be red G S warning on Your EADI (someone correct me if I'm wrong!).EDIT:I've checked it, and it's as Emilio said ILS approach, so there should be GS. Maybe some FSX issue?

Ye, there should have been GS given it was an ILS. I just did another circuit, this time in my "home" airport MPTO using exactly the same procedure only with a new set of frequencies and headings. This time I could see the GS going above and below so I guess it may have been some FSX problem.

Theoretically, if the GS was inoperative for some reason, there should be red G S warning on Your EADI (someone correct me if I'm wrong!).EDIT:I've checked it, and it's as Emilio said ILS approach, so there should be GS. Maybe some FSX issue?