The A2A Simulations Community

OK guys, here's the problem- Been flying the '17 for a few months now, and haven't really had any trouble with anything so far, but today I noticed that the Glide Slope indicator on the ILS isn't working. I've tried it at two different airport with ILSs, and confirmed with the default C172 that the FSX glide slope IS working. Any ideas?

FSX, SP2
Windows Vista, 32 bit
Only payware addons are the B-17 and the Cub- freeware, a few aircraft.

_________________

Yup, had the same problem, try setting the frequency on the bottom Nav freq. on the radio. i think the ILS freq. will only work on the bottom one.

_________________

The frequency needs to be set in the NAV1 frequency box. Pay close attention to the displayed frequency
LSD's as for some reason instead of 1xx.500 I have seen 1xx.400 and of course the tuned VOR/ILS will not
be displayed. Cycling through the setting several times often corrects the issue...

_________________
Paul


i5-2500K @4.3Ghz OC - GA-P67A-UD7-B3 - 8GB Corsair 1600mHz

OK, tried again just to make sure freq, radio, etc, is correct. I do have a localizer indication with NAV1, but still no GS indication. The frequency is 109.15, so I'm not getting the .5/.4 deal.

_________________

Humm...that's strange. I just flew 6 or 7 ILS approaches at various airports the past two days.and encountered no problems.

An on that digit anomaly, that should have read 1xx.150 was 1xx.140 or 1xx.350 was 1xx.340 etc.
It's the 10's of khz digit that somehow gets out of whack.

Paul

I might be being a bit stupid here, but humour me. Can you post the airport codes, and rwy numbers so it can be tried by other people. It may help to confirm it is a plane issue or not.

If you goto EGMC and land on runway 24, with an ILS freq. 111.35, rwy heading 234 (for the course on the map), and see if the glideslope needle works there. I know it works at the airport, it's my test airport.

_________________
Tony

Intel core i7-2600 3.40GHz, 16GB DDR3-1600 Ram, GT430 1GB Graphics, Windows 7 Premium 64bit, FSX Gold Acceleration. REX 2.0 overdrive, TrackIR 5, Saitek X52Pro, CH Rudder Pedals, Saitek Cyborg X.

I went to EGMC took off did a 180 turn to heading 234 for runway 24 ILS 111.35 here are the pic's



















Remember the left and right mouse button moves the dial up or down don't forget pointer left of point will change the FREQ 000.
Pointer right of point will change .00
Hope this helps

_________________
Ron
B-17 AIRFRAME 710 HRS PLUS AND CLIMBING




GIGABYTE X58A-UD5 MB, INTEL I7 950, 12GB DOMINATOR-GT DDR3 RAM, WIN7 64, GIGABYTE SUPER OVER CLOCK GTX 560 TI 1GB GGDDR5 1000Mz, CORSAIR 850W PS, NOCTUA NH-D14,
TRACKIR 5 & TrackClipPro

Whoa Norforce! WAY too high on that approach. You musn't be doing the approach correctly, because the glidslope should bring you in with the VASI's and you should land right at the beginning of the runway, where all the skid marks are.

_________________
© 2011 Peter J. Carlson, All Rights Reserved
"O! for a horse with wings!" -William Shakespeare

OK, kinda odd, but for some reason it's decided to work for me... both different airports that didn't work before. I'll have to keep flying and see if it goes on me again. I'll keep you posted if that does happen.

_________________

Naw PJC, it doesn't work that way at EGMC, the glide slope doesn't line up with the papi lights, never has. I grant you, in the final approach pic he was a bit high, but the pic before that he was perfectly on glideslope, and the lights were still wrong. They are always different, it's the same for any plane on ILS there. I prefer to use the papi anyway, I just test ILS there because I know what to look for.

The thing I found most strange in the pics was the fact that ADF was selected in the radio stack and not NAV1. I noticed the frequency was right, but I always select the NAV1 in the stack too. Maybe he was using the NDB at SND I don't know. It's strange because the VOR is at the 06 end of the runway, but the NDB is nearly half way down runway 24 on the left. Not sure of the navigation technique there. I would've switched to NAV1 on my approach personally.

@bamaham93 Glad you've got it working, I suspect something was slightly off, maybe the frequency wasn't exactly right, I don't know. You still never posted the codes to the airports you were trying though, never mind

_________________
Tony

Intel core i7-2600 3.40GHz, 16GB DDR3-1600 Ram, GT430 1GB Graphics, Windows 7 Premium 64bit, FSX Gold Acceleration. REX 2.0 overdrive, TrackIR 5, Saitek X52Pro, CH Rudder Pedals, Saitek Cyborg X.

Tony, the Nav 1 receiver drives the ILS gauge automatically when tuned to an ILS frequency. You do not
need to select it.

Thus, you can use Nav2 or ADF1 or 2 to drive the Radio Compass.

_________________
Paul


i5-2500K @4.3Ghz OC - GA-P67A-UD7-B3 - 8GB Corsair 1600mHz

Oh right, Thanks Gypsy Baron, I didn't know that. Well not that you don't need it selected anyway. But if it wasn't selected, surely the the red arrow on the map wouldn't show up? And if you had an ADF driving the radio compass, wouldn't that same ADF show as the red arrow on the map? I don't suppose it really matters once you're on an approach though, just asking.

_________________
Tony

Intel core i7-2600 3.40GHz, 16GB DDR3-1600 Ram, GT430 1GB Graphics, Windows 7 Premium 64bit, FSX Gold Acceleration. REX 2.0 overdrive, TrackIR 5, Saitek X52Pro, CH Rudder Pedals, Saitek Cyborg X.

Seriously we went over this a little way back. Not All PAPI and VASI line up with an ILS system. PAPI and VASI work on wheel to eye height. The MEHT for Rwy 24 at EGMC is 48.
Check out this post viewtopic.php?f=23&t=24402 for explanation.

_________________

I knew there'd be a technical explanation, but I didn't know the technicalities. I guess a real pilot would know the numbers for where he/she is going, and the aircraft they're flying, and make some sort of adjustments. I just crash the nose into the numbers on the runway

_________________
Tony

Intel core i7-2600 3.40GHz, 16GB DDR3-1600 Ram, GT430 1GB Graphics, Windows 7 Premium 64bit, FSX Gold Acceleration. REX 2.0 overdrive, TrackIR 5, Saitek X52Pro, CH Rudder Pedals, Saitek Cyborg X.

That's a valid technique. I tend not to use the word "crash" more like gently bump the nose onto the number. Crash tends to upset passengers, cargo, and crew.

_________________