So your idea makes sense I think - this is how I interpret what you are saying

:( ... those look right...strange...I looked right at those Events and decided they did something else.Too bad K:AP_PITCH_REF_SET

Too bad K:AP_PITCH_REF_SET

I believe it is K:AP_PITCH_REF_SELECT.. but no, it does not appear to work.

The SDK is your friend. This key_event is used only to tell the sim to look for manual keyboard entries of the +/- keys.

AP_PITCH_REF_SELECT Selects pitch reference for use with +/-

AP_PITCH_REF_SET won't work for the simple reason there IS no such key_event.

Hi!I forgot I had the same trouble while coding my CWS P, sorry guys. Maybe we were uising the ptich parameters wrongly. but yes they didn't work for me neither. I use for FLARE the elevator trim approach but limited by a timer of no more than 2 secs, other wise it upsets the aircarft totally. To solve the ATT hold issue I used (>K:SYNC_FLIGHT_DIRECTOR_PITCH) when I raech the desired ATT angle. Maybe a combo of elevetor trim and FD sync is more complex but it could work.Javier

K:AP_PITCH_REF_INC_UP and K:AP_PITCH_REF_INC_DN should work fine.It's just that if you've calculate the absolute value you want it's sort of annoying to have to chase it using inc/dec.There's not much use in wishing for a k:event that doesn't exist :( But, In a similar situation I found an event that didn

Some random thoughts that may or may not be helpful and are offered from a profound state of ignorance!When following a glide slope the aircraft is really trying to track a varying height defined by the glide slope, so why not try this in Flight Simulator.The attached figure shows how the glide slope height could be calculated at the aircraft and then predicted forward to give a target glide slope height h_T. ΔT is an arbitrary constant to be determined experimentally.h_T = h_A * γ / (γ + ) + V * ΔT * γAlso, it's essential to ensure h_T is always positive!Converting to flight simulator variables:h_A = PLANE ALT ABOVE GROUND γ = NAV GLIDE SLOPE or = 3^o?ε = HSI GSI NEEDLE or NAV GLIDE SLOPE ERROR:indexV = GROUND VELOCITYHaving calculated h_T, KEY_AP_ALT_VAR_SET should set it into the autopilot height hold.This is untested and, although everything is listed in the SDK, I don't know if they exist or work.

There's not much use in wishing for a k:event that doesn't exist :( But, In a similar situation I found an event that didn