Vortex Studio 2023.1 Change Log
- 1 What's new?
- 2 System Requirements
- 2.1 Supported Platform
- 2.1.1 Windows 11
- 2.2 Hardware Requirements
- 2.3 Software Capabilities
- 2.3.1 Mongo DB
- 2.3.2 Qt
- 2.3.3 Python
- 2.3.4 Unreal Engine Integration
- 2.3.5 Unity Integration
- 2.3.6 Supported Compiler
- 2.3.7 Simulink/MATLAB
- 2.3.8 Supported 3D model File Types
- 2.3.9 Modbus extension
- 2.3.10 SpaceNavigator mouse by 3Dconnexion
- 2.3.11 Vortex Human
- 2.3.12 Vortex Vegetation
- 2.4 Licensing
- 2.4.1 Compatibility Notice
- 2.1 Supported Platform
- 3 End-of-life Notice
- 3.1 Deprecated API
- 4 Minor Improvements in Vortex Studio 2023.1
- 5 Fixed Issues in Vortex Studio 2023.1
- 6 Known Issues in Vortex Studio 2023.1
What's new?
Vulkan Support in Vortex Editor (Tech preview)
Improved support of Intel and AMD GPU
Update to Automatic Display Placement
Improved algorithm for more reliable placement. For more information see How to Configure a System for Automatic Display Placement
System Requirements
Supported Platform
Vortex Studio 2023.1 runs on the following platforms:
Microsoft Windows 10 (x64), version 21H2.
Starting with Windows 10 2004 Update, the Windows Timer Resolution default behavior has changed.
You need to upgrade to 2021b and above in order to benefit from the code changes we made to alleviate these changes and keep the Vortex Application with the same real-time capabilities.
Your system needs a high-performance power plan for Vortex to run properly on Windows.
Windows 11
Vortex Studio is expected to run properly on Windows 11.
It will be fully supported once CM-Labs has completed a comprehensive validation. It will be announced in the release notes.
Not all features are available on the Linux operating system. See Features and Capabilities Overview for more details.
2022.7 is the last version supporting CentOS7 or equivalent. An update to the latest Ubuntu LTS and equivalent systems is in progress.
Hardware Requirements
Recommended Configuration
CPU Intel i7-9700 or better
RAM 32GB
GPU
NVIDIA GeForce RTX 2070 or better to run in OpenGL mode
Intel, NVIDIA or AMD to run in Vulkan mode
Legacy Support of VR rendering in OpenGL mode
Software Capabilities
Mongo DB
Mongo DB is the database engine used in Vortex Activate.
The version supported is Mongo DB 4.2.
Qt
Vortex Studio uses a custom version of Qt 5.15.2.
Python
Unreal Engine Integration
Vortex Studio 2023.1 supports integration with Unreal Engine version 4.26.
Unity Integration
Vortex Studio 2023.1 supports integration with Unity 2021.3.16f1 LTS.
Supported Compiler
Vortex Studio 2023.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 as a beta feature.
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
Modbus extension
The extension is no longer available.
SpaceNavigator mouse by 3Dconnexion
The extension and module are not supported in the new rendering Engine. Both are considered deprecated and will be removed in a later version.
Vortex Human
The Vortex Human library is targeted for deprecation. It will be removed in a future version.
In the editor, humans can be represented as a capsule and moved around with a script or an animation path extension.
Visualization of humans can be done in a simulator using Unity or Unreal.
Vortex Vegetation
The Vortex Vegetation library is targeted for deprecation. It will be removed in a future version.
In the editor, plants and trees can be represented as collision geometries.
Visualization of Vegetation can be done in a simulator using Unity or Unreal.
Licensing
Vortex uses RLM by Reprise Software™ for licensing.
Compatibility Notice
Between any Vortex version
Record-and-Playback as well as Keyframe files created with previous versions may not work with Vortex Studio 2022.11.
End-of-life Notice
Python 3.8 needs to be used.
Feature Snap to Surface in the Vortex Editor was removed.
Deprecated API
Class ApplicationConfigSerializer is deprecated: Use VxObjectSerializer class.
Minor Improvements in Vortex Studio 2023.1
In addition to features documented in the what's new, minor improvements have been made during the development of Vortex Studio 2023.1:
ID | Summary |
---|---|
VP-45140 | Update Unity to 2021.3.16f1 LTS |
VP-45155 | Vulkan Renderer: sRGB conversion inconsistency Nvidia/AMD/Intel |
VP-45157 | nVIDIA GeForce RTX 3070 Ti Support |
VP-45158 | nVIDIA RTX A5000 Support |
Fixed Issues in Vortex Studio 2023.1
Various bugs and workflow issues have been fixed during the development of Vortex Studio 2023.11:
ID | Summary |
---|---|
VP-44439 | HookGroupExtension: Some assets seem to remain asleep when trying to hook them |
VP-44983 | Output in VHL interface exposing a field never changes on slave |
VP-45010 | Starting a Unity simulator does not always start VortexUnityApp.exe when it needs |
VP-45037 | Vortex Editor: Grid transform reset does not work with the Vulkan Renderer |
Known Issues in Vortex Studio 2023.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. |