VP-47501

Unity Integration - Add an option to create, map, and apply Mechanism and Assembly prefabs in a scene

VP-47502

Unity Integration - Identify Prefab types in Vortex Prefab List

VP-47734

Demo Scene - Excavator Update

VP-47840

VortexEditor - Implement Material Visualization View with random colors for primitive CGs

VP-48044

VortexSetup - QOL Added option to select all PC

VP-48073

Terrain streaming - Material is not streamed OnSimulationStart

VP-47818

VortexSetup - Harmless pop-up Error at launch

VP-47844

Terrain Streaming - Wrong collision geometries displayed in dynamics visualizer with terrain streaming

VP-47984

Terrain Streaming - Dynamics visualizer crashes when at the edge of the terrain

VP-47997

Vortex Setup - Users can be given a missing add-on warning when the add-on is already installed

VP-47999

Vortex Setup - Installation size can be wrong when some packages are already downloaded

VP-48043

Vortex Editor - Crash when using Viewport Configuration

VP-48054

VortexSetup - Can freeze after pressing the login button

VP-48126

VxATPUtils - requestApplicationModeChangeAndWait() has an infinite loop when mode change is not possible

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.