Posts by alebo62

    Look for an object [autotuning] in the .tmd file. Comment '//' the line


    <[string8][EventSetNAV1][ ... ]>


    or remove the whole autotuning object to fix this.

    You can change the approach lighting system by changing the name of the dummy object. The supported values are:


    appltsys1_alsf-2
    appltsys1_alsf-1
    appltsys1_sals
    appltsys1_malsr
    appltsys1_malsf
    appltsys1_odals
    appltsys1_rail
    appltsys1_calvert
    appltsys1_calvert-2
    appltsys1_std
    appltsys1_none


    For the reils you have the options reil_uni for unidirectional light along the approach and reil_omni for omnidirectional lights.


    Sorry for the documentation being not complete in many parts, we're preparing a wiki that will address topics like this and become a complete documentation over time.

    The downwash of one wing on another like the wing's downwash acting on the horizontal stabilizer uses the current value of the downwash at the wing (multiplied by a factor that can be adjusted for the relative position of the stabilizer to the wing), so there is no delay.


    However, the computation of the wing's downwash includes a small delay. This is done for numerical stability and because the flow field around a wing doesn't change instantaneously even for sudden changes in angle of attack. The value chosen for the delay is kind of a best compromise, a little too long for the wing acting on itself, a little too short for the stabilizer.


    This will be addressed when we move to the next version of the aerodynamic interactions between different parts of the airplane, then also allowing interaction between multiple elements.

    The lift slope of the 3D wing is computed dynamically at simtime, and it's done more like case 2).


    Each time the aerodynamic forces acting on a wing are computed, Aerofly FS 2 roughly does the following:

    • for each section, the 2D lift, drag and moment curves are interpolated from tip and root values. These curves are modified according to flap and aileron deflections.
    • the relative velocity is computed for each section, taking into account the wing's movement, wind, bending and the self-induced downwash (see below) computed the time step before
    • relative velocity and the curves are used to compute the lift, drag and moment for each segment
    • the downwash is computed for the next iteration. This is where the aspect ratio and the 3D wing as defined by the wing's sections comes in. For a low aspect ratio wing, we have a higher downwash and effectively a reduced lift slope for the 3D wing. The AspectRatioMultiplier is mainly used to tell the left wing that it is just one half of the total wing and vice versa.


    So, the key message is: the lift, drag and moment curves are defined for 2D airfoils, and the sim takes care of the lift slope reduction for finite wings automatically.