i have a problem when I set everythin up for a glideslope intercept using FSX visual flight path

 

I set up the NAV 1 to the ILS Frequency i see the red boxes above me I press APP and my 737 always turns to 360 degrees

lol... I saw the first response was from Chock and was like Huh??? Chock back? (then saw the date).

 

I press APP and my 737 always turns to 360 degrees

 

This really should be a new thread...

 

But sounds like localizer hasn't been picked up and just going into heading hold... just guessing btw.

lol... I saw the first response was from Chock and was like Huh??? Chock back? (then saw the date).

 

Same here. I have the feeling, that this kind of "starting" new topics has increased a lot in the past few days.

I agree, this would better be a new topic, reading through the whole thread to find the new posts is a bit unnecessary.

About a year ago, I had a problem like that. As I tried to do an ILS landing at Heathrow, the autopilot would send me the opposite direction. After fussing with this for a while and seeing the same problem with every aircraft, I came to the conclusion that the problem was being caused by another addon (one adding other crew voices). When I removed the addon, the problem went away.

 

I have the same problem with St.Louis. It's not a case of simply being off a few degrees. The damn thing sends me in the opposite direction. The St.Louis addon (from Taxi2Gate) has been buggy since the day I bought it -- another of thse regretted purchases. The developer made a few changes, but it still does not work right. I just avoid it.

 

There are other airports where ATC does weird stuff. Portland, Oregon is one. The ATC directs me to descend to 0 until I pick up the locator. Believe me, it is not a good idea to descend to 0! There are times when the ATC is best ignored, and this is one of them.

 

After you have done it for a while, the default ATC is pretty predictable. It always brings you in perpendicular to the approach. When it hands you off to the tower, it steers you part of the way towards the approach, but not all of the way. You pretty much are on your own at this point.

 

Typically, I add a couple steps to a landing. After the ATC assigns me a runway, I also enter the runway and approach into the GPS -- in addition to entering the ILS frequency. When the ATC hands me off to the tower, and gives me a new heading, I turn to the new heading. When I reach it, I turn on the GPS approach and let the GPS line me up with the runway. Only when I am lined up do I switch to NAV and/or APP. If the ILS does anything funny, I go back to GPS and descend manually, typically at a rate of about 800 fps.

 

It's sort of a belt and suspenders way of handling the approach. It may or may not be realistic, but it is one way of dealing with FSX's lobotomized ATC.

 

With the default 737, I come in slower than you do -- typically between 130 and 140. At an airport like Midway, this still may be too fast.

When my plane flies away from the glideslope, it is usually because I have forgotten to switch the ILS frequency to the active position after keying it in (you cannot enter a frequency into the active window but only into the standby one.

 

Henri

By shrre luck I found the problem at 10..am NZ Time

 

I had left the NAV / GPS Switcg on GPS I switched to NAV and all is well

 

Thanks for your input