Hi everyone,
I have a problem with the export from Unity to Needle Engine. Using Needle versions up to 5.0 I always get a “UnitySynchronization.ExecuteTasks” window that doesn’t finish - even after hours. Using newer versions of Needle (5.1 or 6.0 alphas) the export fails with “The scene produced no gltf output” also referencing to “UnitySynchronization.ExecuteTasks”. I have tried various things:
- Updating to newer Unity versions: same behaviour
- Creating a new project: first export is successful but as soon as I change something in the scene it failes again
- reinstalling / updating Node.js & Visual Studio
- deleting all Unity, Needle, npm caches in AppData
Does anyone have an idea what could be causing this or what else I could try?
The UnitySynchronization.ExecuteTasks hanging indefinitely points to a stuck task in the sync pipeline. Since a fresh project exports once but fails after changes, you likely have a specific asset or component in your scene that’s blocking the export — probably a complex prefab, an unsupported shader, or a broken animation reference.
Try this first: Strip your scene down to just a cube with a Needle component. If that exports fine, start re-introducing assets one by one until the export breaks again. That’ll tell you exactly what’s causing the freeze.
If the stripped scene also fails, check your Node.js version (needle works best with Node 18 LTS or 20 LTS) and ensure you have no anti-virus scanning your temp folder during exports.
Sources: Needle Engine Docs (64%)
1 replies left - Become PRO for more replies.
Reply to this post directly if you need further help (bottom right button)
Hi, Philipp, which Unity version are you using?
