/
Vortex Studio 2025.1 Change Log

Vortex Studio 2025.1 Change Log

What's new?

Compiler Update: Vortex Studio is now compiled with Visual Studio 2022

What’s changing

The Vortex Studio binaries have been successfully compiled using Microsoft Visual Studio 2022, specifically version 17.11.x, utilizing the 14.40 runtime libraries. The provided code files are compliant with C++17 standards. Please note that binaries built with Visual Studio 2015 are no longer accessible.

Why it matters

Keeping up with the latest compiler versions is essential for ensuring the long-term viability of projects. This practice not only reduces technical debt but also simplifies future upgrades. Newer compilers come equipped with enhanced optimizations that significantly boost performance and efficiency in the generated code. Furthermore, they offer improved support for modern C++ standards, which allows developers to write safer, more expressive, and maintainable code. Upgrading compilers also enhances security by addressing vulnerabilities and ensuring compatibility with updated dependencies. For more information, please refer to the additional details.

Additional details

The minimal version of the Visual Studio redistributable received an update in 2024.9.

Binaries created with Visual Studio 2022 are compatible with Visual Studio 2015 and newer versions, subject to specific restrictions.C++ binary compatibility 2015-2022

Minor Improvements in Vortex Studio 2025.1

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

ID

Summary

ID

Summary

VP-48198

Vortex Setup: In the main views, there is a contextual menu to hide already installed products.

VP-49036

Control Preset view: Add UI element to reset control interface input field without having to rely on the delete button.

VP-49243

Earthwork Integration - Simplify Earthwork Zone shader exposed parameters

VP-49346

Vulkan Renderer - Render transparent objects without anti-aliasing

VP-49410

Demo Scenes - Offshore demo scene refers to deprecated Skydome

VP-49474

Depth sensor image access is slow

VP-49479

Depth/Color sensor -Rendering improvements

VP-49527

Vortex Setup - Select all items available in the selection panel

VP-49548

Sensors performance improvements

VP-49562

Unity Integration - Copy Unity log messages into Vortex Logs

VP-49763

Vortex Setup - Change the installation workflow by only proposing components for the selected products

VP-49764

Vortex Setup - Change the Modify workflow to selects which products the user is interested to modify

Fixed Issues in Vortex Studio 2025.1

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

ID

Summary

ID

Summary

VP-48959

Flexible Cable - There is inconsistency in cable lengths across multiple cable systems that are controlled by the same winch command

VP-48980

Orphan edges of triangle meshes can cause a bad dynamics contacts

VP-49466

Grade Quality Sensors are not visible when too big and might crash Vortex

VP-49568

Device Mapping Script within a preferred preset doesn't initialize after a restart

VP-49644

Unity Integration - Vortex VHL observer callback is not raised when initially connected

VP-49649

Device Calibration: Cannot go back to “None”

VP-49659

Vortex Launcher - When logging out, the focus is not on the proper widget

VP-49690

Control Preset - Deleting a device mapping with an active device can causes a crash

VP-49739

Vortex Integration - Vortex exceptions can make the application crash

VP-49788

Vortex Licensing Tools on Linux cannot run on processor without AVX2 support

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.1

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.