• Home
  • User Manual
  • Tutorials
  • Updates
Search Results for

    Show / Hide Table of Contents
    • twin 25.4
    • twin 25.2
    • twin 24.12
    • twin 24.10
    • twin 24.8
    • twin 24.6
    • twin 24.4
    • twin 24.2
    • twin 23.12
    • twin 23.10
    • twin 23.8
    • twin 1.30.1
    • twin 1.30
    • twin 1.29
    • twin 1.28
    • twin 1.27
    • twin 1.26
    • twin 1.25
    • twin 1.24
    • twin 1.23
    • twin 1.22
    • twin 1.21
    • twin 1.20.1
    • twin 1.19

    2024-04-24 - twin 24.4

    We are pleased to announce that twin version 24.4 is available. In this document you will find all the new features, improvements and fixed issues. If you encounter any problems during installation or during execution, please contact us by e-mail to info@digifai.com.

    Note

    When opening projects created with twin before version 23.8, the window layout may be incorrect. To fix this, please click on Reset Window Layout in the Window button in the toolbar.

    New features

    • twin is now officially compatible with Windows 11. We have adapted the look and feel of twin to the design guidelines of Windows 11.

    • In the Simulation Component Diagram view the simulation components are now organized in containers/groups as in the Simulation Components view. This helps to keep the diagram clean and clear. You can disable the containers in the Settings window under the tab Simulation Component Diagram.

      Note

      Projects created with twin before version 24.4 still do not use diagram containers. You can activate or deactivate the diagram containers manually in the Settings view. If you activate containers, please note that you must rearrange all simulation components in the diagram.

    • ObjectCoupler: You can now define input- and output signals which are then routed to the connected gripper.

    Improvements

    • We have improved the rendering performance of the twin Mirror when there are multiple 3D objects with the same geometry

    Fixed issues

    • When the geometry of a 3D object was invalid, twin-projects could not be loaded
    • Object3DFileSource: We have fixed a problem where the import process was still running when the trigger input was triggered again
    • When a selected BoxSource or SphereSource was deleted, the 3D object preview was still there
    • When duplicating a simulation component or 3D object with a number at the end (e.g. Object3DSource (1)) a new number was added (Object3DSource (1)(1)) instead of increasing the number (Object3DSource (2))
    • The description of the simulation component inputs and outputs was not displayed
    • We have fixed an issue that results in freezing 3D objects in the twin Mirror
    • We fixed an issue that caused twin to crash when many kinematic 3D objects were added to the simulation or moved while the simulation was running
    In This Article
    Back to top Copyright © Eberle Automatische Systeme GmbH & Co KG