Project structure and safe reimporting
Understand generated Unity folders, preserved user code, source assets, one-way updates and how to upgrade the importer without losing custom work.
Native conversion ยท importer 0.3.11
Generated and preserved files
| Path | Contains | Reimport behaviour |
|---|---|---|
| Assets/Zimension/SourceAssets/<Project>/ | Models, textures, sounds and animation libraries | Updated when content changes; source GUIDs are retained. |
| Assets/Zimension/Generated/<Project>/ | Scenes, controllers, baked clips, avatars, terrain, materials and reports | Rebuilt. Direct edits here can be overwritten. |
| Assets/Zimension/Scripts/<Project>/<Project>Logic.Generated.cs | Generated event methods and bindings | Rewritten. |
| Assets/Zimension/Scripts/<Project>/<Project>Logic.cs | Your half of the partial logic class | Created once and preserved. |
| Assets/Zimension/UserContent/ | Your scripts, prefabs, assets and custom work | Not touched by project reimport. |
| Packages/com.zimension.runtime/ | Importer and runtime Kit code | Changes when you upgrade the package. |
Reimport an updated project
- Keep a version-controlled copy or backup of your Unity work.
- Save the Zimension project and download a new Web project export ZIP.
- Import that project ZIP into the same Unity project through From a file.
- Wait for generated C# compilation and the Connected <Project>Logic message.
- Review the new import report, reconnect any custom work affected by changed scene content, and test the base scene and scene switches.
Upgrade the importer
The Unity template download and the project data ZIP have separate purposes. To upgrade an existing Unity project, back it up, replace the embedded Packages/com.zimension.runtime folder with the version from the new template, allow Unity to resolve dependencies, then reimport the project.
Keep template versions and project data versions in your release records. Do not assume that an older Unity project receives package fixes merely because you exported a new project ZIP.
One-way authoring and scene changes
Unity edits do not synchronize back into Zimension. If you continue authoring in Zimension, keep Unity-specific work separate from generated content.
Generated scene-switch events call GameManager.LoadScene. Project variables can be carried into the next scene. Checkpoints belong to the active scene; a checkpoint from one scene is not a global cross-scene save system.
Pull latest uses the optional hosted export-link service. It is not required for the file import workflow and should only be used when your deployment provides that service.
