Skip to main content
Skip table of contents

Using the Pixotope SDK

What is it?

The Pixotope SDK contains public source code and other files that are not released with the base version of Pixotope. When installed together with Pixotope, the SDK enables power users to develop their own C++ code to work with Pixotope.

Pixotope SDK does not expose any proprietary functionality to be accessible through C++. It currently only allows users to access features already available within vanilla UE5.

Where do I get it?

With an SDK license assigned, the SDK zip file can be downloaded from Pixotope Cloud.
To get this license, please contact →


The following are prerequisites for compiling plugins:

  1. Windows 10 (64-bit)

  2. Pixotope (installed without Erizos Plugin)

  3. Microsoft Visual Studio 2022 (with the C++ Desktop extensions included)

Installation (with .zip)

  1. Make sure you have the base Pixotope installed

  2. Download the Pixotope SDK zip file (6 GB) from the provided link

  3. Make sure that the version number of the Pixotope SDK shown in the zip filename matches the version number of your Pixotope installation. (You can check the version number in Pixotope Director in the Windows menu under "Help".)

  4. Unzip the files to a temporary folder (over 22 GB of additional disk space required). NB: The unzipping process may stall for a long time because of Windows virus checking. Under Windows Security > "Virus & threat protection" settings, turn off "Real-time protection" temporarily.

  5. Copy the unpacked Pixotope Engine folder over the Pixotope Engine folder from your installation folder. Agree to replace files.

Building custom plugins

To speed up the development process, you can develop your plugin with the version of vanilla Unreal Engine that corresponds to the version of UE5 that your Pixotope installation is based on.

Third-party plugins which work with the corresponding version of UE5 should work with Pixotope straight away. However, Pixotope always shows an advisory warning for plugins that weren't compiled with the Pixotope SDK. Should you encounter any problems in the plugin operation, we recommend recompiling it with our SDK.

Once you are ready to deploy your plugin for Pixotope, you need to build it with the Unreal Automation Tool from the Pixotope SDK folders.

You should not build the plugin in place under the Engine directory, but instead on the Desktop and then migrate the compiled code to the relevant plugin folder e.g. Pixotope Third Party

The following batch file does exactly that, when executed in your plugin's folder. (You can also find it in your Pixotope SDK installation folder under dev_scripts.)

@ECHO off
REM Please copy this batch file and execute it inside your plugin folder (next to the .uplugin file).
REM Make sure you have Pixotope and Pixotope Dev Kit installed beforehand.
REM Resulting compiled plugin will be generated in /ForPixotope folder.
REM Remember to remove your /Source from /FromPixotope, before distributing /ForPixotope folder's contents, if you desire to keep your code private.
REM This finds the latest installed Pixotope path
FOR /F "skip=2 tokens=2,*" %%A IN ('reg.exe query "HKLM\SOFTWARE\Pixotope Technologies\Pixotope" /v "LastInstallPath"') DO SET "install_dir=%%B"
FOR %%a IN ("%~dp0\.") DO SET "parent=%%~nxa"
SET "install_dir=%install_dir%Pixotope Engine\Engine"

REM Uncomment this to use a different Pixotope installation. For example: SET "install_dir=C:\Pixotope\24.2.0-6000\Pixotope Engine\Engine"

ECHO Building %parent%.uplugin against the engine at %install_dir%
"%install_dir%\Build\BatchFiles\RunUAT.bat" BuildPlugin -Plugin="%~dp0%parent%.uplugin" -Package="%~dp0ForPixotope\%parent%" -UsePrecompiled -TargetPlatforms=""

The batch file, when run next to the .uplugin file, will generate a ForPixotope folder containing your compiled plugin. Make sure to delete any source code that you want to keep private and that might have been copied inside in the process.
Also, please keep in mind that the ForPixotope plugin folder needs to be renamed so as to have the same name as the .uplugin file!

The provided batch file will help you successfully compile plugins that already successfully compile with the full UE5 vanilla source as Engine plugins (plugins in the [Installation folder]\Pixotope Engine\Engine\Plugins folder). Many publicly available plugins were not written to work this way. In such a case, please create a C++ project and compile your plugin with it (by creating a Plugins folder in your project folder, pasting your plugin inside, and regenerating the project files).

This is advanced UE5 programming! Read up on it online as much you can.

NB: The resultant plugin may generate a version warning, saying that it was compiled for e.g. 5.2.0, when in fact you are running 5.2.1. In this case, just edit the .uplugin file and change the EngineVersion to 5.2.1. That will prevent the warning from appearing.

Building C++ projects

Once you have the Pixotope SDK installed, you can also start C++ projects with Pixotope. Any machine that runs such a project will need to have the Pixotope SDK installed.

To create a new C++ project, start the engine directly from the executable [Installation folder]\Pixotope Engine\Engine\Binaries\Win64\UE4Editor.exe

Afterwards, add your project's folder path in Pixotope Director in the "General" panel. 

We strongly advise against using C++ projects, as they can introduce many unexpected crashes and inconsistencies. We recommend implementing your custom functionality using well-tested plugins and Blueprint logic.

Remember that building your custom functionality responsibly, especially within an environment as complex as Unreal Engine 5, requires a lot of testing, preferably by professionals with a QA background.

We can only provide limited support for C++ projects.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.