This information is intended for users of Vortex Studio and Unreal Engine who want to integrate Vortex Studio simulation capabilities with Unreal, within a single process. This integration SDK is useful for single process simulation, VR, and using advanced blueprints logic in Unreal.

To use the following guide, you must be familiar with Vortex mechanisms, Vortex Graphics Galleries, and the Unreal Editor.

In the following documentation, you will be able to simulate Vortex mechanisms just like any other assets in an Unreal level.

With the Vortex Studio Plugin for Unreal Engine, the Unreal Editor lets you connect to parameters that you expose in Vortex Studio.

Any Vortex Studio simulation parameter can be sent to a function in an Unreal blueprint (get/set) and included in your Unreal level.

Vortex Studio automatically detects landscape components that you create in Unreal around a Vortex vehicle. A corresponding height field is created and streamed in Vortex Studio at run time. To monitor contacts and collisions during simulation, you can show the height field at the same time using the Vortex Studio Remote Debugger application.

During the simulation, Vortex Studio sends information about the position and orientation of each body to the Unreal Engine. Parameters and outputs can be accessed via the mechanism's interface. To ensure smooth gameplay with accurate synchronization and realistic movements, Vortex Studio sends information about the position and orientation of each body to the Unreal Engine. Parameters and outputs that you expose using a VHL interface let you control the Mechanism in Unreal.

Vortex Studio manages external devices, such as motion platforms and CANopen-compliant devices for controlling vehicles and enriching simulation.

Getting started...

Installing the Vortex Studio Plugin
Running a Sample Project
Organizing Vortex Studio Assets for a New Project
Creating Your First Project
Importing Mechanisms into Unreal
Enabling Vortex Simulation In Unreal
Packaging Your Project

Tell me about...

Organizing Assets
Managing the Framerate Between Vortex Studio and the Unreal Editor
Get/Set Vortex Mechanisms IO
Debugging
Supported Colliding Objects in Unreal
Mapping Contact Materials
Viewing Log Files
Limitations

Installing the Vortex Studio Plugin

Installing the Vortex Studio Plugin involves downloading the plugin from the Unreal marketplace and configuring basic parameters.

Prerequisites

To use the Vortex Studio for Unreal Engine 4 plugin, you must have Vortex Studio and Unreal Engine 4.26.

Download the plugin from the Unreal Marketplace and install it following these steps:

IMPORTANT

You must have a valid Epic games user account to download the plugin from the Unreal Marketplace.

To install the Plugin with the Epic Games Launcher

Open the Epic Games Launcher and login using your account information.
Click the Marketplace tab.
In the search bar, type Vortex.
The Vortex Studio plugin appears in the list.
Click Vortex Studio plugin and click on Install to Engine.
The Vortex Studio plugin now appears in your Unreal projects

To install the Plugin from the 7z File

Open the folder Plugins at the following address <Unreal Engine Installation Folder>\Engine\Plugins\.
If you see a subfolder named VortexPlugin remove it.
Copy the 7z named Vortex_Studio_Unreal_Plugin_[ReleaseNumber].7z into the Plugins folder.
In the 7-zip context menu, select Extract Here.
Delete the 7z file.

How to rebuild the Vortex Studio Plugin to a later version of Vortex Studio

The Vortex Studio Plugin available on the Epic Games Launcher might not match the version of your Vortex Studio installation. It is however possible to update the plugin's version following these steps.

Prerequisites

Unreal Engine version 4.26: We cannot guarantee that the plugin will work with a version other than 4.26
Microsoft Visual Studio: In order to compile the code, we recommend having Microsoft Visual Studio 2019.
Vortex Studio: A Vortex Studio installation is mandatory for the update and for the plugin to work with Unreal Engine.

How to update the plugin step-by-step

Make sure that you currently have the Vortex Studio plugin from the Marketplace. If you don't, install it from the Marketplace page or from the Vault section of your library if it is there:
Open your Windows Explorer and move to the folder where the Vortex Studio plugin was installed. For example, if Epic Games is installed at the default location, the path should be: C:\Program Files\Epic Games\UE_4.26\Engine\Plugins\Marketplace ;
Inside the Marketplace folder, copy the folder VortexPlugin and copy it somewhere else such as in your Documents or on the Desktop. The important part is that it isn't inside the Epic Games repository.
In your new location, open the VortexPlugin folder. There, delete both the Binaries and the Intermediate folders. The end result should look like this:
From there, go in the folder named <Work Folder>\VortexPlugin\Source\ThirdParty\VortexStudio\Win64 . This is where we will have to change some files.
Open a new Windows Explorer and open your Vortex Studio installation. The path should be C:\CM Labs\Vortex Studio <vortex version>
The first step will be to copy and replace the library. In <Vortex Studio Installation>\lib, copy VortexIntegration.lib and copy it inside <Work Folder>\VortexPlugin\Source\ThirdParty\VortexStudio\Win64\lib. You will have to replace the existing library.
The second step will be to copy the header files. In <Vortex Studio Installation>\include\VortexIntegration, copy all files and move them to <Work Folder>\VortexPlugin\Source\ThirdParty\VortexStudio\Win64\include\VortexIntegration . This will replace all files except the one named Version.h.
Finally, open the file Version.h in <Work Folder>\VortexPlugin\Source\ThirdParty\VortexStudio\Win64\include\VortexIntegration and open the file VxVersion.h from <Vortex Studio Installation>\include\Vx. Each field of Version.h needs to be replaced to mirror the defined fields of VxVersion.h:
Now that the files are updated, we need to compile the plugin. Open a CMD prompt and move to your Unreal Engine install in the batch file folder C:\Program Files\Epic Games\UE_4.26\Engine\Build\BatchFiles
From here, run this command and replace the path location with your own:
```
c:\Users\username\Desktop\vortex>"C:\Program Files\Epic Games\UE_4.26\Engine\Build\BatchFiles\RunUAT.bat" BuildPlugin -Plugin="c:\Users\username\Desktop\vortex\VortexPlugin\VortexPlugin.uplugin"
-Package "c:\Users\username\Desktop\vortex\output" -CreateSubFolder -VS2019
```
Where:
1. RunUAT.bat is the batch file to run;
2. BuildPlugin is the action;
3. -Plugin is the path of the uplugin file from your new plugin folder;
4. -Package is the output folder where your new plugin will be created. This must be outside the Unreal Engine directory;
5. -CreateSubFolder is to specify how to create the plugin hierarchy;
6. -VS2019 is to specify the compiler. This may change depending on your Microsoft Visual Studio installation.
Now go back into your Epic Games application and uninstall the Vortex Studio plugin.
Copy the folder VortexPlugin from your work folder into the plugin repository of Unreal Engine at this location: C:\Program Files\Epic Games\UE_4.26\Engine\Plugins
Close and restart Epic Games. You should now be able to use the Vortex Plugin with your current version.

Running a Sample Project

For convenience, CM Labs offers a sample project that you can use to understand the different features of the Vortex Studio integration with Unreal. You can also use it as a starting point for your own projects.

To download the sample project files do the following:

In a web browser go to https://cm-labs.exavault.com/share/view/1s3xe-amykk3cw
To begin the download, click the filename of the sample project: Vortex_Studio_for_Unreal_Forklift_Sample_[ReleaseNumber].7z and extract the content on your computer.
Open the Unreal Engine 4.26 and click the Launch button.
In the Unreal Project Browser, click Browse and navigate to the extracted sample files.
Open the ForkliftSim_uproject file.
The project opens in the Unreal Editor.
NOTE: It can take several minutes for the project and to load for the first time.
To start the simulation, press the Play button.
You can use a Direct Input game controller to control the forklift.

Organizing Vortex Studio Assets

This section assumes that you already have a good understanding of Vortex Studio Editor Documents.

The Vortex Studio plugin lets you import Vortex mechanisms to an Unreal project.

To create a valid Unreal project using Vortex Studio, you must copy the Vortex assets you want to use in your new Unreal project under the Content directory for the project. Vortex assets include files with the following formats:

*.vxmechanism (Mechanism Document)
*.vxassembly (Assembly Document)
*.vxgraphicgallery (Graphics Gallery Document)
*.vxc (Setup Document)
*.vxmaterials (Material Table)

Example

In this example, you have the following folder hierarchy for a Vortex forklift mechanism:

Forklift
- Dynamics
  - Forklift.vxmechanism
  - Forklift_Assembly.vxassembly
- Graphics
  - Forklift2016.vxgraphicgallery

To build a valid Unreal project, you must move the same folder structure to a sub-folder of the Content folder for your Unreal project. The structure of your Unreal project would appear as follows:

MyProject
- MyProject.uproject
- Config
  - ...
  - ...
- Content
  - Vortex_Mechanisms
    - Forklift
      - Dynamics
        Forklift.vxmechanism
        Forklift_Assembly.vxassembly
      - Graphics
        Forklift2016.vxgraphicgallery

It is easier to configure packaging settings for the project when all your Vortex assets exist under single directories in the project Content folder, with other assets that the Unreal Editor does not recognize.

Creating Your First Project

Bringing your first Vortex Studio project into Unreal involves verifying that the plugin is enabled, restarting the application, and verifying settings for the project with the plugin.

About Vortex Studio Project Settings

You can customize several settings for your project in the Unreal Editor from the Project Settings window.

Specifically, you can customize the following settings for your project:

Anytime you change a setting, you must restart the application before they can take effect.

Category	Setting Name	Description
	Data Provider's Path	This setting is for advanced usage. Specifies a path (must be under the `Content` directory for the project) where some simulation data will be stored (for instance, Control Presets). Default: None.
Application Setup	Use Default	When set to true, the Vortex Studio simulation in the Unreal application uses this default Application Setup Document packaged with Vortex Studio: `C:\CM Labs\Vortex Studio [ReleaseNumber]\resources\config\VortexIntegration.vxc` Default: True.
Application Setup	Custom Application Setup	This setting is only used when Application Setup->Use Default is false. It allows using a custom Application Setup Document for your Unreal project. It is strongly recommended to use the default Application Setup Document for Vortex integrations as a starting point. The default file is under: `C:\CM Labs\Vortex Studio [ReleaseNumber]\resources\config\VortexIntegration.vxc` Your custom Application Setup Document must reside under the `Content` folder for the project. It should be under a specific sub-folder since it will be needed to package this Non-Asset folder when packaging your Unreal project. Default: None (not used)
Material Table	Use Default	When set to true, the Vortex Studio simulation within Unreal will use this default Material Table packaged with Vortex Studio: `C:\CM Labs\Vortex Studio [ReleaseNumber]\resources\DynamicsMaterials\default.vxmaterials` Default: True
Material Table	Custom Material Table	This setting is only used when Material Table->Use Default is false. It lets you specify a custom Material Table for your Unreal project. It is strongly recommended that you use the default Material Table for Vortex Studio integrations as a starting point. The default file is under: `C:\CM Labs\Vortex Studio [ReleaseNumber]\resources\DynamicsMaterials\default.vxmaterials` Your custom Material Table must exist under the `Content` folder for your project. It must exist under a specific sub-folder since the application uses it to package this `Non-Asset` folder when packaging your Unreal project. Default: None (not used)
Static Collision	Enable Landscape Collision Detection	If true, Unreal Landscapes will be transferred to Vortex Studio at runtime, using the underlying Vortex terrain paging system, so your mechanisms can collide with them. For additional parameters that allow tuning the performance of the terrain paging system, please see the Static Collision → Terrain Paging category below. Default: True
	Enable Mesh Simple Collision Detection	If true, Collision On a Simple Shaped Mesh for all Unreal Static Meshes will be transferred to Vortex Studio at runtime, using the underlying Vortex terrain paging system, so your mechanisms can interact with them. Note that Vortex Studio always uses the colliding geometry (simple or complex) that PhysX would use in Unreal. For additional parameters that allow tuning the performance of the terrain paging system, please see the Static Collision → Terrain Paging category below. Default: True
	Enable Mesh Complex Collision Detection	If true, Collision On a More Complex Mesh for all Unreal Static Meshes will be transferred to Vortex Studio at runtime, using the underlying Vortex terrain paging system, so your mechanisms can interact with them. Note that Vortex Studio always uses the colliding geometry (simple or complex) that PhysX would use in Unreal. For additional parameters that allow tuning the performance of the terrain paging system, please see the Static Collision → Terrain Paging category below. Default: True
	Material Mappings	Allows associating an Unreal Physical Material to a Vortex Contact Material by name. This lets you specify which contact material a Vortex collision uses for computation purposes. The application only uses these associations when at least one of the following settings is enabled: Enable Landscape Collision Detection Enable Mesh Simple Collision Detection Enable Mesh Complex Collision Detection Default: None.
Static Collision → Terrain Paging Landscape	Tile Size XY	Size in meters, in world X and Y direction, of the square tiles used by the landscape terrain pager for landscape collision queries and caching. Landscape component will be queried by the terrain pager in tiles of the given size around the dynamically moving Vortex mechanisms. Tiles will be cached and only queried again if not already present in the cache in order to reduce query time, and in order to produce consistent, non-duplicate collision geometries in the Vortex simulation when multiple moving objects are operating in close proximity. Use Tile Size XY value around the Landscape Component size for better results. For more information on this parameter and the terrain paging system underlying the Unreal integration, refer to Integrating Vortex Studio using the VortexIntegration API. Default: 50 meters
	Look Ahead Time	Specifies the time, in simulation seconds, the terrain pager should forecast ahead. All the terrain to be reached within the specified time, at the current velocity, will be requested. If the terrain paging system experiences slow downs when navigating, consider reducing this parameter. For more information on this parameter and the terrain paging system underlying the Unreal integration, refer to Integrating Vortex Studio using the VortexIntegration API. Default: 1 second
	Safety Band Size	Specifies the distance (in meters) to grow the paged region by, as a safety band, in order to account for objects changing direction. If the terrain paging system experiences slow downs when navigating, consider reducing this parameter. For more information on this parameter and the terrain paging system underlying the Unreal integration, refer to Integrating Vortex Studio using the VortexIntegration API. Default: 1 meter
Static Collision → Terrain Paging Mesh	Tile Size XY	Size in meters, in world X and Y direction, of the square tiles used by the terrain pager for Mesh collision queries and caching. Terrain will be queried by the terrain pager in tiles of the given size around the dynamically moving Vortex mechanisms. Tiles will be cached and only queried again if not already present in the cache in order to reduce query time, and in order to produce consistent, non-duplicate collision geometries in the Vortex simulation when multiple moving objects are operating in close proximity. If the terrain paging system experiences slow downs when navigating on a complex terrain with many obstacles (e.g., trees) consider reducing this parameter. Note that a too drastic reduction (e.g., a value of 1 meter) can in itself lead to slowdowns. A balance can be found through experimentation. For more information on this parameter and the terrain paging system underlying the Unreal integration, refer to Integrating Vortex Studio using the VortexIntegration API. Default: 50 meters
	Look Ahead Time	Specifies the time, in simulation seconds, the terrain pager should forecast ahead. All the terrain to be reached within the specified time, at the current velocity, will be requested. If the terrain paging system experiences slow downs when navigating on a complex terrain with many obstacles (e.g., trees) consider reducing this parameter. For more information on this parameter and the terrain paging system underlying the Unreal integration, refer to Integrating Vortex Studio using the VortexIntegration API. Default: 1 second
	Safety Band Size	Specifies the distance (in meters) to grow the paged region by, as a safety band, in order to account for objects changing direction. If the terrain paging system experiences slow downs when navigating on a complex terrain with many obstacles (e.g., trees) consider reducing this parameter. For more information on this parameter and the terrain paging system underlying the Unreal integration, refer to Integrating Vortex Studio using the VortexIntegration API. Default: 1 meter

To Create a New Unreal Project Using the Vortex Studio Plugin

Open the Unreal Engine 4.26 and click the Launch button.
In the Unreal Editor, follow steps in Unreal documentation to create a new project.
In the upper left, click Edit and then click Plugins.
Confirm that the Vortex Studio plugin is installed.
To enable the plugin, click to select Enabled.
In the lower right, click Restart Now.
The project re-opens with the Vortex Studio plugin enabled.
Save the project to permanently enable the plugin.

Managing the Frame Rate Between Vortex Studio and the Unreal Editor

By default, new Unreal projects use a variable frame rate. The Vortex Studio integration in Unreal Engine uses a fixed frame rate of 60 Hz. If you do not change the default settings, the simulation will run at unrealistic speeds.

IMPORTANT

To maintain fidelity and realism in the simulation, you must configure project settings so that Unreal Engine and Vortex Studio both use a fixed frame rate.

Example: Setting the Frame Rate in Vortex Studio and the Unreal Engine

In this example, you want a simulation to run at 90 Hz.

To set the Frame Rate in the Unreal Editor, do the following:

In the Unreal Editor, open your project.
Click Edit and then click Project Settings.
In the Project Settings window, under the Engine section, click General Settings.
Scroll down to the Framerate section and do the following:
1. Click to select the Use Fixed Frame Rate checkbox.
2. In the Fixed Frame Rate field, specify 90.00.
Save the settings and restart the project.

To set the Frame Rate in the Vortex Studio Editor, do the following:

Prerequisite: You must have a custom Simulator Setup User Guide (not the default one provided with Vortex Studio). For more information, see About Vortex Studio Project Settings.

Make sure the custom application setup document is saved in the Content directory of your Unreal project.

In the Vortex Studio Editor, open the custom Application Setup Document for this project.
In the Explorer panel, click Setup.
On the right of screen, in the Properties panel, set the Simulation Frame Rate value to 90.00.
To save your changes, click the Save button.
When you restart the Unreal Editor, validate that the settings have been correctly configured.

Importing Mechanisms into Unreal

When you import a mechanism from Vortex Studio to the Unreal editor, the application identifies all Graphics Galleries (.vxgraphicgallery) in the mechanism file (.vxmechanism). The application imports all textures, materials, and meshes from the galleries as standard Unreal assets in the directory you specify.

Unreal creates a new Actor blueprint subclass to represent the Vortex Studio mechanism. You can use the new blueprint class to instantiate your Vortex Studio mechanism in an Unreal map. The class accomplishes the following things:

It replicates the Vortex Studio graphics node hierarchy using the imported graphics galleries and uses it to create a hierarchy of corresponding Unreal Scene and Static Mesh components.
It automatically updates the position and orientation of relevant Unreal Scene and Static Mesh components when Vortex Studio parts are moving.
When a Vortex Studio part moves, the blueprint analyzes connections between parts and graphics nodes in Vortex Studio (typically under the Skin connection container) to detect which components move.

The Unreal Editor does not expose the automatic mapping which occurs.

The Skin connection container and all relevant graphic nodes in Vortex Studio are required for the integration and must not be deleted.

Importing a Vortex Studio mechanism into Unreal involves preparing your Vortex Studio project, specifying project settings in the Unreal Editor, and creating a new project blueprint.

Preparing your Vortex Studio Project for Import

When you import a mechanism from Vortex Studio, Unreal creates a version of each material in the Graphics Gallery. Each material that Unreal creates becomes a material instance of "BaseGraphicsMaterial". This material uses a single texture, the first albedo texture defined in the original material, and configures it to use UV set 0. The material instance uses no other textures or material inputs (such as Emission, Occlusion, Specular, or Gloss). Unreal imports every texture currently in the Graphics Gallery.

After you import a mechanism for Vortex Studio to the Unreal Editor, you can modify the graphics gallery contents and the Unreal Editor will automatically update behavior in your project there. Renaming any meshes in Unreal Editor breaks the related Unreal mesh <=> graphics node mapping. If a name changes, you must rename the mesh in Unreal Editor to the name it had when you imported the project.

To Import a Mechanism from Vortex Studio to the Unreal Editor

To add Vortex Studio mechanism to your Unreal project, do the following:

Make sure your Vortex Studio assets are 3302964707 in the Content folder for your Unreal project.
In the Unreal Editor, select the directory in the Content Browser where you will import your Vortex mechanism, including textures, material instances static meshes, and a VortexMechanism Unreal asset.
Option 1:
1. Drag and drop the .vxmechanism file you want to import from Windows Explorer into the Content Browser.
2. A pop-up window for selecting a folder appears
3. After selecting a folder to save the generated blueprint, the application imports the mechanism.
Option 2
1. Right-click on the directory in the Content Browser and then click Import to /Game/...
2. A pop-up window for selecting a folder appears.
3. Select the .vxmechanism file you want to import and click Open.
4. The application imports the mechanism and generates a blueprint.
Select a folder for the new blueprint class and then click OK.
Drag-and-drop the generated mechanism blueprint from the Content Browser into the viewport.
You can open the blueprint to get or set additional values from Vortex Studio. The blueprint appears empty while the application maps the meshes and transforms from Vortex.

(Optional) To Take Control of the New Actor

To take control of the new Actor in Unreal, do the following:

In the Blueprint Editor for your new Actor, on the toolbar click File and then click Reparent Blueprint.
In the Reparent Blueprint list, search for Pawn and then click to select it.
To verify the new parent class for your blueprint, use the mouse to hover over the root element of the Components panel.
The parent class of the blueprint is now Pawn.
To add a camera to the blueprint, click the +Add Component button and select the camera you want to add from the menu.
Click Compile and then click Save.
In the Components panel, click to select the new camera. Then, switch the center view to Viewport and use manipulators to move your camera to the correct location.
When the camera is added and in the correct position, in the Components panel, click select the root element (the self element).
On the right of the screen, in the Details panel, scroll down to the Pawn category and assign Auto Possess Player to a valid player ID. For example, Player 0.
Compile and save the blueprint.
In the main window of the project, click the Save Current button.
Now, because the Pawn blueprint is automatically possessed when the simulation begins, the 3D view should automatically display what the Blueprint camera sees when you press the Play button.

Enabling Vortex Simulation

For simulation with Vortex content to function correctly, your Unreal Level Blueprint must include functions to start and stop Vortex simulation in the context of your Unreal gameplay.

To add these functions, do the following:

Open your Level Blueprint:
In the Event Graph, find the EventBeginGameplay item.
In the EventGameplay item, use the left mouse button to click the Exec icon and drag it to the right and then release the mouse button.
A pop-up window for adding a function appears
In the pop-up window, scroll to the Vortex →Application category and click Start Simulation.
In the Event Graph area, right-click anywhere on the empty space (not on a node).
In the search bar of the blueprint actions pop-up window that appears, type end play and then select the search result Event End Play.
Use the same process to add a Stop Simulation function. Click the Exec icon on the new Event End Play and drag it right before you release the mouse button. Then, add the Stop Simulation function.
Compile and save the Level Blueprint.
To save your map, press the Save Current button in the main Unreal Editor interface.

To make sure that the Vortex simulation can start correctly, always press the Save Current button before you press Play. This of course will also save to disk any changes to your map.

You can call the Start Simulation and Stop Simulation functions at any time, but you must make sure the Vortex simulation has completely stopped when you stop the Unreal simulation. All Vortex mechanisms must be loaded when the Vortex simulation is not running.

Get/Set Vortex Studio Mechanism Inputs and Outputs (IO)

After you import Vortex mechanisms to an Unreal project, you must get/set Vortex mechanism inputs and outputs (IO) from the Unreal simulation.

Available IO for mechanisms are defined by the following mechanism interfaces:

Outputs from these interfaces can be read from Unreal, while inputs can be set with new values from the Unreal simulation.

For this purpose, a set of useful blueprint functions are exposed by the Vortex Studio plugin. To quickly find them, type VHL in the action search bar:

Each function must have a Mechanism Component as a target. This component is automatically created under the blueprint class created when you import a Vortex mechanism (see Importing Mechanisms into Unreal).

The following functions are available to you:

Blueprint Function	Description
From Vortex to Unreal
Get VHLField as Bool	Allows to search for a specific VHL/Control interface's output field on the target mechanism. This function assumes the desired field is a boolean field and will return its value as a bool.
Get VHLField as Float	Allows to search for a specific VHL/Control interface's output field on the target mechanism. This function assumes the desired field is a double field and will return its value as a float.
Get VHLField as Integer	Allows to search for a specific VHL/Control interface's output field on the target mechanism. This function assumes the desired field is an integer field and will return its value as an int32.
Get VHLField as String	Allows to search for a specific VHL's output field on the target mechanism. This function assumes the desired field is a string field and will return its value as an FString.
Get VHLField as Transform	Allows to search for a specific VHL's output field on the target mechanism. This function assumes the desired field is a Matrix44 field and will return its value as an FTransform.
Get VHLField as Vector 2	Allows to search for a specific VHL's output field on the target mechanism. This function assumes the desired field is a Vector2 field and will return its value as an FVector2D.
Get VHLField as Vector 3	Allows to search for a specific VHL's output field on the target mechanism. This function assumes the desired field is a Vector3 field and will return its value as an FVector.
Get VHLField as Vector 4	Allows to search for a specific VHL's output field on the target mechanism. This function assumes the desired field is a Vector4 field and will return its value as an FVector4.
From Unreal to Vortex
Set VHLField as Bool	Allows to search for a specific VHL/Control interface's input field on the target mechanism. This function assumes the desired field is a boolean field and will set its value from a bool.
Set VHLField as Float	Allows to search for a specific VHL/Control interface's input field on the target mechanism. This function assumes the desired field is a double field and will set its value from a float.
Set VHLField as Integer	Allows to search for a specific VHL/Control interface's input field on the target mechanism. This function assumes the desired field is an integer field and will set its value from an int32.
Set VHLField as String	Allows to search for a specific VHL/Control interface's input field on the target mechanism. This function assumes the desired field is a string field and will set its value from an FString.
Set VHLField as Transform	Allows to search for a specific VHL/Control interface's input field on the target mechanism. This function assumes the desired field is a Matrix44 field and will set its value from an FTransform.
Set VHLField as Vector 2	Allows to search for a specific VHL/Control interface's input field on the target mechanism. This function assumes the desired field is a Vector2 field and will set its value from an FVector2D.
Set VHLField as Vector 3	Allows to search for a specific VHL/Control interface's input field on the target mechanism. This function assumes the desired field is a Vector3 field and will set its value from an FVector.
Set VHLField as Vector 4	Allows to search for a specific VHL/Control interface's input field on the target mechanism. This function assumes the desired field is a Vector4 field and will set its value from an FVector4.

Additional variations of the Get VHLField as ... function are available, but they are reserved for exceptional circumstances.

All functions have similar structures:

You must connect the Exec input to the correct Event tick. For example, if the data is get/set every tick, then the Exec of Event Tick must connect to the Exec input for the new function.

Get VHLField as ...

Input	Target	Specifies on which Mechanism Component to call this function. The Mechanism Component refers to the specific `.vxmechanism` file from Vortex.
Input	VHLName	The name of the VHL/Control interface to search for.
Input	Field Name	The name of the output field to search for.
Output	Value	The returned value (the type differs for each variation of the Get VHLField as ... function).

Set VHLField as ...

Input	Target	Specifies on which Mechanism Component to call this function. The Mechanism Component refers to the actual .`vxmechanism` file from Vortex.
Input	VHLName	The name of the VHL/Control interface to search for.
Input	Field Name	The name of the input field to search for.
Input	Value	The value to assign to the specified field (the type differs for each variation of the Set VHLField as ... function).

Earthworks Systems

As a Vortex Studio and Unreal Engine user, you can combine the best of both worlds and use Vortex Studio Earthworks as your soil simulation in Unreal Engine. While an Unreal Engine Landscape can be sculpted and edited in Unreal Editor, it is usually a static and non-deformable object during the simulation. The Vortex Studio Earthwork Systems allows you to make otherwise rigid terrain surfaces deformable within a limited area. Earthmoving operations such as digging, trenching, filling, etc generate particles and respect mass conservation.

To do this, you will want to create one (or many) Deformable Terrains in Vortex Studio, as well as cutting tools or buckets, and import them in Unreal Engine. This guide will help you put it together for the following Earthworks constructs: Soil Bin, Deformable Terrain, Soil Particles. Refer to official Vortex Studio documentation (Earthwork Systems Tutorials) for the remaining Earthworks features: Soil Layer, Soil Emitter, Soil Culling Geometry, Soil Mass Sensor, Soil Materials, Bucket, Blade, Generic Bucket. They work without any specific adaptation needed for Unreal Engine.

A single Soil Particle extension is responsible for all particles generated in a simulation from any deformer on any Soilbin or Deformable Terrain. A single Soil Materials extension is responsible for all soil materials present in a simulation. With this in mind, a single Vortex Mechanism should contain a Soil Particles and Soil Materials extension and this Mechanism should be added once to a given Unreal level. Refer to Unreal Engine documentation about Levels if you are not familiar with them (https://docs.unrealengine.com/en-US/Engine/Levels/index.html).

Soilbin

As a Vortex Studio and Unreal Engine user, you can see your Vortex Studio Soilbin and interact with it in Unreal Engine. Here are the steps:

	Information	Media
1	How to view an Earthworks Soilbin in Unreal Engine Before you start, make sure that your Soilbin is correctly designed in Vortex Studio. You cannot make changes to the Soilbin extension from the Unreal Editor, and changes to inputs, outputs, and parameters that you make in Vortex Studio can cause problems in Unreal if they affect the mapping to the Procedural Mesh Component in the Unreal blueprint.
2	Expose your Soilbin and its World Transform to VHL using the Vortex Editor. For the proper position of the origin of the Soilbin in Unreal, expose the Outputs. World Transform of the Dynamics Soil Bin. This will be used from the blueprint as a position for the Procedural Mesh Component. To expose it, drag the field onto the VHL Interface's "Outputs" row.
3	To expose a Soilbin's shape so the Unreal object (created later in this guide) can conform to the Soilbin visuals, using Vortex Editor navigate to the VHL editing screen. Add an extension pointer output field by pressing '+' next to the "Outputs" column title. Keeping the VHL editing screen open navigate to your Soilbin in the Explorer tree. Select it and drag it to the "Data" column of the just created extension pointer output on the VHL editing screen. You will need to remember the names of these two outputs when working in Unreal, so it might be helpful for you to rename them.
4	In your Unreal project, open Plugins. Then, enable the 'Procedural Mesh' plugin. It can be found in the Built-In" pulldown.
5	To prepare Unreal Editor to receive Soilbin data from Vortex, create a 'Procedural Mesh' component in a blueprint relevant to the Soilbin (truck, ground, pile, etc).
6	The 'Procedural Mesh' must be created and updated at runtime from the Vortex data. Here is a breakdown of the Blueprint image shown next to this step: Set the Material on the mesh Set the Transform of the Procedural Mesh based on data from Vortex Create the mesh with the Height Field data from Vortex Recreate the mesh when the Heightfield size changes or Update it if the size didn't change Optional: An empty Soil Bin will likely create graphical artifacts as the bottom face of the container exactly overlaps with the flat height field. To avoid this, you can raise or lower the Transform received from Vortex by a small amount.

Soil particles

When simulating any Earthworks System in Unreal Engine, you will want to see a visual representation of the dug soil (inside or falling from a bucket for example). In Vortex Studio, this dug soil is represented by the Vortex Studio Particle extension. Ensure that your particle system is set up with particle culling and has a reasonable maximum particle count. Refer to official Vortex Studio documentation (Earthwork Systems Tutorials). Once that is set up, here are the steps to use it in Unreal Engine:

	Information	Media
1	How to view Earthworks particles in Unreal Engine
2	To expose your soil particles to Unreal, create a VHL interface in the Vortex Studio Editor (your soil particles must be already functional).
3	In Vortex Studio Editor, on your VHL interface, add an extension pointer output field by pressing '+' in the VHL editing screen using Vortex Editor.
4	In Unreal Editor, import some rock models into your Unreal assets. Import some material to use for the rock models. If your rock model doesn't come from a pre-existing Unreal asset (ie you imported it from fbx) verify that the scale matches Unreal's centimeter units by opening it in Unreal and confirming its size.
5	In Unreal Editor, create an 'Instanced Static Mesh' component in an Actor relevant to the soil particles (environment, ground, etc). Configure it to use one of the previously imported rock models.
6	Soil Particles must be created as instanced meshes in Unreal Engine. Here is a breakdown of the Blueprint image shown next to this step: In the relevant actor's 'Construction Script', pre-create a pool of particles. Match the maximum particle count the Vortex Studio particle culling, in this example, it is a pool of 10000 particles matching the maximum particle count setup in Vortex Studio. (refer to Earthwork Systems Tutorials) Set the initial transform for the instances to be out of the Player's view. (like underground)
7	In Unreal, Soil Particles must be updated at runtime from the Vortex data. Here is a breakdown of the Blueprint image shown next to this step: For each particle, a transform must be created from a position and a scale given by Vortex data. (advanced) You can use the particle ID and a modulus operator to randomize mesh instance and angle of rotation (using frame number for example) "Mark Render State Dirty" on "Update Instance Transform" must be true for particle position change to be taken into account by Unreal Engine visible. (performance) Setting it to true for each particle is very slow. It should be true for the last particle only. (optional) Since we are working with a pool of particles (from the Construction Script) you may need to position the remaining unused particles out of view. The 'Hide Particles' variable is a transform to apply to unused particles to 'park' them out of sight.

Deformable Terrain

As a Vortex Studio and Unreal Engine user, you can see your Vortex Studio Deformable Terrain and interact with it in Unreal Engine. Here are the steps:

For general information about creating a Deformable Terrain in Vortex Studio, refer to Deformable Terrain

	Information	Media
1	The expected result when driving on soft ground with soft ground tire models in Unreal, notice the following: The ground texture is different where the wheel has compressed the grass. The ground is visually and permanently deformed (compressed) when wheels move over it.
2	The first step is to create a new Mechanism in Vortex Studio containing a Deformable Terrain. Refer to the Deformable Terrain Engineering Guide. It is possible to create a Deformable Terrain at the Scene or Mechanism level. For Unreal use, it must be created at the Mechanism level since it is the importable building block. As with the Soilbin in the Earthworks - Soilbin section above, expose the Deformable Terrain object as a VHL output.
3	In Unreal Editor, follow "Loading a Vortex Mechanism in Unreal" to add your Vortex Studio Mechanism to the Unreal world Depending on how the Mechanism containing the Deformable Terrain was created you may need to delete or hide some imported assets from the resulting Unreal import to properly view the terrain. If the Deformable Terrain conforms to a gallery they will be superimposed once in Unreal Engine. This can be used to hide the imported gallery (static mesh): Convert it to Blueprint and add a Procedural Mesh. Open the Event Graph for editing. To associate the Procedural Mesh to your Deformable Terrain, create a "Get VHL Field as Tiled Heightfield" event. The VHLName and Field Name should match the field used to expose the Deformable Terrain in the previous step. Store the OK output in a variable for use in the next step. Each step, get this (previous) value and pass it to the Update input. This allows the event to differentiate updating the mesh from creating the mesh The rest of the event graph deals with setting proper materials on each section and disabling the costly 'Cast Shadow' flag
4	In the Blueprint for the Actor containing the Vortex Mechanism of the Deformable Terrain, add the typical Blueprint construct to position the origin of the Procedural Mesh (shown in the image on the right)
5	You can design a material that will use a different texture for deformed and undeformed regions (as in Vortex Studio). When designing your material, mix the two textures according to the value of one of the color channels of "Vertex Color". Black is deformed and White is undeformed. Refer to https://docs.unrealengine.com/en-US/Engine/Rendering/Materials/index.html

Visualizing the Vortex Simulation for Debugging Purposes Using the Vortex Remote Debugger

It can be useful to use the Vortex Studio Remote Debugger tool visualize your simulation. The tool lets you inspect collision geometries, contacts, part origins, and more to identify the source of problems.

The Remote Debugger can be very useful to view the Vortex Studio environment within Unreal.
It allows the user to see collision geometries, contacts, part origins, etc.

Supported Colliding Objects in Unreal

The Unreal Engine supports multiple colliding objects in your simulations, including landscape and static meshes.

Landscape

The landscape is the primary tool to create a terrain in the Unreal Engine. This object uses a height map to define the elevations of the terrain. It includes several Landscape Components (each with the same number of quads).

The plugin automatically discovers Landscape Components within a 50m x 50m range around any given Vortex Mechanism and creates the corresponding height field in the Vortex world (all this occurs at runtime).

The following image shows an example of a landscape component made of 127 X 127 quads (16129 quads):

You can inspect any generated height fields in the Vortex world using the Vortex Remote Debugger. The following image shows an example of generated height fields in the Vortex Remote Debugger:

Meshes That Do Not Simulate Physics

With the plugin, the application can generate collisions between a Vortex Mechanism and any Unreal mesh that does not simulate physics (static). For example, the system can generate collisions with the following:

Static meshes
Instanced static meshes, such as foliage
Landscape splines

The Unreal Engine supports 2 different types of collisions:

Simple Collision
Complex Collision

By default, the application uses simple collisions, since they support better performance. You can override the collision type at different levels in Unreal Engine, in Project Settings or for the individual mesh. For more information about simple and complex collisions in Unreal, see: https://docs.unrealengine.com/en-US/Engine/Physics/SimpleVsComplex/index.html

The plugin always uses the same collision type as the one currently being used by PhysX on the Unreal Engine side. The integration supports the following shapes:

Supported Simple Collision Shapes	Box Sphere Sphyl Convex
Supported Complex Collision Shapes	Triangle Mesh

IMPORTANT: To function correctly, the static meshes cannot be in a blueprint containing a Deformable Terrain or a Soil Bin. The statics mesh must exist in a separate actor.

Example of Meshes that Do Not Simulate Physics

The following image shows a default simple collision used by a tree mesh (for foliage).

You can visualize the resulting geometry in the Vortex Remote Debugger:

Mapping Contact Materials

The Vortex Plugin for the Unreal Engine lets you specify which dynamic materials the application uses for a given collision. To configure this, you can map physical materials in Unreal to dynamics materials in Vortex Studio.

The physics properties you define for material in the Unreal Editor do not affect materials in Vortex Studio. The changes you make only apply to PhysX simulation in the Unreal Engine.

Create a Mapping for Contact Materials

To create a mapping for contact materials, do the following:

If a Physical Material does not already exist in your Unreal project for the type of material you want to use, create a new one:
Navigate to Project Settings → Vortex Studio and do one of the following:
- Click to select the Vortex material table you want to use.
- Accept the default material setting.
Create a Material Mapping. In this new mapping, select the Unreal physical material you want to use and write the Vortex dynamics material that you want to associate it with. You can create a landscape mapping, static Mesh mapping, or static mesh mapping with complex collisions.

Map Landscape Materials
The Unreal Editor lets you assign physical materials by Landscape Layer. You can inspect each later here:
To map landscape materials, do the following:
1. Click to select the layer that you will associate with a physical material.
2. To automatically select the Landscape Layer Info Object, click on the lens icon next to it.
3. From the Content Browser, double click on the Layer Info Object. The following window appears:
4. Specify the Physical Material that you will associate with the layer and then press the Save.
Map Static Meshes
To map a static mesh, do the following:
1. In the Unreal Editor, open a window for the static mesh that you want to associate with a physical material.
2. Select the Simple Collision Physical Material that you will use for this mesh and save the changes.
  The system only applies the physical material if the mesh uses simple collisions
Map a Static Mesh Using Complex Collisions
To map a static mesh that uses complex collisions, do the following:
1. In the Unreal Editor, open a window for the static mesh that you want to associate with a physical material.
2. Search for graphics materials in the mesh.
  When you use a complex collision, the application uses a graphics material to apply each physical material (a one-to-one relationship). You must pay special attention to the graphics material you select for the static mesh.
3. Double click on the graphics material you want to open an editor for it.
4. From the editor window for the graphics material, select the physical material you will associate with the graphics material.
  The application only applies the physical materials if the mesh uses complex collisions.
(optional) Use the Vortex Studio Remote Debugger to debug Vortex Studio dynamics material.
Using the Vortex Studio Remote Debugger tool, you can inspect the dynamics material the Vortex Studio uses for a given contact from the following page:

Packaging Your Project

Before you can distribute your simulation to users as an Unreal project, you must package it. Packaging ensures that all code and content is up to date and in the correct format to run on your target platform. For more information about packaging projects in Unreal, see the Packaging Projects topic in Unreal online documentation: https://docs.unrealengine.com/en-US/Engine/Basics/Projects/Packaging/index.html.

When you package an Unreal project that uses the Vortex Studio plugin, you must include all Vortex Studio assets with all the Unreal assets in the packaging process.

To prevent disorganization, CM Labs strongly recommends that you isolate the Vortex Studio assets, including mechanisms, assemblies, graphics galleries, the application setup document, and any material tables, in sub-folders under the Content folder of the Unreal project directory.

IMPORTANT: You can only use the Vortex Studio Plugin for Unreal Engine to package a project for Windows (64-bit)

To Package Your Project

To package a Vortex Mechanisms directory, including all dependent files, do the following:

In the Unreal Editor, open the Project Settings for you project.
Under Project, click to select Packaging.
At the bottom of the Packaging items, click Show Advanced.
Scroll down to Additional Non-Asset Directories to Copy.
To add a new entry, press the + button and click to select the Vortex_Mechanisms directory under the Content directory
A packaged version of your Unreal project will now run correctly.

Viewing Vortex Studio Log Files in the Unreal Editor

When you develop a project in the Unreal Editor using Vortex Studio content, you may need to refer to application information about the Vortex Studio simulation for debugging purposes. To facilitate troubleshooting, the Vortex Studio plugin and the Vortex Studio application log messages. To access application logs, follow these steps:

To View Vortex Studio Plugin for Unreal Engine Logs

When you use the plugin, Vortex Studio generates logs in the Output Log window of the Unreal Editor. The application groups log files under the LogVortex category:

You can also find these logs in the Saved/Logs subfolder of your Unreal project.

Logs from the Vortex Application

Logs generated by the Vortex Studio application are output as .log files in the Saved/Logs subfolder of your Unreal project.

Limitations

Physical Interaction Between Unreal and Vortex Studio

The Vortex Studio Plugin for Unreal Engine allows Vortex mechanisms to interact with Unreal static objects only. When enabling this feature, a 50m x 50m detection box is used in the Unreal world around each Vortex Mechanism to automatically detect all static obstacles. Those obstacles are streamed at runtime to Vortex to create corresponding collision geometries.

Supported Platform

The Vortex Studio Plugin for the Unreal Engine only supports the "Windows (64-bit)" platform.

To use the following guide, you must be familiar with Vortex mechanisms, Vortex Graphics Galleries, and the Unreal Editor.

In the following documentation, you will be able to simulate Vortex mechanisms just like any other assets in an Unreal level.

With the Vortex Studio Plugin for Unreal Engine, the Unreal Editor lets you connect to parameters that you expose in Vortex Studio.

Any Vortex Studio simulation parameter can be sent to a function in an Unreal blueprint (get/set) and included in your Unreal level.

Vortex Studio manages external devices, such as motion platforms and CANopen-compliant devices for controlling vehicles and enriching simulation.

Getting started...

Tell me about...

Installing the Vortex Studio Plugin

Installing the Vortex Studio Plugin involves downloading the plugin from the Unreal marketplace and configuring basic parameters.

Prerequisites

To use the Vortex Studio for Unreal Engine 4 plugin, you must have Vortex Studio and Unreal Engine 4.26.

Download the plugin from the Unreal Marketplace and install it following these steps:

IMPORTANT

You must have a valid Epic games user account to download the plugin from the Unreal Marketplace.

To install the Plugin with the Epic Games Launcher

Open the Epic Games Launcher and login using your account information.
Click the Marketplace tab.
In the search bar, type Vortex.
The Vortex Studio plugin appears in the list.
Click Vortex Studio plugin and click on Install to Engine.
The Vortex Studio plugin now appears in your Unreal projects

To install the Plugin from the 7z File

Open the folder Plugins at the following address <Unreal Engine Installation Folder>\Engine\Plugins\.
If you see a subfolder named VortexPlugin remove it.
Copy the 7z named Vortex_Studio_Unreal_Plugin_[ReleaseNumber].7z into the Plugins folder.
In the 7-zip context menu, select Extract Here.
Delete the 7z file.

How to rebuild the Vortex Studio Plugin to a later version of Vortex Studio

Prerequisites

Unreal Engine version 4.26: We cannot guarantee that the plugin will work with a version other than 4.26
Microsoft Visual Studio: In order to compile the code, we recommend having Microsoft Visual Studio 2019.
Vortex Studio: A Vortex Studio installation is mandatory for the update and for the plugin to work with Unreal Engine.

How to update the plugin step-by-step

Make sure that you currently have the Vortex Studio plugin from the Marketplace. If you don't, install it from the Marketplace page or from the Vault section of your library if it is there:
Open your Windows Explorer and move to the folder where the Vortex Studio plugin was installed. For example, if Epic Games is installed at the default location, the path should be: C:\Program Files\Epic Games\UE_4.26\Engine\Plugins\Marketplace ;
Inside the Marketplace folder, copy the folder VortexPlugin and copy it somewhere else such as in your Documents or on the Desktop. The important part is that it isn't inside the Epic Games repository.
In your new location, open the VortexPlugin folder. There, delete both the Binaries and the Intermediate folders. The end result should look like this:
From there, go in the folder named <Work Folder>\VortexPlugin\Source\ThirdParty\VortexStudio\Win64 . This is where we will have to change some files.
Open a new Windows Explorer and open your Vortex Studio installation. The path should be C:\CM Labs\Vortex Studio <vortex version>
The first step will be to copy and replace the library. In <Vortex Studio Installation>\lib, copy VortexIntegration.lib and copy it inside <Work Folder>\VortexPlugin\Source\ThirdParty\VortexStudio\Win64\lib. You will have to replace the existing library.
The second step will be to copy the header files. In <Vortex Studio Installation>\include\VortexIntegration, copy all files and move them to <Work Folder>\VortexPlugin\Source\ThirdParty\VortexStudio\Win64\include\VortexIntegration . This will replace all files except the one named Version.h.
Finally, open the file Version.h in <Work Folder>\VortexPlugin\Source\ThirdParty\VortexStudio\Win64\include\VortexIntegration and open the file VxVersion.h from <Vortex Studio Installation>\include\Vx. Each field of Version.h needs to be replaced to mirror the defined fields of VxVersion.h:
Now that the files are updated, we need to compile the plugin. Open a CMD prompt and move to your Unreal Engine install in the batch file folder C:\Program Files\Epic Games\UE_4.26\Engine\Build\BatchFiles
From here, run this command and replace the path location with your own:
```
c:\Users\username\Desktop\vortex>"C:\Program Files\Epic Games\UE_4.26\Engine\Build\BatchFiles\RunUAT.bat" BuildPlugin -Plugin="c:\Users\username\Desktop\vortex\VortexPlugin\VortexPlugin.uplugin"
-Package "c:\Users\username\Desktop\vortex\output" -CreateSubFolder -VS2019
```
Where:
1. RunUAT.bat is the batch file to run;
2. BuildPlugin is the action;
3. -Plugin is the path of the uplugin file from your new plugin folder;
4. -Package is the output folder where your new plugin will be created. This must be outside the Unreal Engine directory;
5. -CreateSubFolder is to specify how to create the plugin hierarchy;
6. -VS2019 is to specify the compiler. This may change depending on your Microsoft Visual Studio installation.
Now go back into your Epic Games application and uninstall the Vortex Studio plugin.
Copy the folder VortexPlugin from your work folder into the plugin repository of Unreal Engine at this location: C:\Program Files\Epic Games\UE_4.26\Engine\Plugins
Close and restart Epic Games. You should now be able to use the Vortex Plugin with your current version.

Running a Sample Project

To download the sample project files do the following:

In a web browser go to https://cm-labs.exavault.com/share/view/1s3xe-amykk3cw
To begin the download, click the filename of the sample project: Vortex_Studio_for_Unreal_Forklift_Sample_[ReleaseNumber].7z and extract the content on your computer.
Open the Unreal Engine 4.26 and click the Launch button.
In the Unreal Project Browser, click Browse and navigate to the extracted sample files.
Open the ForkliftSim_uproject file.
The project opens in the Unreal Editor.
NOTE: It can take several minutes for the project and to load for the first time.
To start the simulation, press the Play button.
You can use a Direct Input game controller to control the forklift.

Organizing Vortex Studio Assets

This section assumes that you already have a good understanding of Vortex Studio Editor Documents.

The Vortex Studio plugin lets you import Vortex mechanisms to an Unreal project.

*.vxmechanism (Mechanism Document)
*.vxassembly (Assembly Document)
*.vxgraphicgallery (Graphics Gallery Document)
*.vxc (Setup Document)
*.vxmaterials (Material Table)

Example

In this example, you have the following folder hierarchy for a Vortex forklift mechanism:

Forklift
- Dynamics
  - Forklift.vxmechanism
  - Forklift_Assembly.vxassembly
- Graphics
  - Forklift2016.vxgraphicgallery

To build a valid Unreal project, you must move the same folder structure to a sub-folder of the Content folder for your Unreal project. The structure of your Unreal project would appear as follows:

MyProject
- MyProject.uproject
- Config
  - ...
  - ...
- Content
  - Vortex_Mechanisms
    - Forklift
      - Dynamics
        Forklift.vxmechanism
        Forklift_Assembly.vxassembly
      - Graphics
        Forklift2016.vxgraphicgallery

Creating Your First Project

Bringing your first Vortex Studio project into Unreal involves verifying that the plugin is enabled, restarting the application, and verifying settings for the project with the plugin.

About Vortex Studio Project Settings

You can customize several settings for your project in the Unreal Editor from the Project Settings window.

Specifically, you can customize the following settings for your project:

Anytime you change a setting, you must restart the application before they can take effect.

Category	Setting Name	Description
	Data Provider's Path	This setting is for advanced usage. Specifies a path (must be under the `Content` directory for the project) where some simulation data will be stored (for instance, Control Presets). Default: None.
Application Setup	Use Default	When set to true, the Vortex Studio simulation in the Unreal application uses this default Application Setup Document packaged with Vortex Studio: `C:\CM Labs\Vortex Studio [ReleaseNumber]\resources\config\VortexIntegration.vxc` Default: True.
Application Setup	Custom Application Setup	This setting is only used when Application Setup->Use Default is false. It allows using a custom Application Setup Document for your Unreal project. It is strongly recommended to use the default Application Setup Document for Vortex integrations as a starting point. The default file is under: `C:\CM Labs\Vortex Studio [ReleaseNumber]\resources\config\VortexIntegration.vxc` Your custom Application Setup Document must reside under the `Content` folder for the project. It should be under a specific sub-folder since it will be needed to package this Non-Asset folder when packaging your Unreal project. Default: None (not used)
Material Table	Use Default	When set to true, the Vortex Studio simulation within Unreal will use this default Material Table packaged with Vortex Studio: `C:\CM Labs\Vortex Studio [ReleaseNumber]\resources\DynamicsMaterials\default.vxmaterials` Default: True
Material Table	Custom Material Table	This setting is only used when Material Table->Use Default is false. It lets you specify a custom Material Table for your Unreal project. It is strongly recommended that you use the default Material Table for Vortex Studio integrations as a starting point. The default file is under: `C:\CM Labs\Vortex Studio [ReleaseNumber]\resources\DynamicsMaterials\default.vxmaterials` Your custom Material Table must exist under the `Content` folder for your project. It must exist under a specific sub-folder since the application uses it to package this `Non-Asset` folder when packaging your Unreal project. Default: None (not used)
Static Collision	Enable Landscape Collision Detection	If true, Unreal Landscapes will be transferred to Vortex Studio at runtime, using the underlying Vortex terrain paging system, so your mechanisms can collide with them. For additional parameters that allow tuning the performance of the terrain paging system, please see the Static Collision → Terrain Paging category below. Default: True
	Enable Mesh Simple Collision Detection	If true, Collision On a Simple Shaped Mesh for all Unreal Static Meshes will be transferred to Vortex Studio at runtime, using the underlying Vortex terrain paging system, so your mechanisms can interact with them. Note that Vortex Studio always uses the colliding geometry (simple or complex) that PhysX would use in Unreal. For additional parameters that allow tuning the performance of the terrain paging system, please see the Static Collision → Terrain Paging category below. Default: True
	Enable Mesh Complex Collision Detection	If true, Collision On a More Complex Mesh for all Unreal Static Meshes will be transferred to Vortex Studio at runtime, using the underlying Vortex terrain paging system, so your mechanisms can interact with them. Note that Vortex Studio always uses the colliding geometry (simple or complex) that PhysX would use in Unreal. For additional parameters that allow tuning the performance of the terrain paging system, please see the Static Collision → Terrain Paging category below. Default: True
	Material Mappings	Allows associating an Unreal Physical Material to a Vortex Contact Material by name. This lets you specify which contact material a Vortex collision uses for computation purposes. The application only uses these associations when at least one of the following settings is enabled: Enable Landscape Collision Detection Enable Mesh Simple Collision Detection Enable Mesh Complex Collision Detection Default: None.
Static Collision → Terrain Paging Landscape	Tile Size XY	Size in meters, in world X and Y direction, of the square tiles used by the landscape terrain pager for landscape collision queries and caching. Landscape component will be queried by the terrain pager in tiles of the given size around the dynamically moving Vortex mechanisms. Tiles will be cached and only queried again if not already present in the cache in order to reduce query time, and in order to produce consistent, non-duplicate collision geometries in the Vortex simulation when multiple moving objects are operating in close proximity. Use Tile Size XY value around the Landscape Component size for better results. For more information on this parameter and the terrain paging system underlying the Unreal integration, refer to Integrating Vortex Studio using the VortexIntegration API. Default: 50 meters
	Look Ahead Time	Specifies the time, in simulation seconds, the terrain pager should forecast ahead. All the terrain to be reached within the specified time, at the current velocity, will be requested. If the terrain paging system experiences slow downs when navigating, consider reducing this parameter. For more information on this parameter and the terrain paging system underlying the Unreal integration, refer to Integrating Vortex Studio using the VortexIntegration API. Default: 1 second
	Safety Band Size	Specifies the distance (in meters) to grow the paged region by, as a safety band, in order to account for objects changing direction. If the terrain paging system experiences slow downs when navigating, consider reducing this parameter. For more information on this parameter and the terrain paging system underlying the Unreal integration, refer to Integrating Vortex Studio using the VortexIntegration API. Default: 1 meter
Static Collision → Terrain Paging Mesh	Tile Size XY	Size in meters, in world X and Y direction, of the square tiles used by the terrain pager for Mesh collision queries and caching. Terrain will be queried by the terrain pager in tiles of the given size around the dynamically moving Vortex mechanisms. Tiles will be cached and only queried again if not already present in the cache in order to reduce query time, and in order to produce consistent, non-duplicate collision geometries in the Vortex simulation when multiple moving objects are operating in close proximity. If the terrain paging system experiences slow downs when navigating on a complex terrain with many obstacles (e.g., trees) consider reducing this parameter. Note that a too drastic reduction (e.g., a value of 1 meter) can in itself lead to slowdowns. A balance can be found through experimentation. For more information on this parameter and the terrain paging system underlying the Unreal integration, refer to Integrating Vortex Studio using the VortexIntegration API. Default: 50 meters
	Look Ahead Time	Specifies the time, in simulation seconds, the terrain pager should forecast ahead. All the terrain to be reached within the specified time, at the current velocity, will be requested. If the terrain paging system experiences slow downs when navigating on a complex terrain with many obstacles (e.g., trees) consider reducing this parameter. For more information on this parameter and the terrain paging system underlying the Unreal integration, refer to Integrating Vortex Studio using the VortexIntegration API. Default: 1 second
	Safety Band Size	Specifies the distance (in meters) to grow the paged region by, as a safety band, in order to account for objects changing direction. If the terrain paging system experiences slow downs when navigating on a complex terrain with many obstacles (e.g., trees) consider reducing this parameter. For more information on this parameter and the terrain paging system underlying the Unreal integration, refer to Integrating Vortex Studio using the VortexIntegration API. Default: 1 meter

To Create a New Unreal Project Using the Vortex Studio Plugin

Open the Unreal Engine 4.26 and click the Launch button.
In the Unreal Editor, follow steps in Unreal documentation to create a new project.
In the upper left, click Edit and then click Plugins.
Confirm that the Vortex Studio plugin is installed.
To enable the plugin, click to select Enabled.
In the lower right, click Restart Now.
The project re-opens with the Vortex Studio plugin enabled.
Save the project to permanently enable the plugin.

Managing the Frame Rate Between Vortex Studio and the Unreal Editor

IMPORTANT

To maintain fidelity and realism in the simulation, you must configure project settings so that Unreal Engine and Vortex Studio both use a fixed frame rate.

Example: Setting the Frame Rate in Vortex Studio and the Unreal Engine

In this example, you want a simulation to run at 90 Hz.

To set the Frame Rate in the Unreal Editor, do the following:

In the Unreal Editor, open your project.
Click Edit and then click Project Settings.
In the Project Settings window, under the Engine section, click General Settings.
Scroll down to the Framerate section and do the following:
1. Click to select the Use Fixed Frame Rate checkbox.
2. In the Fixed Frame Rate field, specify 90.00.
Save the settings and restart the project.

To set the Frame Rate in the Vortex Studio Editor, do the following:

Prerequisite: You must have a custom Simulator Setup User Guide (not the default one provided with Vortex Studio). For more information, see 3302964707.

Make sure the custom application setup document is saved in the Content directory of your Unreal project.

In the Vortex Studio Editor, open the custom Application Setup Document for this project.
In the Explorer panel, click Setup.
On the right of screen, in the Properties panel, set the Simulation Frame Rate value to 90.00.
To save your changes, click the Save button.
When you restart the Unreal Editor, validate that the settings have been correctly configured.

Importing Mechanisms into Unreal

It replicates the Vortex Studio graphics node hierarchy using the imported graphics galleries and uses it to create a hierarchy of corresponding Unreal Scene and Static Mesh components.
It automatically updates the position and orientation of relevant Unreal Scene and Static Mesh components when Vortex Studio parts are moving.
When a Vortex Studio part moves, the blueprint analyzes connections between parts and graphics nodes in Vortex Studio (typically under the Skin connection container) to detect which components move.

The Unreal Editor does not expose the automatic mapping which occurs.

The Skin connection container and all relevant graphic nodes in Vortex Studio are required for the integration and must not be deleted.

Importing a Vortex Studio mechanism into Unreal involves preparing your Vortex Studio project, specifying project settings in the Unreal Editor, and creating a new project blueprint.

Preparing your Vortex Studio Project for Import

To Import a Mechanism from Vortex Studio to the Unreal Editor

To add Vortex Studio mechanism to your Unreal project, do the following:

Make sure your Vortex Studio assets are 3302964707 in the Content folder for your Unreal project.
In the Unreal Editor, select the directory in the Content Browser where you will import your Vortex mechanism, including textures, material instances static meshes, and a VortexMechanism Unreal asset.
Option 1:
1. Drag and drop the .vxmechanism file you want to import from Windows Explorer into the Content Browser.
2. A pop-up window for selecting a folder appears
3. After selecting a folder to save the generated blueprint, the application imports the mechanism.
Option 2
1. Right-click on the directory in the Content Browser and then click Import to /Game/...
2. A pop-up window for selecting a folder appears.
3. Select the .vxmechanism file you want to import and click Open.
4. The application imports the mechanism and generates a blueprint.
Select a folder for the new blueprint class and then click OK.
Drag-and-drop the generated mechanism blueprint from the Content Browser into the viewport.
You can open the blueprint to get or set additional values from Vortex Studio. The blueprint appears empty while the application maps the meshes and transforms from Vortex.

(Optional) To Take Control of the New Actor

To take control of the new Actor in Unreal, do the following:

In the Blueprint Editor for your new Actor, on the toolbar click File and then click Reparent Blueprint.
In the Reparent Blueprint list, search for Pawn and then click to select it.
To verify the new parent class for your blueprint, use the mouse to hover over the root element of the Components panel.
The parent class of the blueprint is now Pawn.
To add a camera to the blueprint, click the +Add Component button and select the camera you want to add from the menu.
Click Compile and then click Save.
In the Components panel, click to select the new camera. Then, switch the center view to Viewport and use manipulators to move your camera to the correct location.
When the camera is added and in the correct position, in the Components panel, click select the root element (the self element).
On the right of the screen, in the Details panel, scroll down to the Pawn category and assign Auto Possess Player to a valid player ID. For example, Player 0.
Compile and save the blueprint.
In the main window of the project, click the Save Current button.
Now, because the Pawn blueprint is automatically possessed when the simulation begins, the 3D view should automatically display what the Blueprint camera sees when you press the Play button.

Enabling Vortex Simulation

For simulation with Vortex content to function correctly, your Unreal Level Blueprint must include functions to start and stop Vortex simulation in the context of your Unreal gameplay.

To add these functions, do the following:

Open your Level Blueprint:
In the Event Graph, find the EventBeginGameplay item.
In the EventGameplay item, use the left mouse button to click the Exec icon and drag it to the right and then release the mouse button.
A pop-up window for adding a function appears
In the pop-up window, scroll to the Vortex →Application category and click Start Simulation.
In the Event Graph area, right-click anywhere on the empty space (not on a node).
In the search bar of the blueprint actions pop-up window that appears, type end play and then select the search result Event End Play.
Use the same process to add a Stop Simulation function. Click the Exec icon on the new Event End Play and drag it right before you release the mouse button. Then, add the Stop Simulation function.
Compile and save the Level Blueprint.
To save your map, press the Save Current button in the main Unreal Editor interface.

To make sure that the Vortex simulation can start correctly, always press the Save Current button before you press Play. This of course will also save to disk any changes to your map.

You can call the Start Simulation and Stop Simulation functions at any time, but you must make sure the Vortex simulation has completely stopped when you stop the Unreal simulation. All Vortex mechanisms must be loaded when the Vortex simulation is not running.

Get/Set Vortex Studio Mechanism Inputs and Outputs (IO)

After you import Vortex mechanisms to an Unreal project, you must get/set Vortex mechanism inputs and outputs (IO) from the Unreal simulation.

Available IO for mechanisms are defined by the following mechanism interfaces:

Outputs from these interfaces can be read from Unreal, while inputs can be set with new values from the Unreal simulation.

For this purpose, a set of useful blueprint functions are exposed by the Vortex Studio plugin. To quickly find them, type VHL in the action search bar:

Each function must have a Mechanism Component as a target. This component is automatically created under the blueprint class created when you import a Vortex mechanism (see 3302964707).

The following functions are available to you:

Blueprint Function	Description
From Vortex to Unreal
Get VHLField as Bool	Allows to search for a specific VHL/Control interface's output field on the target mechanism. This function assumes the desired field is a boolean field and will return its value as a bool.
Get VHLField as Float	Allows to search for a specific VHL/Control interface's output field on the target mechanism. This function assumes the desired field is a double field and will return its value as a float.
Get VHLField as Integer	Allows to search for a specific VHL/Control interface's output field on the target mechanism. This function assumes the desired field is an integer field and will return its value as an int32.
Get VHLField as String	Allows to search for a specific VHL's output field on the target mechanism. This function assumes the desired field is a string field and will return its value as an FString.
Get VHLField as Transform	Allows to search for a specific VHL's output field on the target mechanism. This function assumes the desired field is a Matrix44 field and will return its value as an FTransform.
Get VHLField as Vector 2	Allows to search for a specific VHL's output field on the target mechanism. This function assumes the desired field is a Vector2 field and will return its value as an FVector2D.
Get VHLField as Vector 3	Allows to search for a specific VHL's output field on the target mechanism. This function assumes the desired field is a Vector3 field and will return its value as an FVector.
Get VHLField as Vector 4	Allows to search for a specific VHL's output field on the target mechanism. This function assumes the desired field is a Vector4 field and will return its value as an FVector4.
From Unreal to Vortex
Set VHLField as Bool	Allows to search for a specific VHL/Control interface's input field on the target mechanism. This function assumes the desired field is a boolean field and will set its value from a bool.
Set VHLField as Float	Allows to search for a specific VHL/Control interface's input field on the target mechanism. This function assumes the desired field is a double field and will set its value from a float.
Set VHLField as Integer	Allows to search for a specific VHL/Control interface's input field on the target mechanism. This function assumes the desired field is an integer field and will set its value from an int32.
Set VHLField as String	Allows to search for a specific VHL/Control interface's input field on the target mechanism. This function assumes the desired field is a string field and will set its value from an FString.
Set VHLField as Transform	Allows to search for a specific VHL/Control interface's input field on the target mechanism. This function assumes the desired field is a Matrix44 field and will set its value from an FTransform.
Set VHLField as Vector 2	Allows to search for a specific VHL/Control interface's input field on the target mechanism. This function assumes the desired field is a Vector2 field and will set its value from an FVector2D.
Set VHLField as Vector 3	Allows to search for a specific VHL/Control interface's input field on the target mechanism. This function assumes the desired field is a Vector3 field and will set its value from an FVector.
Set VHLField as Vector 4	Allows to search for a specific VHL/Control interface's input field on the target mechanism. This function assumes the desired field is a Vector4 field and will set its value from an FVector4.

Additional variations of the Get VHLField as ... function are available, but they are reserved for exceptional circumstances.

All functions have similar structures:

You must connect the Exec input to the correct Event tick. For example, if the data is get/set every tick, then the Exec of Event Tick must connect to the Exec input for the new function.

Get VHLField as ...

Input	Target	Specifies on which Mechanism Component to call this function. The Mechanism Component refers to the specific `.vxmechanism` file from Vortex.
Input	VHLName	The name of the VHL/Control interface to search for.
Input	Field Name	The name of the output field to search for.
Output	Value	The returned value (the type differs for each variation of the Get VHLField as ... function).

Set VHLField as ...

Input	Target	Specifies on which Mechanism Component to call this function. The Mechanism Component refers to the actual .`vxmechanism` file from Vortex.
Input	VHLName	The name of the VHL/Control interface to search for.
Input	Field Name	The name of the input field to search for.
Input	Value	The value to assign to the specified field (the type differs for each variation of the Set VHLField as ... function).

Earthworks Systems

Soilbin

As a Vortex Studio and Unreal Engine user, you can see your Vortex Studio Soilbin and interact with it in Unreal Engine. Here are the steps:

	Information	Media
1	How to view an Earthworks Soilbin in Unreal Engine Before you start, make sure that your Soilbin is correctly designed in Vortex Studio. You cannot make changes to the Soilbin extension from the Unreal Editor, and changes to inputs, outputs, and parameters that you make in Vortex Studio can cause problems in Unreal if they affect the mapping to the Procedural Mesh Component in the Unreal blueprint.
2	Expose your Soilbin and its World Transform to VHL using the Vortex Editor. For the proper position of the origin of the Soilbin in Unreal, expose the Outputs. World Transform of the Dynamics Soil Bin. This will be used from the blueprint as a position for the Procedural Mesh Component. To expose it, drag the field onto the VHL Interface's "Outputs" row.
3	To expose a Soilbin's shape so the Unreal object (created later in this guide) can conform to the Soilbin visuals, using Vortex Editor navigate to the VHL editing screen. Add an extension pointer output field by pressing '+' next to the "Outputs" column title. Keeping the VHL editing screen open navigate to your Soilbin in the Explorer tree. Select it and drag it to the "Data" column of the just created extension pointer output on the VHL editing screen. You will need to remember the names of these two outputs when working in Unreal, so it might be helpful for you to rename them.
4	In your Unreal project, open Plugins. Then, enable the 'Procedural Mesh' plugin. It can be found in the Built-In" pulldown.
5	To prepare Unreal Editor to receive Soilbin data from Vortex, create a 'Procedural Mesh' component in a blueprint relevant to the Soilbin (truck, ground, pile, etc).
6	The 'Procedural Mesh' must be created and updated at runtime from the Vortex data. Here is a breakdown of the Blueprint image shown next to this step: Set the Material on the mesh Set the Transform of the Procedural Mesh based on data from Vortex Create the mesh with the Height Field data from Vortex Recreate the mesh when the Heightfield size changes or Update it if the size didn't change Optional: An empty Soil Bin will likely create graphical artifacts as the bottom face of the container exactly overlaps with the flat height field. To avoid this, you can raise or lower the Transform received from Vortex by a small amount.

Soil particles

	Information	Media
1	How to view Earthworks particles in Unreal Engine
2	To expose your soil particles to Unreal, create a VHL interface in the Vortex Studio Editor (your soil particles must be already functional).
3	In Vortex Studio Editor, on your VHL interface, add an extension pointer output field by pressing '+' in the VHL editing screen using Vortex Editor.
4	In Unreal Editor, import some rock models into your Unreal assets. Import some material to use for the rock models. If your rock model doesn't come from a pre-existing Unreal asset (ie you imported it from fbx) verify that the scale matches Unreal's centimeter units by opening it in Unreal and confirming its size.
5	In Unreal Editor, create an 'Instanced Static Mesh' component in an Actor relevant to the soil particles (environment, ground, etc). Configure it to use one of the previously imported rock models.
6	Soil Particles must be created as instanced meshes in Unreal Engine. Here is a breakdown of the Blueprint image shown next to this step: In the relevant actor's 'Construction Script', pre-create a pool of particles. Match the maximum particle count the Vortex Studio particle culling, in this example, it is a pool of 10000 particles matching the maximum particle count setup in Vortex Studio. (refer to Earthwork Systems Tutorials) Set the initial transform for the instances to be out of the Player's view. (like underground)
7	In Unreal, Soil Particles must be updated at runtime from the Vortex data. Here is a breakdown of the Blueprint image shown next to this step: For each particle, a transform must be created from a position and a scale given by Vortex data. (advanced) You can use the particle ID and a modulus operator to randomize mesh instance and angle of rotation (using frame number for example) "Mark Render State Dirty" on "Update Instance Transform" must be true for particle position change to be taken into account by Unreal Engine visible. (performance) Setting it to true for each particle is very slow. It should be true for the last particle only. (optional) Since we are working with a pool of particles (from the Construction Script) you may need to position the remaining unused particles out of view. The 'Hide Particles' variable is a transform to apply to unused particles to 'park' them out of sight.

Deformable Terrain

As a Vortex Studio and Unreal Engine user, you can see your Vortex Studio Deformable Terrain and interact with it in Unreal Engine. Here are the steps:

For general information about creating a Deformable Terrain in Vortex Studio, refer to Deformable Terrain

	Information	Media
1	The expected result when driving on soft ground with soft ground tire models in Unreal, notice the following: The ground texture is different where the wheel has compressed the grass. The ground is visually and permanently deformed (compressed) when wheels move over it.
2	The first step is to create a new Mechanism in Vortex Studio containing a Deformable Terrain. Refer to the Deformable Terrain Engineering Guide. It is possible to create a Deformable Terrain at the Scene or Mechanism level. For Unreal use, it must be created at the Mechanism level since it is the importable building block. As with the Soilbin in the Earthworks - Soilbin section above, expose the Deformable Terrain object as a VHL output.
3	In Unreal Editor, follow "Loading a Vortex Mechanism in Unreal" to add your Vortex Studio Mechanism to the Unreal world Depending on how the Mechanism containing the Deformable Terrain was created you may need to delete or hide some imported assets from the resulting Unreal import to properly view the terrain. If the Deformable Terrain conforms to a gallery they will be superimposed once in Unreal Engine. This can be used to hide the imported gallery (static mesh): Convert it to Blueprint and add a Procedural Mesh. Open the Event Graph for editing. To associate the Procedural Mesh to your Deformable Terrain, create a "Get VHL Field as Tiled Heightfield" event. The VHLName and Field Name should match the field used to expose the Deformable Terrain in the previous step. Store the OK output in a variable for use in the next step. Each step, get this (previous) value and pass it to the Update input. This allows the event to differentiate updating the mesh from creating the mesh The rest of the event graph deals with setting proper materials on each section and disabling the costly 'Cast Shadow' flag
4	In the Blueprint for the Actor containing the Vortex Mechanism of the Deformable Terrain, add the typical Blueprint construct to position the origin of the Procedural Mesh (shown in the image on the right)
5	You can design a material that will use a different texture for deformed and undeformed regions (as in Vortex Studio). When designing your material, mix the two textures according to the value of one of the color channels of "Vertex Color". Black is deformed and White is undeformed. Refer to https://docs.unrealengine.com/en-US/Engine/Rendering/Materials/index.html

Visualizing the Vortex Simulation for Debugging Purposes Using the Vortex Remote Debugger

The Remote Debugger can be very useful to view the Vortex Studio environment within Unreal.
It allows the user to see collision geometries, contacts, part origins, etc.

Supported Colliding Objects in Unreal

The Unreal Engine supports multiple colliding objects in your simulations, including landscape and static meshes.

Landscape

The following image shows an example of a landscape component made of 127 X 127 quads (16129 quads):

You can inspect any generated height fields in the Vortex world using the Vortex Remote Debugger. The following image shows an example of generated height fields in the Vortex Remote Debugger:

Meshes That Do Not Simulate Physics

Static meshes
Instanced static meshes, such as foliage
Landscape splines

The Unreal Engine supports 2 different types of collisions:

Simple Collision
Complex Collision

The plugin always uses the same collision type as the one currently being used by PhysX on the Unreal Engine side. The integration supports the following shapes:

Supported Simple Collision Shapes	Box Sphere Sphyl Convex
Supported Complex Collision Shapes	Triangle Mesh

IMPORTANT: To function correctly, the static meshes cannot be in a blueprint containing a Deformable Terrain or a Soil Bin. The statics mesh must exist in a separate actor.

Example of Meshes that Do Not Simulate Physics

The following image shows a default simple collision used by a tree mesh (for foliage).

You can visualize the resulting geometry in the Vortex Remote Debugger:

Mapping Contact Materials

The physics properties you define for material in the Unreal Editor do not affect materials in Vortex Studio. The changes you make only apply to PhysX simulation in the Unreal Engine.

Create a Mapping for Contact Materials

To create a mapping for contact materials, do the following:

If a Physical Material does not already exist in your Unreal project for the type of material you want to use, create a new one:
Navigate to Project Settings → Vortex Studio and do one of the following:
- Click to select the Vortex material table you want to use.
- Accept the default material setting.
Create a Material Mapping. In this new mapping, select the Unreal physical material you want to use and write the Vortex dynamics material that you want to associate it with. You can create a landscape mapping, static Mesh mapping, or static mesh mapping with complex collisions.

Map Landscape Materials
The Unreal Editor lets you assign physical materials by Landscape Layer. You can inspect each later here:
To map landscape materials, do the following:
1. Click to select the layer that you will associate with a physical material.
2. To automatically select the Landscape Layer Info Object, click on the lens icon next to it.
3. From the Content Browser, double click on the Layer Info Object. The following window appears:
4. Specify the Physical Material that you will associate with the layer and then press the Save.
Map Static Meshes
To map a static mesh, do the following:
1. In the Unreal Editor, open a window for the static mesh that you want to associate with a physical material.
2. Select the Simple Collision Physical Material that you will use for this mesh and save the changes.
  The system only applies the physical material if the mesh uses simple collisions
Map a Static Mesh Using Complex Collisions
To map a static mesh that uses complex collisions, do the following:
1. In the Unreal Editor, open a window for the static mesh that you want to associate with a physical material.
2. Search for graphics materials in the mesh.
  When you use a complex collision, the application uses a graphics material to apply each physical material (a one-to-one relationship). You must pay special attention to the graphics material you select for the static mesh.
3. Double click on the graphics material you want to open an editor for it.
4. From the editor window for the graphics material, select the physical material you will associate with the graphics material.
  The application only applies the physical materials if the mesh uses complex collisions.
(optional) Use the Vortex Studio Remote Debugger to debug Vortex Studio dynamics material.
Using the Vortex Studio Remote Debugger tool, you can inspect the dynamics material the Vortex Studio uses for a given contact from the following page:

Packaging Your Project

When you package an Unreal project that uses the Vortex Studio plugin, you must include all Vortex Studio assets with all the Unreal assets in the packaging process.

IMPORTANT: You can only use the Vortex Studio Plugin for Unreal Engine to package a project for Windows (64-bit)

To Package Your Project

To package a Vortex Mechanisms directory, including all dependent files, do the following:

In the Unreal Editor, open the Project Settings for you project.
Under Project, click to select Packaging.
At the bottom of the Packaging items, click Show Advanced.
Scroll down to Additional Non-Asset Directories to Copy.
To add a new entry, press the + button and click to select the Vortex_Mechanisms directory under the Content directory
A packaged version of your Unreal project will now run correctly.

Viewing Vortex Studio Log Files in the Unreal Editor

To View Vortex Studio Plugin for Unreal Engine Logs

When you use the plugin, Vortex Studio generates logs in the Output Log window of the Unreal Editor. The application groups log files under the LogVortex category:

You can also find these logs in the Saved/Logs subfolder of your Unreal project.

Logs from the Vortex Application

Logs generated by the Vortex Studio application are output as .log files in the Saved/Logs subfolder of your Unreal project.

Limitations

Physical Interaction Between Unreal and Vortex Studio

Supported Platform

The Vortex Studio Plugin for the Unreal Engine only supports the "Windows (64-bit)" platform.

Browser not supported