/
Vortex Studio 2023.1 Change Log

Vortex Studio 2023.1 Change Log

Owned by Marc Lievin
Feb 21, 2023
6 min read

What's new?

Vulkan Support in Vortex Editor (Tech preview)

  • Improved support of Intel and AMD GPU

 

Update to 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

 

Any computer running Vortex Studio Create or Activate must support AVX2 instructions set.

The Vortex OpenGL rendering module (named Cyclone) while still supported is now considered a legacy mode.

For advanced simulation application rendering, we recommend using the Unity or Unreal graphics together with the Vortex integration plugin.

See Integrating Unity as Graphics Renderer in a Vortex distributed simulator and Integrating Vortex Studio with Unreal Engine.

On computers equipped with multiple graphics cards (e.g., laptops with both integrated Intel card and dedicated NVIDIA graphics card), the default configuration of these systems is to auto-select the card to run the application, which might prevent Vortex Studio from running with the NVIDIA card. In the NVIDIA Control Panel, select Manage 3D Settings and change the Preferred graphics processor to High-performance NVIDIA processor and restart the Vortex application.

Some monitors have factory refresh rates set to high frequencies, i.e. 144Hz. Vortex applications will process the graphical information at 60 Hz by default, which might lead to visual artifacts. Please set the monitor refresh rate so it matches the Vortex simulation rate.

Windows Remote Desktop is not supported by Vortex Studio running in OpenGL mode.
We recommend using the Vulkan mode of the Editor.

Legacy Support of VR rendering in OpenGL mode

It is strongly recommended to use Unity or Unreal integration for advanced VR rendering support.

The extension VR system has been deprecated.

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

Python 3.8 is supported. Vortex Studio contains an embedded version of python 3.8.6.

The corresponding Python or Anaconda distribution can also be used to include more modules in the scripts.

Python 2.7.13 might still be functional on Windows but its support has been removed in Vortex Studio.

See Converting Python 2 scripts to Python 3 Dynamics Script  to upgrade your scripts

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

The CAD plugin feature is at the end of life and its support is discontinued.

The following CAD file types can be imported into Vortex Studio 2022.7 with the purchase license of the CAD Importer add-on. 

  • .step, .3dxml, .stl, .catproduct, .stp, .catpart, .vrml, .cgr, .wrl, .jt, .sldasm, .sldprt, .x_t, .x_b

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.

Academic License is not offered anymore. The previously provided Academic licenses will still be functional until expiration.

Compatibility Notice

Files created with previous versions, up to 2 years, can be used in the newest release.

We recommend that you use the "Save All Child Documents" feature of the Vortex Editor to ensure that all components are properly saved.

We also recommend that you back up your assets before migrating to the latest version. When overwritten, they will not be recoverable in their original version. Assets include any files created with the Vortex Editor, Vortex Director or programmatically with the Vortex SDK, including: code, extensions, legacy parts, assemblies, mechanisms, galleries, scenes, setup files, simulator files and any other proprietary Vortex file.

Part documents no longer exists; Opening Assemblies in the editor will automatically merge it's part document into it. Opening a part file will create an empty assembly document with the part in it.

A VHL Interface extension in an Assembly document will automatically be converted in a Linking Interface.

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.

The CAD plugin feature is no longer supported. 2022.7 is the last version supporting this feature. In order to benefit from new Vortex Studio versions until the expiration of your purchased CAD license,

2022.7 can be used to import CAD files and the generated Vortex content can be loaded in subsequent Vortex Studio versions.

  • 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

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

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.



Related content