Zimension Docs

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.

Native conversion matrix
Zimension featureUnity representationLimits or changes
Scenes and hierarchyOne .unity scene per Zimension scene; GameObjects and WorldItemIdBase scene is first. Source IDs resolve copied items.
Models, materials and placementglTF/GLB prefabs, materials and transformsCoordinates are mirrored once across X. Prefab root scale and rotation are retained.
Basics shapes and groundGenerated meshes, colliders and Unity TerrainLighting, terrain and material appearance are approximations of the browser renderer.
Sky, lighting and fogUnity environment, directional light, sky and fog settingsBrowser postprocessing and rendering are not reproduced exactly.
Project events and variablesGenerated <Project>Logic partial class and typed propertiesOnly registered project events bind. Built-in events use GameManager.
Conditions, arithmetic and switchesGenerated C# statements and methodsSwitch Control and Return to Previous Control do not have a native equivalent.
Delayed and sequenced event cardsCoroutine helpers and generated callsIndividual supported card timing is distinct from the unsupported full animation-sequencer feature.
Interactions, zones and collectablesInteractable, PlayerZone, Collectable and ItemContactSelection and reach are approximated with bounds; hiding an item stops its zone checks.
Player, camera and healthPlayerController and CharacterControllerCharacter movement and camera are native implementations; view and control modes need project-specific checks.
Spawn points and checkpointsGameManager.spawnPoints and generated event callsevent changes the respawn pose; teleportEvent moves the player without changing the checkpoint. Poses are scene-specific.
Character animationsAnimator Controllers, Humanoid Avatars and muscle-space clipsRecognisable rigs retarget; unsupported skeletons use bone-name binding. Review the report.
Holding, firing and reloadingRifle/pistol states, Weapon and corrected hand gripRequires compatible clips in the export. Saved grip and muzzle poses transfer; scoped optics and the full browser aiming system do not.
Transitions and procedural motionBaked movement clips and ProceduralMotionPickup stops scene placement motion while a hand owns the weapon.
Audio and completion eventsAudioSources, SoundFinished and generated callbacksAudio rolloff, subtitles and browser mixing are not identical in every case.
VehiclesRigidbody with four-wheel suspension, saved wheel/seat settings, camera and eventsTyre forces and handling approximate the browser system; test the course in Unity. Bikes and aircraft need custom work.
NPC behavioursCharacterBehaviour and RuntimeNavMeshSupported follow, patrol, attack and shoot behaviour is approximated; navigation must be checked in the converted scene.
Damage and respawnHealth, damage callbacks and respawn settingsHit effects and VFX systems are not fully reproduced.
Instance groupsGenerated copies of objectsDoes not preserve the browser's instanced-rendering implementation.
Default HUD and game flowGameHud and GameManagerSaved prompt/message styling, enabled health, top-right health placement and green/orange/red thresholds; start/death/pause/win screens.
Custom HUD and overlaysNativeCustomUi and shared UI rendererNested absolute/relative placement, centered row/column layouts, responsive overrides, images, events and variable bindings. Complex CSS and spatial UI need manual work.
Camera cutscenesNativeCutscenesCamera shots, paths, transitions, FOV, control suspension, return and skip events. Review timing in the imported scene.
Objectives and environment effectsManual implementationObjectives, quests and event-driven screen/environment effects are not converted.
Terrain, grass and waterTerrain height/paint data, native grass and water shadersRendering is approximated across engines. Check materials, density, lighting and water styles in Unity.
Physics and advanced geometryMesh/primitive colliders and supported character/vehicle componentsCollision-none objects retain interaction ranges without solid physics. General rigid-body authoring and spline sweeps need manual work.
Meta Quest controller VROptional OpenXR rig and tracked Canvas UIEnable VR in the importer. Supports basic controller gameplay; hand tracking, advanced spatial constraints and full browser UI parity remain outside this scope.
Multiplayer and voiceManual implementationNetworking and voice are not recreated by native conversion.
Custom scripts and cloud featuresRewrite as Unity C# or service integrationBrowser 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.

Zimension AI

Docs assistant

How can I help?

Ask anything about Zimension docs

AI may make mistakes. Always verify with official docs.