An accurate flight model comprises a set of linked, non-linear differential equations. Such equations can be solved by a variety of numerical means (e.g., Runga-Kutta method) on a computer, but the computations can be very time intensive. One can make it easier for the computer by using simpler models (i.e., less complex with linearized and easier-to-solve equations), but the fidelity of the simulation may suffer. I assume that so-called "physics" models use a differential equation model and solve the equations in real-time to continuously compute the state variables incorporated in the model (e.g., linear and angular position, velocity, and acceleration in three dimensions).
I assume that what makes a "table-based" model fundamentally different from a "physics" model is that the table-based model does not involve solving differential equations in real time (i.e., as the simulation is running). I can imagine that a table-based model might include entries that would specify that, for example, at a particular position (e.g., altitude and orientation), velocity (3d), and acceleration (3d), a set of inputs (e.g., thrust, control surface deflections) results in a pre-defined change in position (3d), velocity (3d), and accerlation (3d). Obviously, the more entries the table has, the more accurately it can simulate a "physics" model.
I can see a couple of advantages to a table-based model. First, and perhaps most importantly, the CPU overhead needed to implement it is far below that necessary to chug through a complex physics model. Second, it may be difficult to construct accurate differential state equations to model a particular plane--these are generally complex and, as stated in an earlier post, depend critically on all of the plane's physical characteristics. A table-based model allows the designer to more readily incorporate heuristic information (e.g., climb rate and speed charts) about a plane's performance into its flight model.
In the end, I don't think that one approach is "better" than the other in every situation. If you have "perfect" equations for your physics model and ample CPU overhead with which to implement it, then that is probably the way to go. My guess, however, is that HTC had neither when designing AH.
- JNOV