Vortex Studio 2024.5 Change Log

Owned by Marc Lievin
Jun 14, 2024
2 min read

What's new?

Integrating Unity Physics with Vortex

What’s changing

When utilizing the Vortex Integration in simulations, Unity objects are now capable of interacting with Vortex objects, and vice versa.

Why it matters

Utilizing Unity's physics engine, you can generate procedurally based animations that are physically accurate. This feature enhances both the immersion and functionality of your content.

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

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

ID

Summary

ID

Summary

VP-48084

Demo Scene -IntegrationDemoProject now uses com.cmlabs.vortex.integration.unity

VP-48113

Unity Integration - Control Interfaces are available using VortexVHL

VP-48159

Vortex Editor - Renderer Performance Improvements

VP-48164

Vortex Material Visualization - Add legend to material visualization mode

VP-48165

Vortex Material Visualization - Add material colorization for meshes and heightfields

VP-48250

Vortex Debugger - Create a Vortex setup file for debugging in the Dynamics Visualizer

VP-48254

Vortex - Add contact material names to the Contact Visualizer

Fixed Issues in Vortex Studio 2024.5

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

ID

Summary

ID

Summary

VP-45531

Potential crash in Keyboard Module

VP-48108

Contact between a box and a heightfield can have the wrong material

VP-48162

Unity Integration: Invalid Vortex Toolkit path reported

VP-48163

Vulkan Validation errors when pressing F3 for the FPS display

VP-48203

Unity Integration - Errors when unloading scenes that can result in crashes

VP-48210

Unity Integration - Crash in new projects when trying to add to a Vortex Prefab list

VP-48234

Vortex Editor - crashes when clicking on a constraint while in the attachment offset window

VP-48330

Vortex Studio - Potential crash at startup of a Vortex Application

VP-48297

Vortex Editor - crashes when closing documents without saving

VP-48331

Vortex Editor - Performance difference between renderers

VP-48349

Vortex Simulator - Score invalid when using fractional deductions

Known Issues in Vortex Studio 2024.5

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. Requires a 3rd party update.

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.