Vortex Studio 2024.6 Change Log

What's new?

Latest Vortex Linux Release Download

What’s changing

The Linux package for Vortex Studio is now accessible to the public for download with each new version release.

Why it matters

A more user-friendly method for downloading Linux has been requested by numerous customers.

Additional details

Vortex Setup Update Mode

What’s changing

Vortex Setup now introduces an update mode that considers previously installed packages, optimizing download, installation time, and disk space usage.

Why it matters

Previously, when updating an installation with multiple packages, it was necessary to reinstall all packages and dependencies. This process resulted in unnecessary time consumption.

Additional details

Vortex Integration with Unity - Build Scripts

What’s changing

Scripts utilized in constructing the Unity application for integration with Vortex have been made public.

Why it matters

Various use cases are accommodated when constructing the application to simplify the development process.

Additional details

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

End-of-life Notice

n/a

Minor Improvements in Vortex Studio 2024.6

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

ID

Summary

ID

Summary

Fixed Issues in Vortex Studio 2024.6

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

ID

Summary

ID

Summary

VP-48145

Vortex Simulator - Exercise options page does not properly cut off titles that are too long

VP-48427

Vortex Integration - Moving mechanism in Unity only takes effect after saving

VP-48475

Vortex Simulator - Exercise options page does not properly cut off descriptions

Known Issues in Vortex Studio 2024.6

ID

Summary

Workaround

VP-39601

Unloading a lot of Dynamics Script Extension takes a long time. At unload when removing a Python script, ending a Python Interpreter is exponentially slower the more script is present in the loaded content. When more than a few hundred scripts are present, the unload time can be a few 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.