Bryan,I've noticed that the FO isn't quite perfect on appropriate situations to call glideslope deviations. In particular, I've noted two different instances.1. You have not yet intercepted the G/S, but at some point started a "descent". While handflying it's not uncommon for me to at moments end up with a 1-200 fpm descent. The end result is usually altitude deviations <20ft total by the time I correct, but it seems that if the G/S was alive when this happened, the FO believes you've intercepted the G/S and starts calling "glideslope deviation" as you continue to fly level waiting to truly intercept the glideslope (i.e., the FO now believes you are below the glideslope rather than waiting to intercept from below).2. Near the runway the FO will start to make pseudo-legitimate glideslope calls. No matter how good I am, I don't consistently hold the G/S down to the flare...nor is this necessary since once you reach DH you are officially flying a visual approach. However, even 50' above the runway the FO will make glideslope deviation calls.I'm not sure how things are coded, but perhaps a simple solution would be to disable this call in the coding unless you are between 1500' AGL and whatever is set as DH (or generalize to 200' if necessary)? You should be established by 1500' AGL so this would avoid point (1) and under DH you are legally visual so this would deal with (2). Just a thought. It's a nusuance but hardly a realy knock against the program. Please don't take the stream of comments coming from my end as bad thoughts on FS2Crew. I love the products and will continue to love them even if nothing about them changes. I just figure it can't hurt to make small suggestions and see what happens.Eric Szczesniak

Bryan,I've noticed that the FO isn't quite perfect on appropriate situations to call glideslope deviations. In particular, I've noted two different instances.1. You have not yet intercepted the G/S, but at some point started a "descent". While handflying it's not uncommon for me to at moments end up with a 1-200 fpm descent. The end result is usually altitude deviations <20ft total by the time I correct, but it seems that if the G/S was alive when this happened, the FO believes you've intercepted the G/S and starts calling "glideslope deviation" as you continue to fly level waiting to truly intercept the glideslope (i.e., the FO now believes you are below the glideslope rather than waiting to intercept from below).2. Near the runway the FO will start to make pseudo-legitimate glideslope calls. No matter how good I am, I don't consistently hold the G/S down to the flare...nor is this necessary since once you reach DH you are officially flying a visual approach. However, even 50' above the runway the FO will make glideslope deviation calls.I'm not sure how things are coded, but perhaps a simple solution would be to disable this call in the coding unless you are between 1500' AGL and whatever is set as DH (or generalize to 200' if necessary)? You should be established by 1500' AGL so this would avoid point (1) and under DH you are legally visual so this would deal with (2). Just a thought. It's a nusuance but hardly a realy knock against the program. Please don't take the stream of comments coming from my end as bad thoughts on FS2Crew. I love the products and will continue to love them even if nothing about them changes. I just figure it can't hurt to make small suggestions and see what happens.Eric Szczesniak

This is a good idea...to make the calls within the "stabilized approach" window. Typically in a jet it something like stabilized by 500 AGL for visual or 1000ft AGL for precision approaches. I'm not sure how it deviates for prop planes, but posing the question to RR should yield quick results.

This is a good idea...to make the calls within the "stabilized approach" window. Typically in a jet it something like stabilized by 500 AGL for visual or 1000ft AGL for precision approaches. I'm not sure how it deviates for prop planes, but posing the question to RR should yield quick results.

Hi Guys,I'll see what I can do in a future update. I can probably tweak this a bit as per your requests.Current conditions to trigger the call are this:Display mode set to Landing or Final.Aircraft not on groundGlideslope position < - 30 or > + 30.... that's around 1 dot or so.Approach type set to PrecisionWithin 80 degrees of the inbound approach courseAircraft Alt < 1500 feet above the arrival airport elevAircraft Alt > 100 feet above the arrival airport elevReminder: Arrival Airport Elev is determined by the value you entered in the Pressurization controller window on the center panel.Cheers,

Hi Guys,I'll see what I can do in a future update. I can probably tweak this a bit as per your requests.Current conditions to trigger the call are this:Display mode set to Landing or Final.Aircraft not on groundGlideslope position < - 30 or > + 30.... that's around 1 dot or so.Approach type set to PrecisionWithin 80 degrees of the inbound approach courseAircraft Alt < 1500 feet above the arrival airport elevAircraft Alt > 100 feet above the arrival airport elevReminder: Arrival Airport Elev is determined by the value you entered in the Pressurization controller window on the center panel.Cheers,

Good information. I'll have to pay a bit more attention to this, as it seems you have this programmed basically the way I was thinking already. At least in the first example I was guided to intercept at about 1600' AFE, so maybe it has just been some odd circumstances here and there.