Feature mapping and compatibility
See which Zimension features become Unity components, which are approximated, and which need manual implementation in the native converter.
Native conversion ยท importer 0.3.11
Native conversion matrix
Converted means that the importer generates a Unity representation of the supported settings. It does not imply exact rendering or physics parity. The import report identifies approximations and unsupported settings for the particular project.
| Zimension feature | Unity representation | Limits or changes |
|---|---|---|
| Scenes and hierarchy | One .unity scene per Zimension scene; GameObjects and WorldItemId | Base scene is first. Source IDs resolve copied items. |
| Models, materials and placement | glTF/GLB prefabs, materials and transforms | Coordinates are mirrored once across X. Prefab root scale and rotation are retained. |
| Basics shapes and ground | Generated meshes, colliders and Unity Terrain | Lighting, terrain and material appearance are approximations of the browser renderer. |
| Sky, lighting and fog | Unity environment, directional light, sky and fog settings | Browser postprocessing and rendering are not reproduced exactly. |
| Project events and variables | Generated <Project>Logic partial class and typed properties | Only registered project events bind. Built-in events use GameManager. |
| Conditions, arithmetic and switches | Generated C# statements and methods | Switch Control and Return to Previous Control do not have a native equivalent. |
| Delayed and sequenced event cards | Coroutine helpers and generated calls | Individual supported card timing is distinct from the unsupported full animation-sequencer feature. |
| Interactions, zones and collectables | Interactable, PlayerZone, Collectable and ItemContact | Selection and reach are approximated with bounds; hiding an item stops its zone checks. |
| Player, camera and health | PlayerController and CharacterController | Character movement and camera are native implementations; view and control modes need project-specific checks. |
| Spawn points and checkpoints | GameManager.spawnPoints and generated event calls | event changes the respawn pose; teleportEvent moves the player without changing the checkpoint. Poses are scene-specific. |
| Character animations | Animator Controllers, Humanoid Avatars and muscle-space clips | Recognisable rigs retarget; unsupported skeletons use bone-name binding. Review the report. |
| Holding, firing and reloading | Rifle/pistol states, Weapon and corrected hand grip | Requires compatible clips in the export. Saved grip and muzzle poses transfer; scoped optics and the full browser aiming system do not. |
| Transitions and procedural motion | Baked movement clips and ProceduralMotion | Pickup stops scene placement motion while a hand owns the weapon. |
| Audio and completion events | AudioSources, SoundFinished and generated callbacks | Audio rolloff, subtitles and browser mixing are not identical in every case. |
| Vehicles | Rigidbody with four-wheel suspension, saved wheel/seat settings, camera and events | Tyre forces and handling approximate the browser system; test the course in Unity. Bikes and aircraft need custom work. |
| NPC behaviours | CharacterBehaviour and RuntimeNavMesh | Supported follow, patrol, attack and shoot behaviour is approximated; navigation must be checked in the converted scene. |
| Damage and respawn | Health, damage callbacks and respawn settings | Hit effects and VFX systems are not fully reproduced. |
| Instance groups | Generated copies of objects | Does not preserve the browser's instanced-rendering implementation. |
| Default HUD and game flow | GameHud and GameManager | Saved prompt/message styling, enabled health, top-right health placement and green/orange/red thresholds; start/death/pause/win screens. |
| Custom HUD and overlays | NativeCustomUi and shared UI renderer | Nested absolute/relative placement, centered row/column layouts, responsive overrides, images, events and variable bindings. Complex CSS and spatial UI need manual work. |
| Camera cutscenes | NativeCutscenes | Camera shots, paths, transitions, FOV, control suspension, return and skip events. Review timing in the imported scene. |
| Objectives and environment effects | Manual implementation | Objectives, quests and event-driven screen/environment effects are not converted. |
| Terrain, grass and water | Terrain height/paint data, native grass and water shaders | Rendering is approximated across engines. Check materials, density, lighting and water styles in Unity. |
| Physics and advanced geometry | Mesh/primitive colliders and supported character/vehicle components | Collision-none objects retain interaction ranges without solid physics. General rigid-body authoring and spline sweeps need manual work. |
| Meta Quest controller VR | Optional OpenXR rig and tracked Canvas UI | Enable VR in the importer. Supports basic controller gameplay; hand tracking, advanced spatial constraints and full browser UI parity remain outside this scope. |
| Multiplayer and voice | Manual implementation | Networking and voice are not recreated by native conversion. |
| Custom scripts and cloud features | Rewrite as Unity C# or service integration | Browser JavaScript, purchases, account services, video surfaces and custom input bindings are not automatically ported. |
Use the report as your project checklist
Open export-report.json after every import. Blocking findings prevent the project from running as saved; approximated findings describe behaviour changes; unsupported and optional findings identify missing conversion or assets.
The repository also documents the legacy interpreting runtime. For this workflow, use the native conversion section in the ProjectGuide and inspect the generated components. Test your release in Unity rather than assuming a feature transfers because it works in the browser.
