/
Vortex Studio 2025.4 Change Log

Vortex Studio 2025.4 Change Log

What's new?

Feature Tire Model Improvements

What’s changing

Tire models, beginning with the Magic Formula tire model, are having their accuracy improved, usage workflow updated and documentation improved.

Why it matters

The new Magic Formula model is now available as an extension in the toolbox, like the majority of the other modeling tools in Vortex. It is now used in the same way as other extensions, improving it’s usability and homogenizing the Magic Formula with other Vortex features.

The Magic Formula model itself has been improved, with a number of low level bugs fixed. Making this a more accurate tire model.

The improved accuracy can be verified in improved documentation, which now contains both an improved theoretical description of the model and parameters, as well as verification against published data, ensuring that the model is accurate.

Additional details

The description of the new model workflow can be found here:

Tire Models

The new technical description of the Magic Formula can be found here:

Magic Formula - Pacejka 1989 Tire Model

The validation of the Magic Formula can be found here:

https://cm-labs.atlassian.net/wiki/x/ioGeTQ

Feature Path Constraint

What’s changing

A new constraint that restricts the position of a part to a user-defined path has been added.

Why it matters

The new constraint allows the user to constrain parts in very complicated ways that would either be impossible, or prohibitively inconvenient and expensive to do in other ways, such as with scripting logic or invisible colliders. It allows for representing more complicated parts in Vortex, as the path can model features such as grooves, rails, tunnels, etc.

Additional details

The documentation, which includes a tutorial showcasing its application in both content and code, can be accessed here: Path Constraint.

Feature Collision Rules with Labels

What’s changing

A new feature that allows collidable extensions to be tagged with labels, which can then be referenced via label collision rules.

Why it matters

The new feature allows a collection of collidable objects to be referenced by their label, where the collection is generated when a simulation begins. This means large groups of objects from multiple assemblies or mechanisms can be referred to by a single label, and any objects then added which have that label are also part of the group.

The feature also has the facility to collect rules in a json file, which allows centralization of the rules, and reuse between content.

Additional details

See also Collision Label Rules.

FMU Support in Vortex Studio

What’s changing

Vortex now supports importing FMU models conforming to the FMI 2.0 Standard. Models are imported through an extension, which provide a representation of the FMU that may interface with a Vortex simulation in the standard way (connecting fields, scripting).

Why it matters

FMI is an industry standard supported by 100s of tools for modeling and simulation. Models exported from these tools as standalone FMUs can be imported into Vortex and used without any further integration required between the exporting tool and Vortex.

Additional details

The documentation, which includes a tutorial showcasing its application in both content and code, can be accessed here: Integrating Vortex Studio with the Functional Mock-up Interface (FMI) Standard.

Minor Improvements in Vortex Studio 2025.4

In addition to features documented in the “What's New”, minor improvements have been made during the development:

ID

Summary

ID

Summary

VP-50190

VxATP - Improve output readability when looking for recursive tests

VP-50216

Vortex Editor: Spot light extension available for Vulkan Renderer

Fixed Issues in Vortex Studio 2025.4

Various bugs and workflow issues have been fixed during the development:

ID

Summary

ID

Summary

VP-49320

Vortex Editor: potential crash when switching between multiple opened documents

VP-49389

Vortex Editor: Intermittent system graphics freeze

VP-50135

Vortex Simulator: Windows taskbar may show up on 3dview configured as full screen

VP-50180

Vortex Editor: Toolbox Search By Category not Working

VP-50208

Vortex Simulator: Device Mapping - Cannot duplicate default preset when it has device mapping scripts

VP-50252

Vortex License Manager: duplicated license file when generating licenses for another computer

VP-50357

Vortex Editor: Cannot pick or use mouse spring

System Requirements

The system requirements have recently been updated to reflect the wider range of GPUs Vortex Studio supports when using its Vulkan renderer.

See System Requirements

End-of-life Notice

n/a

Known Issues in Vortex Studio 2025.4

ID

Summary

Workaround

VP-39601

Unloading a large number of Dynamics Script Extensions can take significant time. During the unload process, removing a Python script becomes exponentially slower as the number of scripts in the loaded content increases. When there are several hundred scripts, the unload time can extend to several seconds.

Reducing the number of scripts.

VP-41437

When a sound is created such that the listener and the emitter are exactly at the same location, or the listener is moving together with the emitter such that it is precisely above it, the sound that the operator hears becomes garbled. 

This happens for monaural sound track when the listener and the emitter are moving in tandem while being either too close or aligned vertically. The workaround is keep the sound emitter and the listener separate and make sure they can't be move in a way where they could align with each other.

VP-43810

Memory blocks dumped, when terminating the application. 

None. This memory leak is not growing, it's memory that should be returned before the end of the process.

VP-44315

Memory leak related to VxContactMaterial when there is a contact upon termination of a VxCore application.

Removing all parts and collision geometries before destroying the VxUniverse ensures that any ongoing contact is invalidated before destroying the VxUniverse. Optionally, using the higher level VxSim API and loading content created in the Vortex Studio Editor seems to work around this issue as the content is automatically unloaded before the application is destroyed.

VP-50018

Potential crash and visual glitches when DPI Scaling is enabled in Windows at something greater than 100%.

Do not use scaling. Vortex Studio Editor works best at a resolution of 1920x1080 at 100% scale.

VP-50509

When utilizing Dynamics Scripts, fields generated within a container in the code may not be recognized by the Edit Fields Action. Any modifications made using the action could result in their removal.

When the script is run again, the fields will be re-created.

 

Looking for labels? They can now be found in the details panel on the floating action bar.