Installation
Infinio is on its way to the Unity Asset Store. Installing from the store arrives with the launch,
and this page will be updated for it. The steps below install Infinio from a .unitypackage file.
Requirements
- Unity 6000.0 LTS. Infinio is developed and tested on 6000.0.72f1. Unity 6.3 LTS is expected
to work. Unity 6.5 and newer are not supported yet: Unity’s own migration docs say the
obsolete
InstanceIDAPIs become compilation errors from 6.5, and Infinio calls one of them in its runtime assembly. The NodeGraphProcessor package is included in the.unitypackage. - Windows or macOS. Linux is not tested.
- A Universal Render Pipeline (URP) project. Burst, Collections and Mathematics reach the project as dependencies of URP, and the example shaders are URP-only. The runtime itself is pipeline-neutral, but the current install path is not.
- A network connection for the first import. Package Manager fetches Burst, Collections and Mathematics from the Unity registry when the project is created. Everything after that works offline.
Installing from a .unitypackage
- Open a Unity 6 LTS project, or create a new one with the URP 3D template. Nothing else needs installing: Burst, Collections and Mathematics come in with URP.
- Assets → Import Package → Custom Package… and select the
.unitypackagefile. - Click Import All. Unity compiles the package, which takes 30 to 60 seconds on first import.
- To confirm the editor is working, open any example graph: find one under
Assets/Infinio/Examples/, and double-click the graph asset (the one with the
icon).
If Infinio stops compiling later on, with a wall of errors about Unity.Mathematics,
Unity.Collections or Unity.Burst not existing: URP has been removed or the project’s packages
have been reset, and those three went with it. Re-add URP, or add com.unity.burst,
com.unity.collections and com.unity.mathematics by name in Package Manager (Window → Package
Manager → + → Install package by name).
Open the graph editor from Window → Infinio → Graph Editor, or by double-clicking any Infinio graph asset in the Project window. Help, docs, and support links are under Help → Infinio. Maintenance commands live under Tools → Infinio. Create new graphs via Create → Infinio Graph in the Project window’s right-click menu.
Next: Getting Started takes you from an empty graph to a working tool in about ten minutes.
Binary format and updates
Infinio compiles your node graphs into a binary format that is executed by a Burst evaluator, either in the Unity Editor or at runtime. When a format change ships in a new version, the editor automatically re-compiles your graphs the next time you open or re-save them, and the runtime accepts previous versions of compiled Infinio binaries, so an update will not break your existing graphs. Any change that could cause wire loss will be announced before it ships, not applied silently.
If you see a “graph binary format … is below the required minimum” message after an update, re-open the graph asset and re-save it. That is the complete recovery step.
Updating to a new version
New versions are announced on the Discord.
To install a new version cleanly:
- Keep any graphs you have authored outside
Assets/Infinio. Your ownAssets/Scripts,Assets/MyGraphs, or any folder that is not insideAssets/Infiniois safe. - Open an empty scene (File → New Scene → Empty) before deleting the old package, so the editor is not holding references to Infinio assets.
- Delete the entire
Assets/Infiniofolder. - Import the new
.unitypackage(Assets → Import Package → Custom Package…).
Your graphs recompile automatically on the next open or save; you will see this as a version-control diff on the compiled sub-assets. Scatter placement results may shift slightly between versions as node logic is refined.
If you import over the old version instead of deleting first: the project compiles cleanly, but
every Infinio graph asset shows the generic ScriptableObject icon rather than the
icon.
This is a Unity asset-database quirk caused by the icon file moving between versions; it has no
effect on graph behaviour. The clean-install steps above resolve it.