Vortex Studio 2025.2 Change Log
- Marc Lievin
- 1 What's new?
- 1.1 Device Mapping Script support in the Vortex Editor
- 1.1.1 What’s changing
- 1.1.2 Why it matters
- 1.1.3 Additional details
- 1.2 Water Volume
- 1.2.1 What’s changing
- 1.2.2 Why it matters
- 1.2.3 Additional details
- 1.1 Device Mapping Script support in the Vortex Editor
- 2 Minor Improvements in Vortex Studio 2025.2
- 3 Fixed Issues in Vortex Studio 2025.2
- 4 System Requirements
- 5 End-of-life Notice
- 6 Known Issues in Vortex Studio 2025.2
What's new?
Device Mapping Script support in the Vortex Editor
What’s changing
The device mapping script features, which is available using the control presets page of the player, is now available in the Vortex Editor.
Why it matters
Using a script within the Vortex Editor allows users to validate that their control interface will answer the needs from within the Vortex Editor.
Additional details
Water Volume
What’s changing
The new Water Volume extension enables you to incorporate a graphical water volume effect into your scene or mechanism. This effect is purely visual and does not influence the dynamics of the simulation.
Why it matters
It allows simulation of water effect to simulation using our Vulkan-based renderer.
Additional details
Minor Improvements in Vortex Studio 2025.2
In addition to features documented in the “What's New”, minor improvements have been made during the development:
ID | Summary |
|---|---|
VP-49030 | Control Preset - Add a confirmation to the close button of the device mapping script dialog |
VP-49031 | Control Preset - Change the icon for Device mapping script edit button to be different from the add script button |
VP-49051 | Control Preset - Add An indicator in the main Control Preset widget to show that a control interface field is used in the device mapping script |
Fixed Issues in Vortex Studio 2025.2
Various bugs and workflow issues have been fixed during the development:
ID | Summary |
|---|---|
VP-49632 | Control Preset - The device mapping script dialog does not display script info when the device is not present |
VP-49827 | Vortex Editor: Decal flickering issue with Vulkan renderer |
VP-49830 | Control Presets - Current Value column stops updating when switching preferred presets |
VP-49919 | ControlPreset - Device calibration overrides should not modify the device mapping's or the device mapping script's parameters |
VP-49950 | Vortex Editor: Constraint Properties Windows doesn't update |
VP-50000 | Vortex Editor: Colliders are duplicated after reloading an assembly |
System Requirements
The system requirements have recently been updated to reflect the wider range of GPUs Vortex Studio supports when using its Vulkan renderer.
End-of-life Notice
n/a
Known Issues in Vortex Studio 2025.2
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. |