Vortex Studio 2022.2 Change Log



What's new?

Content Creation

Assembly Links are used to connect two Linking Interfaces together which creates the binding between two Assemblies. The result will establish two levels of connection between the Linking Interfaces: a data connection as well as a dynamic connection with the help of an Attachment. See Assembly Link for more details.

Interfaces design

VHL and linking interface creation user interface has been updated to support containers.

Python 3

The Python 3 Dynamics extension is now available on the Linux platform. Python 2 is no longer functional on Linux. You will need to convert your content for it to work on that platform. See Converting Python 2 scripts to Python 3 Dynamics Script.

The Python 2 Vortex tutorials were removed.


Unity Integration

Several changes were made to improved the overall performance and memory management. 

Documentation Updates

Documentation on how to configure a Simulator has been updated : Simulator Setup User Guide

Documentation on how to use the Vortex Application SDK has been consolidated : Integrating Vortex Studio using the SDK - Making a Vortex Application

Vortex Studio on Linux, supported features, installation, usage has been updated : Vortex Studio on Linux

A Tutorial on how to script automated tests with Vortex Content has been added : Automated Vortex Content Testing with Python

System Requirements

Supported Platforms

Vortex Studio 2022.2 runs on the following platforms:

  • Microsoft Windows 10 (x64), version 21H2.
  • Linux CentOS 7 or equivalent.

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.

Not all features are available on the Linux operating system. See Features and Capabilities Overview for more details.

Hardware Requirements

Minimum ConfigurationRecommended Configuration
  • CPU Intel i7-4700 or equivalent
  • RAM 16GB
  • GPU NVIDIA compatible graphics card
  • CPU Intel i7-9700 or better
  • RAM 32GB
  • GPU NVIDIA GeForce GTX 2070 or better

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

Supported Graphics Cards by the OpenGL rendering module

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 Using Unity as Graphics Renderer and Integrating Vortex Studio with Unreal Engine.


Vortex Studio 2022.2 has been extensively tested with NVIDIA GeForce RTX 3060 TI, RTX 3060, RTX 2070 and GTX 1070 cards for high performance rendering with 466.27 and 461.40 WHQL drivers.

Other GTX and RTX graphic cards listed in the NVIDIA release notes work with Vortex Studio, however some performance or rendering degradation may occur.

The 466.27 driver may cause issues when running many graphics simulations concurrently on the same computer. While this was only observed in extreme cases, the driver can be downgraded to 461.40 if needed.

Vortex Studio Create 2022.2 has also been tested with NVIDIA Quadro P5000 graphics cards.

Vortex Studio 2022.2 supports AMD and Intel graphics cards as a tech preview with limited feature set.

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 another remoting application that uses the remote graphics card for rendering, e.g. VNC.


Supported VR Hardware in OpenGL rendering

Vortex Studio 2022.2 supports as a legacy mode the following VR hardware via the OpenVR protocol:

  • HTC Vive Pro

A Steam account is needed to configure and use the VR hardware in a Windows 10 environment.

Your graphics card must also meet minimal requirements for VR performances.

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 3.8 has to be used. Python 2.7.13 might still be functional on Windows but support will be removed in an upcoming version.

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

Unreal Engine Integration

Vortex Studio 2022.2 supports integration Unreal Engine version 4.26.

Unity Integration

Vortex Studio 2022.2 supports integration with Unity 2020.3.20f1.

Supported Compiler

Vortex Studio 2022.2 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.

Licensing

Vortex uses RLM by Reprise Software™ for licensing.

Altair Partner Alliance (APA) Licensing

Altair license server supported version is 14.5.1.

Vortex Studio Activate is not included in the Altair APA licensing support.

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 following CAD file types can be imported into Vortex Studio with the purchase of the CAD Importer add-on. 

The CAD Importer add-on is a paid add-on. Contact your CM Labs representative for more information.

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

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.

Between any Vortex version

Record-and-Playback as well as Key frame files created with previous versions may not work with Vortex Studio 2022.2.


From any version of Vortex Studio Academic

Note that content saved in Vortex Studio Academic cannot be opened with commercial Vortex Studio licenses such as Create or Activate.

Academic can open and run content created with other licenses.

End-of-life Notice

  • Python 3.8 should be used. Python 2.7.13 might still be functional on legacy systems.

Minor Improvements in Vortex Studio 2022.2

In addition to features documented in the what's new, minor improvements have been made during the development of Vortex Studio 2022.2:

IDSummary
VP-42012There is a dynamics only version of simapp.vxc, simapp_DynamicsOnly.vxc meant to run on Linux.
VP-43059Vortex Editor: Enumerations numerical values are now shown in the Property Browser to ease scripting
VP-43111Is is possible to configure the extra module paths to locate Python 3 packages that are not in the Interpreter path
VP-43153Vortex Editor: Opening a python script file: Python 3 script file can be open in their external editor from the Dynamics Script Extension contextual menu. Any field of type filename can be opened in an external editor from the field's drop-down menu.

Fixed Issues in Vortex Studio 2022.2

Various bugs and workflow issues have been fixed during the development of Vortex Studio 2022.2:

IDSummary
VP-42990Vortex Editor: Warnings caused by extensions Added Multiples Times. The mouse spring manipulator extension must now be added to a setup file for the feature to be enabled.
VP-43011Vortex Editor: UIOjectManager warnings caused by object leaks
VP-43166Vortex Editor: Interface UI multi select does not work with Shift when Shift key is released
VP-43169Vortex Setup: documentation link does not work
VP-43183Linking Interface: assemblyLinkInformation.attachmentPoint not accessible in Python
VP-43195Vortex Editor: Cannot add Soil Mass Sensor to Generic Bucket Extension within the Assembly Environment
VP-43199Vortex Editor: missing category icons in toolbox for Assembly document
VP-43201VortexUnityApp: Performance slowdown after extended use
VP-43205Console - Python Report: If the report log PNG contains transparency, the result is a black square.
VP-432102022.1 RTM documentation has instances of 2022.01 instead of 2022.1 typed in.
VP-43230DirectX: Crash when loading multiple scenes.
VP-43231DirectX: Crash when reloading shaders.
VP-43232Vortex Editor : Tire Type in assembly can't be placed in folder

Known Issues in Vortex Studio 2022.2

ID

Summary

Workaround
VP-39136

Vortex Editor shows black screen when running on a laptop with NVIDIA GPU with Optimus technology.

Manually choose the OpenGL renderer in the Vortex Editor options. Alternatively, set an external monitor as primary.
VP-41437When 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.

Deprecations in Vortex Studio 2022.2

see End of Life Notice