VP-50209

Vortex Editor - Update Sensor/Trigger lists to tables

VP-50215

Vortex Editor - New Directional light extension for the Vulkan renderer

VP-50488

Vortex Demo scenes - Upgrade Demo Project to Unity 6

VP-48192

Vortex Setup - Inconsistencies in the process name

VP-50295

Tire Model - Computed wheel footprint can flicker

VP-50419

Tire Models - Wheel Adapter outputs disappear when the wheel goes to sleep

VP-50500

Vortex Simulator - Display automatic placement is incorrect with Vulkan Renderer

VP-50503

Tire Model - Rolling Resistance Table field is missing

VP-50586

Tire Model - Rolling resistance inputs get cleared when simulation is stopped

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.

VP-50509

When utilizing Dynamics Scripts, fields generated within a container in the code may not be recognized by the Edit Fields Action. Any modifications made using the action could result in their removal.

When the script is run again, the fields will be re-created.

VP-51014

When starting the Demo Scene (2025.5) the Asset Bundle Scene is still visible even though the Unity project is not there

Do not select that Demo project.