Unity versions and render pipelines

Reference for Convai Unity SDK environment requirements, including the minimum Unity version, required package dependencies, and render pipeline support.

The Convai Unity SDK requires Unity 6000.0.80f1 or later. There is no supported configuration on an earlier Unity release, and the SDK compiles on Unity 6000.5 now that Unity moved scene identity to 64-bit. All three Unity render pipelines are supported with no additional configuration, and both installation methods — Package Manager and Asset Store — resolve the required package dependencies automatically.

Unity version requirements

Requirement	Version
Minimum	6000.0.80f1 or later
Recommended for new projects	Unity 6 (6000.x)

The minimum is a hard floor. Convai supports no configuration below Unity 6000.0.80f1 or later, including earlier LTS releases. Upgrade the project before installing the SDK.

Required package dependencies

The SDK depends on four Unity packages. Both installation methods install these automatically — you do not need to add them manually unless you encounter a version conflict.

Package	Version
com.unity.ai.inference	2.2.1
com.unity.nuget.newtonsoft-json	3.2.2
com.unity.ugui	2.0.0
com.unity.inputsystem	1.19.0

Do not downgrade these packages after installation. The SDK targets the versions listed above and behavior on lower versions is undefined. If your project already pins an older version of any of these in Packages/manifest.json, remove or update the pin before installing.

NavMesh-driven locomotion needs one more package the SDK does not install. ConvaiNavMeshLocomotion drives a built-in Unity NavMeshAgent, but NavMesh authoring — Window > AI > Navigation and the NavMeshSurface component — comes from com.unity.ai.navigation. If your project bakes a NavMesh for character movement, install com.unity.ai.navigation yourself through Package Manager.

Render pipeline support

The SDK detects the active render pipeline at runtime and adapts automatically. The Vision module's camera capture path, for example, uses built-in render hooks when no render pipeline asset is assigned and an explicit render path on URP and HDRP. All three Unity render pipelines are fully supported with no manual configuration required.

Render Pipeline	Supported
Built-in Render Pipeline	✅ Full
Universal Render Pipeline (URP)	✅ Full
High Definition Render Pipeline (HDRP)	✅ Full

Support requires no manual configuration on any pipeline, but the Vision module's CameraVisionFrameSource captures differently depending on the pipeline. On the Built-in pipeline it uses command-buffer render hooks with no extra render pass. On URP and HDRP it falls back to an explicit render-compatibility path that issues one additional Camera.Render() call per captured frame.

The included sample scenes use URP materials. If your project uses the Built-in or HDRP pipeline, sample scene materials require reassignment. The optional depth-of-field camera scripts in SamplesShared/Camera/ support URP and HDRP; on the Built-in pipeline they skip depth-of-field and log a warning instead. None of these scripts are required for SDK functionality.

Next steps

With your Unity version and packages confirmed, check which platforms you are targeting.

Platform support matrix