TFR operation

Hi Steve

Well done on an impressive add on to FSX, very realistic & brings back the memories.

I've noticed that the TFR climb/dive command is calculated from instantaneous height above ground and is not predictive. This results in a/c altitude falling below the set clearance and video returns breaking through the ZCL on the E-scope. In reality, this would result in a fail/fly-up. Any chance of modifying the calculations to be predictive?

I realise that the actual algorithms for g-command are complex, and use stick position, flight vector, pitch, velocity, acceleration, range and angle to peak. However something simple would suffice.

Cheers,

Paul

Thank you for the kind words.

The climb/dive command IS predictive. We have the only true look ahead, pitch and roll stabilized TFR in FSX. It is a very complicated system and works quite well.

We are working on Version 2.0 of the aircraft and improving the pitch steer bar are one the of the things on the list as well as adding pull-up commands. Unfortunatly FSX make it hard to model thing the way they should work, so we have to simulate systems in the simulator as best it will allow us.

Steve

Paul,

As Steve mentioned it is predictive but also absolute - using our TFR look ahead along with height above ground, 1 of 3 modes are then used to send data to the autopilot. The big problem is the lag of the autopilot and it's inherit problems of overshooting. I have recently found a new setting that does increase the responsiveness of the AP pitch system but as usual fixing one thing did break other modes of the AP and overshoot became more pronounced. Right now things are in a happy mix where all modes act appropriately although in the future I would like to try the new settings along with ALOT of testing. This is in the long future though.

Thanks for the comments,

Roman