The A2A Simulations Community

I can not get the glide slope to work either but the course needle works.

I've graduated the MSFS IFR class so I'm no stranger to this stuff.

Any ideas?

You can see here that the course needle works so I am tuned in correctly and I am obviously above any possible glide slope yet the needle is dead. This is Kodiak (PADQ) ILS 110.900.

Channel ----LOC (MHz)----G/S (MHz)
46X--------110.90--------330.80

110.90 should have a GS of 330.80 that gets tuned in behind the scenes. Perhaps there is a problem in the B-17 configuration file?

I'm thinking you are to high so the horizontal will not register coming into an ILS you should be around the 3000ft mark I had no problems at this airport

_________________
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

No I landed as well...

Only the B17 has the problem.

So which needle won't work

_________________
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

The GS in my screen shot is pegged dead.

Here is another shot..

The CDI works so I'm on the right freq.

Mooney works fine...

One thing is that REX weather engine make a nice difference though...

Yes it's a great program
Humm that is a funny one
Have you backed up your maintenance hanger and tried a new flight if so keep the backup and try a reinstall of the B-17 I take it you have tried another airport

_________________
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

I want to try a few things before a reinstall. Seems a few people have had this but it went away.
Maybe it's only one of the four models. Another thing I want to try is switching planes in flight to one that has a working ILS and then switching back. Maybe that will reset something.

OK Figured it out!

First attempt was to continue from where I left off in the B17 and then switch aircraft on the tarmac.
This had the effect of killing the ILS in my Mooney. I then switched to the Bonanza and that killed the ILS in the Bonanza. I tried doing free flight with the Mooney and the ILS was still dead. Something got messed up and those planes were broken as well now.

So, I decided to free flight a plane at Kodiak that I hadn't contaminated with the B17 settings yet. I picked a Cessna, drove it to the touchdown point for the ILS, and had both needles active.

THEN I switched aircraft to the B17 and POOF - I now have both needles working in the B17!

Not sure if it matters, but, while in the Cessna I switched back and fourth from the GPS to the NAV setting multiple times while driving to the touchdown point...

At least now when this bug comes up in the future we know how to help people fix it.

So here is the screen shot with GS and CDI both working!

BOZ what's your default flight set as? Asking because it's been reported that changing it may lead to issues with payware aircraft down the line.

_________________

I have it set as my B17 flight. Think that is a problem?

Could be. Do you have it set to load when FSX first starts? I remember reading in another developers forum that their aircraft needed the default flight to be loaded when FSX is first run, and should be the default that comes from MS. From there you could use the free flight menu to set your flights.

_________________