Unreal Engine bridge
The Unreal Engine bridge plugin integrates directly into the Unreal Editor, supporting one-click asset importing, automatic material conversions, and non-blocking background imports.
Before you install
- Supports Unreal Engine 5.3 and later.
- Ensure the Korvix3D desktop app is installed and running.
- You need Python Developer Scripting enabled in Unreal Editor (Edit β Plugins β Scripting β Python Foundation Packages / Python Developer Scripting).
Install from Asset Hub (recommended)
- Open Asset Hub β Bridges β Unreal Engine.
- Click Install. The desktop app scans for your Unreal projects automatically.
- Choose the target
.uprojectproject file and install the bridge files. - The installer writes the scripts to the project's
Plugins/Korvix3D/directory. - Open your project in Unreal Editor. You will see a Korvix3D icon on the editor toolbar.
Manual Installation
If you want to manually copy the bridge files:
- Download the Unreal Bridge ZIP package from the Download page.
- Navigate to your Unreal project's root folder. Create a folder named
Pluginsif it does not exist. - Extract the contents of the ZIP into
Plugins/Korvix3D/. - Restart Unreal Editor, go to Edit β Plugins, and verify that Korvix3D Bridge is enabled.
Using the Unreal Bridge
- Open your project in Unreal Editor.
- Click the **Korvix3D** button on the toolbar or choose **Window β Korvix3D Panel** to open the non-modal dashboard.
- The panel operates asynchronously in the background using pre-tick ticks so it will not lock or block your editor workspace.
- When you export an asset from the Korvix3D desktop app, the bridge automatically processes the mesh, converts textures to Unreal texture assets, generates a material instance, and spawns the actor in the viewport.
Troubleshooting
- Toolbar icon missing: Confirm that the Python Scripting plugin is enabled in Unreal preferences and check the Output Log (Window β Output Log) for any startup errors.
- Import fails or lists errors: Open the Korvix3D Panel in Unreal and scroll to the bottom logs. Hover or click on the error log row to reveal the nested traceback details.