Questions About Aerofly TMD Structure and Immersive Modding

  • Hello, I've recently gained interest in TMD structure, and altering them to add to immersion in-game.

    To Developers and Modders, I hope all is well. I wanted to first say thank you for all the work you've done on Aerofly over the years. I've recently started experimenting with aircraft camera and immersion tuning through editable '.tmd' aircraft files, as of recently, adjusting camera inertia, damping, and cockpit movement behavior to create more realistic environmental motion and touchdown feel through code that is already accessible.

    Through this experimenting, I've become heavily curious and very invested in learning more about not only the internal structure of .tmd files, but how to code and maybe even mod in the near future. Within these .tmd files, I am interested in knowing if the code available pertains to-

    • Camera Physics/Inertia Systems
    • Suspension and Touchdown Dynamics
    • Acceleration Linked-Camera Movement
    • Reusable Physics/Filter Objects
    • Immersion Related Systems in General

    I completely understand that some or most files are not available to the public to be edited. That some systems are proprietary or intentionally protected, I'm not asking that to be changed. I don't want to access private files or reverse engineer protected content. I'm mainly interested in understanding what types of editable systems are officially supported for modding and experimentation, or possibly if the structure allows for more code.

    I was wondering if there is:

    1. Any Documentation Regarding .tmd Files

      2. Any List of Supported Objects/Parameters

      3. Or any recommended way to learn more about creating realistic immersion enhancements within Aerofly FS 4

    I've really enjoyed experimenting with the existing editable camera parameters and would love to continue learning in a respectful and supported way.

    Thank you very much for reading this, and thank you very much for all the work done on Aerofly.

    Best Regards,

    Mar17

  • I use the WIKI written for the FS 2, which also applies to the FS 4 largely:

    My experience is: try & error.

    It is very important to always do everything in the user directory and not in the original directory. You can also copy an aircraft complete over and then you just have to change the folder name and the names of the same name of the files, because each aircraft must have its own name.

    Tschüss, Michael (🍎🚁)

    Configurations:

    - MacBook Pro (16", 2024); Chip: Apple M4 Max; actual macOS
    - Controllers: | WinWing: URSA MINOR-Fighter-Joystick R, EFIS-L & FCU & EFIS-R | Thrustmaster TCA AIRBUS EDITION: 2x Quadrant, 2x Quadrant Add-On | Pro-Flight-Trainer: PUMA X | Steelseries: Nimbus+

    - iPad (12,9", 4th Generation, RAM: 6 GB); actual iOS | Steelseries: Nimbus+

  • The tmd files build the entire aircraft from building blocks. The buildings blocks themselves are implemented in C++ code, which you cannot edit. But you can set parameters for each building block (object) in the file and all TMD files can be edited.

    The camera already has a simulated inertia and physics. The parameters to adjust the damping and spring constants are available, e.g. see F18. You cannot modify the linear spring-damper system to something else but you can adjust the parameters.

    All building blocks / objects are reusable.

    You can implement immersion related systems just like any other object in the tmd. More advanced features like particles are not available, this would require new building blocks to be implemented first.

    Some documentation is available in the wiki: https://www.aerofly.com/dokuwiki/>
    The SDK and example aircraft is available on our website: https://www.aerofly.com/developers/
    On my personal website I have several tools that you can use: https://www.aerofly-sim.de/download/software
    One of them is called code snippets, which contains a lot of templates for all kinds of building blocks. It's not up to date though. I would recommend using something like file locator to quickly find samples in the existing aircraft files and copy from there.

    Regards,
    Jan