VP-48239

VortexSetup - Add a search filter on the component page

VP-49136

Unity Integration - When in Unity Edit mode, the Vortex Role and Seat manager should be disabled

VP-49405

Unity integration - Whn pausing, the Vortex simulation and the Unity simulation should be paused at the same time

VP-49498

Vortex Setup: Distributed installation may take considerable time to synchronize with the remote server.

VP-49528

Unity Integration - The VortexIntegrationModule's post update is taking a few milliseconds on the Master process, some of its processing is not required on that node.

VP-48242

Constraints - When creating a constraint, the order the parts were selected is not used to set the reference parts

VP-48409

Interacting with the boundaries of an earthworks zone creates unrealistic forces

VP-49085

Device mapping script does not re-initialize with preferred preset

VP-49143

Device mapping script sends default values to its outputs before the script has been initialized

VP-49289

Unity Integration Demo Scene : Cascade Shadow atlasing error

VP-49333

Unity Integration : Undo deleted Earthwork zone is not functioning as expected following save

VP-49368

Tire model: Longitudinal slip calculation returns wrong value

VP-49399

Demo Scenes: Control presets are not working properly

VP-49401

Vortex Editor: "Replace Assembly..." option not available at scene level

VP-49557

Vortex Launcher: Clicking outside of the Login ID/PIN fields does not remove their focus

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.