VP-47961

Vortex Create - The hydraulic Actuator extension "Float Mode" should reset the lock position of the constraint when disabled

VP-48032

Unity Integration - Preload mesh colliders toggled during Play mode breaks the collision

VP-48496

Unity Integration - Cables are not visible when asset bundle prefabs are not activated

VP-48532

Content Debugger - Values in read-only mode are almost unreadable (black on dark grey)

VP-48589

Unity Integration - One should not be able to add a mechanism or an assembly in Play mode

VP-48591

Unity Integration - Mechanism just added does not simulate unless the scene is saved

VP-48596

Documentation - The system requirements say to use the wrong Unity version

VP-48725

Vortex Licensing Tools GUI for 2024.6.0.11 RTM does not open and says there is a missing DLL

VP-48790

Vortex Editor - Editor fails at saving if more than 4 soil bins are added to a Vortex file

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.