Here's are the requested shots Alex;http://forums.avsim.net/user_files/132508.jpghttp://forums.avsim.net/user_files/132509.jpghttp://forums.avsim.net/user_files/132510.jpgAs you can see intially I'm descending at -500FPM. It then goes down to ~ -800FPM and then up to ~ -250FPM. I have only notice this at low speeds as that's when I use V/S.Cheers,Paul

Dear Paul,Evey automatic control system has a tolerance margin and an associated "response" curve related to departure from "target" figures. You can see that the flight director is commanding slight up in the first case and slight pitch down in the second (0.5 degrees attitude difference at most ?). The FCC will do that in a manner which guarantees that necks will not "snap" at row 40, nor passenegers see their orange juice travelling to the roof. The FCC also knows you are banking at low speed. Hence, lag that may allow for +-200 fpm deviation (in this case) and "measured" response is perfectly acceptable. What would NOT be acceptable is the system being "stuck" or not responding at all for more than 5 - 10 seconds.Note that the easy thing is to programme instant reaction rather than using data filters and virtual accelerometers. This however is wrong and totally unacceptable. Think what would happen in even light turbulence...Roller coaster ride if such a "design" were to be implemented.Best,Vangelis===================================== E. M. Vaos Precision Manuals Development Group www.precisionmanuals.com=====================================