Vortex Studio 2024.1 Change Log
- 1 What's new?
- 1.1 Tech Preview: New Hybrid solver
- 1.1.1 What’s changing
- 1.1.2 Why it matters
- 1.1.3 Additional details
- 1.2 Contacts Debugging Improvements
- 1.2.1 What’s changing
- 1.2.2 Why it matters
- 1.2.3 Additional details
- 1.3 Customization of the Operator Interface of the Simulator
- 1.3.1 Why it matters
- 1.3.2 Additional details
- 1.4 The Vegetation Library is no longer available
- 1.4.1 What’s changing
- 1.4.2 Why it matters
- 1.4.3 Additional details
- 1.1 Tech Preview: New Hybrid solver
- 2 System Requirements
- 2.1 License Requirements
- 2.2 Supported Platform
- 2.3 Hardware Requirements
- 2.4 Software Capabilities
- 2.4.1 MongoDB Support - Deprecated
- 2.4.2 Qt
- 2.4.3 Python
- 2.4.4 Unreal Engine Integration
- 2.4.5 Unity Integration
- 2.4.6 Supported Compiler
- 2.4.7 Simulink/MATLAB
- 2.4.8 Supported 3D model File Types
- 2.4.9 Vortex Human
- 2.4.10 Vortex Vegetation
- 2.5 Licensing
- 2.5.1 Compatibility Notice
- 3 End-of-life Notice
- 4 Minor Improvements in Vortex Studio 2024.1
- 5 Fixed Issues in Vortex Studio 2024.1
- 6 Known Issues in Vortex Studio 2024.1
What's new?
Tech Preview: New Hybrid solver
What’s changing
This version is intended as a technical preview of the new hybrid solver.
The hybrid solver solves the dynamic simulation issue using both direct and iterative methods. This is demonstrated via a novel Generalized Hybrid Solver extension and new Fast Friction parameters for dynamic materials and material pairs.
The generalized hybrid solver has some limitations. Before activating it, read the documentation carefully.
Why it matters
The standard solver in Vortex Studio uses a direct method. The direct method is more accurate, but it can get slowed down drastically for content containing many contacts with friction. An iterative solver can be faster for such use cases, but at the cost of lower fidelity.
Additional details
Tech Preview - Generalized Hybrid Solver and Fast Friction Model
Contacts Debugging Improvements
What’s changing
Contacts can now be selected in the 3D view of the Vortex Editor and their values inspected in the Properties panel.
A legend has been added in the 3D window that describes the different contact colors and modes.
Why it matters
This feature can be especially useful when debugging erroneous contacts between two geometries such as the contacts between a wheel geometry and the terrain during simulation.
Additional details
Debugging the simulation content
Customization of the Operator Interface of the Simulator
The Vortex Simulator operator window was updated in 2023.11. The window now supports new page categories as well as multiple pages under the same category.
Why it matters
This feature provides more flexibility to content creators when customizing the operator’s window pages.
Additional details
How to add UI pages to a simulator
The Vegetation Library is no longer available
What’s changing
Vortex Studio no longer supports the vegetation extensions and modules, leading to warnings when loading content that uses them. It is safe to remove these extensions and modules from the system.
Why it matters
The vegetation library could not be updated when updating rendering technology. It is suggested to create simple collision geometries for representing vegetation, and to utilize a 3rd party rendering engine for visualization in a simulator context.
Additional details
Integrating Vortex Studio with Unity
System Requirements
License Requirements
Starting with Vortex Studio 2023.7, no license is needed to run a simulation of content created with Vortex Studio Editor (or purchased from CM Labs).
"Running a simulation" is available on any single computer, allowing the use of applications like Python, Unity, or Unreal to run Vortex Studio content regardless of the operating system, as long as it's supported by Vortex Studio.
Vortex Studio Create applications, including Vortex Studio Editor and Vortex Studio Debugger, still require a license.
Whenever a Vortex Studio Activate feature is used in a simulation, a Vortex Studio license is required.
Supported Platform
Windows
Vortex Studio 2024.1 runs on the following platforms:
Microsoft Windows 10 (x64), version 22H2.
Microsoft Windows 11 (x64), version 22H2.
Linux
Not all features are available on the Linux operating system. See Features and Capabilities Overview for more details.
2022.8 is the last version supporting CentOS7 or equivalent.
An update to the latest Ubuntu LTS and equivalent operating systems is in progress.
Currently, Vortex Studio on Linux can only open content created on Vortex Studio (Windows) 2023.3 or earlier until this issue is fixed in a later release.
Using an earlier version of Vortex Studio on Windows to create content still works on Linux.
Hardware Requirements
Recommended Configuration for Vortex Create Applications
CPU Intel i7-9700 or better
RAM 32GB
GPU minimum 4 GB of VRAM with Vulkan 1.3 support
Nvidia GeForce GTX 10 series or later
AMD Radeon RX 5000 series or later
Intel UHD Graphics 600 or later
Any computer running Vortex Studio Create or Activate must support AVX2 instructions set.
Software Capabilities
MongoDB Support - Deprecated
Qt
Vortex Studio uses a custom version of Qt 5.15.2.
Python
Unreal Engine Integration
Vortex Studio 2024.1 supports integration with Unreal Engine version 4.27.
Unity Integration
Vortex Studio 2024.1 supports integration with Unity Unity 2021.3.22f1 LTS.
Supported Compiler
Vortex Studio 2024.1 supports Microsoft Visual Studio 2015 (VC14) compiler and above.
GCC 7.3 is the supported compiler on Linux.
Simulink/MATLAB
Real-time UDP protocol of Simulink/MATLAB is supported.
Vortex S-Function block in Simulink is supported.
Supported 3D model File Types
The following 3D model file types can be imported into Vortex Studio Editor.
.cive, .dae, .fbx, .flt, .ive, .obj
.osg2, .osga, .osgb, .osgs, .osgt, .osgx, .shp
Vortex Human
Vortex Vegetation
Licensing
Vortex uses RLM by Reprise Software™ for licensing.
See Licensing for more information.
Compatibility Notice
Between the Windows version and the Linux version
Between any Vortex version
Record-and-Playback as well as Keyframe files created with previous versions may not work with Vortex Studio 2024.1.
Vortex Console
End-of-life Notice
Python 3.8 needs to be used.
Feature Snap to Surface in the Vortex Editor was removed.
Minor Improvements in Vortex Studio 2024.1
In addition to features documented in the “What's New”, minor improvements have been made during the development of Vortex Studio 2024.1:
ID | Summary |
---|---|
VP-47022 | Unity Usage - VortexScene contains a list of Vortex extensions that will use Asset Bundle prefab |
VP-47147 | Vortex Simulator - Add new page category enumeration field on IQtPage and use it in Vortex Simulator |
VP-47149 | Vortex Simulator - Support more than one pages in each category |
VP-47150 | Vortex Simulator - Create new window extension for Drone view |
VP-47323 | Vortex Editor - Display the contact information in the property pane |
VP-47352 | Make the hybrid solver extension available in the Vortex Studio |
VP-47421 | Vortex Studio: Remove Vegetation Library |
VP-47510 | Vortex Simulator - Final Reports page header section update |
VP-47514 | Vulkan renderer: Display a legend for contact debugging in the 3D view |
VP-47551 | Documentation update: Function required to implement when creating a Vortex plugin |
VP-47573 | Vortex Simulator - Add a scrollbar to the Exercise Selection screen |
Fixed Issues in Vortex Studio 2024.1
Various bugs and workflow issues have been fixed during the development of Vortex Studio 2024.1:
ID | Summary |
---|---|
VP-45931 | Vulkan renderer: Node shading is inconsistent due to the normal computation |
VP-46911 | Vortex Editor - Cannot use the keyboard to copy text from the Python Output |
VP-46965 | Prismatic constraint drifts when rotating |
VP-47099 | The DeformableTerrain produces Vulkan Validation Errors |
VP-47116 | Constraint coordinates values reset when constraint is re-enabled |
VP-47119 | Unity integration - Earthwork particles can show up black |
VP-47253 | Demo Scenes - Errors and Warnings when loading UnityIntegrationDemoProject |
VP-47266 | Vortex Editor - Dragging viewport area causes duplicated render area |
VP-47325 | Vortex Editor - Vulkan Renderer - Selection/highlighting object not working in Typhoon at wireframe mode |
VP-47340 | Vulkan Renderer - The wireframe renderers produce Vulkan validation errors |
VP-47347 | Vortex Editor - Can't access a VHL input if the parent is an assembly |
VP-47376 | VortexSetup - Cannot interact with VortexSetup if sign in popup is closed |
VP-47440 | Vortex Editor - Right-clicking highlighted contact in Assembly causes crash |
VP-47449 | Vortex Editor - Application can freeze when changing tabs |
VP-47480 | Unity Integration - Unity editor always crashes the second time using Vortex Player pages |
VP-47500 | Vortex Setup - Download fails. Failed downloading package: Connection timeout error |
VP-47531 | Vortex Editor - Crash when adding contact Properties to Graphical Plotter |
VP-47565 | Vortex Editor - possible crash when switching tabs |
VP-47575 | Unity Integration - Some graphical elements of Vortex Objects are not moving correctly in Unity |
VP-47630 | Unity Integration - Graphic cables object gets set to inactive every time Vortex Scene object is refreshed |
VP-47638 | Unity Integration - Using Asset Bundle Prefabs toggles do not save |
Known Issues in Vortex Studio 2024.1
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. |