What's new?
Vortex Studio Supports Unity 2022.3 LTS
What’s changing
As of Vortex Studio 2024.3, Vortex Studio Unity Integration now supports Unity 2022.3.21f1 LTS.
Furthermore, additional tools were added to help users transition to the latest Unity integration of Vortex Studio.
Why it matters
Unity LTS versions are released and supported for a 2-year period. Vortex Studio will follow with regular updates.
Additional details
Integrating Vortex Studio with Unity
How to Use Asset Bundles in the Unified Integration
System Requirements
The system requirements have recently been updated to reflect the wider range of GPUs Vortex Studio supports when using its Vulkan renderer.
End-of-life Notice
Minor Improvements in Vortex Studio 2024.3
In addition to features documented in the “What's New”, minor improvements have been made during the development of Vortex Studio 2024.3:
ID | Summary |
|---|---|
VP-47640 | Vortex Studio - Mark the Deformable Terrain extension as a experimental |
VP-47707 | Vortex Simulator - Add new page priority field on IQtPage to order pages properly in the operating Window |
VP-47730 | Vortex Editor - Create a CAD look shader prototype |
VP-47747 | Vortex Setup - Validate required disk space in distributed modes |
VP-47759 | Vortex demoscenes - use the new material table extensions |
VP-47760 | Vortex samples - use the new material table extensions |
VP-47787 | VortexSetup - Support Disk space requirement check in download mode |
VP-47901 | Vortex Simulator - The starting page category should be selectable |
VP-47910 | Raycast sensor - Add an output showing the distance between its origin and the intersection point |
VP-48056 | Unity Integration - AssetBundle export |
Fixed Issues in Vortex Studio 2024.3
Various bugs and workflow issues have been fixed during the development of Vortex Studio 2024.3:
ID | Summary |
|---|---|
VP-47849 | Unity Integration - Two earthwork zones in a single asset bundle do not function |
VP-47620 | Vortex Simulator - Missing metrics in downloaded pdf Exercise Final Report |
Known Issues in Vortex Studio 2024.3
ID | Summary | Workaround |
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. |