Skip to content

Integrations

RenderDoc

IMPORTANT

Status: Discontinued in 1.1
Minimum Version: 1.0

image

Support for work (dx11 only) with the ability to connect in real-time (run with the -renderdoc key). Also, when running with this parameter, the debug mode for shaders is enabled, allowing you to modify them in RenderDoc

WARNING

As of version 1.1, only launches from the program are supported.
To use shader debug mode, use the -dxdebug key

Discord

IMPORTANT

Status: Supported
Minimum Version: 1.0

image

Basic Discord activity integration. The title can be specified in engine_external.ltx in the [general] section in the title parameter. The section uses StringTable, which allows you to make translations for different languages.

LuaPanda

IMPORTANT

Status: Supported
Minimum Version: 1.0

LuaPanda - This is a VSCode plugin that allows you to debug Lua scripts.

WARNING

Integration is not available for Release configuration!

  1. Install the plugin
  2. Open the scripts folder as the root for VSCode
  3. Run the debugger
  4. Connect the game to VSCode

image

Optick

IMPORTANT

Status: Supported
Minimum Version: 1.2

Optick - is a high-performance, low-overhead profiler for C++, designed for the game industry. It provides all the necessary tools for analyzing and optimizing application performance.

WARNING

Integration is not available for Release configuration!

Usage Instructions

  1. Download and install Optick
  2. Run the Optick application
  3. Run the game and go to the area that needs profiling.

Profiling can be done in two ways: through the Optick interface or directly in the game.

Method 1: Profiling via Optick

  1. In the Optick interface, click the Start Profiling Session button in the desired game scene

image

  1. Wait for connection — a Connecting message will appear

image

  1. After capture is complete, information about the number of recorded frames will be displayed

image

  1. To stop profiling, click the Stop button

Method 2: Profiling via the Game Interface

  1. Run the game;
  2. Go to the scene that needs to be analyzed;
  3. Activate debug mode: press Alt + I (English layout);
  4. You will get a cursor, go to the Tools tab;
  5. Click the Optick Start Capture button;
  6. To finish profiling, use the Optick Stop Capture button in the same tab;

image

  1. A file named ixray-date-time-username.opt will appear in the game root;
  2. Open the file in Optick

WARNING

After capture is complete, the game may crash. This is acceptable behavior.

Recommendations

  • Long capture is not recommended — it may cause Optick to malfunction.
  • Running Optick and the game as administrator allows you to get a more complete set of data for analysis.

Published under the MIT license.