Vortex Studio 2024.8 Change Log

What's new?

Truck with Trailer in the Unity Demo Scene

What’s changing

A truck with trailer has been added in the Unity Demo Scene.

 

 

 

Why it matters

The truck with trailer equipment demonstrates the vehicle capabilities of Vortex Studio as well as the integration capabilities of Vortex with Unity.

Additional details

More documentation is planned in the next releases.

See https://cm-labs.atlassian.net/wiki/spaces/VSD2408/pages/811656842/Opening+the+demo+project+from+Vortex+Demo+Scenes+in+Unity+Editor#Terrain-Demo

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 https://vortexstudio.atlassian.net/wiki/spaces/VSD2408/pages/3716921120

End-of-life Notice

n/a

Minor Improvements in Vortex Studio 2024.8

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

ID

Summary

ID

Summary

VP-48528

Vortex Editor - Add MSAA anti-aliasing mode to Vulkan Renderer

VP-48527

Vortex Editor - Automatic replacement of SkyDome with SkyBox when using the Vulkan renderer

VP-48751

Earthwork - An Earthworks Zone extension not longer requires a File Terrain as its parent

Fixed Issues in Vortex Studio 2024.8

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

ID

Summary

ID

Summary

VP-48707

Vortex Editor - Terrain demo scene materials do not appear properly

VP-48785

Vortex Editor - Earthwork zone cell size less than 1 cm can cause a crash

VP-48818

Vortex Director - Unable to inpect or activate licenses on all computers of a simulator when running in elevated mode.

Known Issues in Vortex Studio 2024.8

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.