: AnyLogic has transitioned from Java 11 to Java 17 , offering modelers access to the latest language features and performance enhancements.
: The software now runs natively on Apple Silicon (M1/M2/M3/M4) chips, ensuring a smooth experience for macOS users without the performance overhead of Rosetta.
: Building on the 8.9.0 release, version 8.9.1 fully supports Git version control . This allows teams to work on the same model simultaneously, manage branches, and resolve merge conflicts. To support this, a new multi-part ALP format saves models as a group of files (one per agent) rather than a single monolithic file, making it much easier to track changes in Git repositories like GitHub or GitLab. Technical Improvements and Modernization AnyLogic Professional 8.9.1
The 8.9.1 update introduces several "long-awaited" features that streamline the modeling of data-heavy systems:
: To combat potential memory leaks in large-scale simulations, the Memory dump analyzer allows users to take a snapshot of memory usage during a run to identify which objects are consuming the most resources. Use Cases and Industry Application : AnyLogic has transitioned from Java 11 to
AnyLogic Professional is distinguished by its "multimethod" approach, allowing users to combine modeling in a single environment.
: This version simplifies data processing by offering built-in connectors for Oracle, PostgreSQL, MySQL, and MariaDB . Previously, modelers often had to manually upload and configure external JDBC drivers; now, these can be selected directly from a list within the AnyLogic Database connectivity element. This allows teams to work on the same
: A major addition for the Material Handling Library (MHL) is the ability to manually move transporters using the move() function. This allows developers to direct vehicles to nodes even before an agent is ready for transport, which is essential for custom routing and pre-staging logic.
: The updated Downtime block provides more granular control over equipment maintenance and random failures. It includes new priority settings that define how a machine should respond if a failure trigger occurs while it is already busy—such as finishing the current task or stopping immediately for critical repairs.