🎯 ZionTPS

Setup Wizard

The ZionTPS Setup Wizard is the main setup workflow for generating a player and camera rig from a humanoid model.

Watch the full setup walkthrough: YouTube Video

Open it from:

Tools > ZionTPS > Setup Wizard

The wizard is split into five steps:

1. Model
2. Animation
3. Camera
4. Modules
5. Generate

Overview

The Setup Wizard generates an Asset-Store-safe player and camera setup from a model prefab or FBX.

Depending on your choices, it can:

• validate your model
• use an existing Animator Controller or generate one
• create a player prefab
• create a camera rig prefab
• create CharacterDefinition and AnimationDefinition assets
• create camera profile assets
• optionally install integration, Foot IK, and audio components
• optionally instantiate the result into the current scene

Step 1 — Model

Assign a visual-only model prefab or FBX.

You can also optionally assign an existing Animator Controller.

Expected model setup

For best results, your source model should be:

• humanoid
• using a valid Avatar
• visual-only
• free from colliders on the visual model
• free from rigidbodies on the visual model
• free from a CharacterController on the model
• free from an assigned Runtime Animator Controller on the model

Validation

The wizard can validate the assigned model and report issues.

Validation checks include:

• no Animator found
• no Avatar assigned
• invalid Avatar
• non-humanoid Avatar
• Runtime Animator Controller assigned on the model
• colliders on the model
• rigidbodies on the model
• CharacterController on the model
• script components on the model
• model scale not equal to 1,1,1

Asset-Store Lockdown

When Asset-Store Lockdown is enabled, validation errors can block generation until the setup is fixed.

Fix options

The wizard can apply fixes to the generated model instance, including:

• reset local position / rotation / scale
• strip colliders
• strip rigidbodies
• clear Animator Controller on the model instance

There is also an advanced option to apply fixes to the source model prefab.

Step 2 — Animation

The Animation step controls how the controller gets its motion setup.

Using an existing Animator Controller

If an existing Animator Controller is assigned in Step 1:

• the controller is used as-is
• clip fields are disabled

Generating a controller from clips

If no Animator Controller is assigned, the wizard generates one from clips.

Required locomotion clips

These are required:

• Idle
• Walk
• Run

Optional air clips

These are supported but optional:

• Jump
• Fall
• Land

Optional crouch setup

If Enable Crouch is enabled, you can assign:

• Crouch Idle
• Crouch Walk

If either crouch clip is missing, the wizard can still generate the setup, but crouch states are not added unless both clips are assigned.

Optional roll setup

If Enable Roll is enabled, you can assign:

• Roll

If the roll clip is missing, the wizard can still generate the setup, but roll is not added.

Demo animations

The Animation step includes a button to open the demo animations package.

Step 3 — Camera

The Camera step controls the generated rig and optional profile assets.

Camera Profiles

When enabled, the wizard generates three camera profiles:

• Default
• Combat
• Aim

If profile generation is disabled, the wizard still generates the rig, but not the profile assets.

Camera behaviour options

Available options include:

• Collision Smoothing
• Input Smoothing
• Dynamic FOV

Default camera values

You can also set:

• Distance
• Pivot Offset

Step 4 — Modules

The Modules step controls optional add-ons.

Core Integration API

When enabled, the wizard installs:

• ZionPlayer
• ReflectionLocomotionSource
• ZionLocomotionEventEmitter

These components are added to the player root and wired to ThirdPersonController.

Foot IK

When enabled, the wizard:

• adds ZionFootIK to the model Animator
• enables IK Pass on layer 0 of the Animator Controller

Audio Module

The audio step is optional and only works if ZionTPS.Audio is present in the project.

When available, the wizard can install:

• AudioSource
• ZionTPSAudioModule
• ZionTPSAnimationAudioEvents

It can also create:

• ZionTPSAudioConfig.asset

If the audio module is not present, the wizard skips audio installation.

Separate modules

Stats, UI, and Audio can be separate assets and imported independently.

Step 5 — Generate

The Generate step controls output and scene setup.

Output settings

You can choose:

• output folder
• player prefab name
• camera rig name

Default output folder:

Assets/ZionTPS_Generated

Scene setup options

If Instantiate into current scene is enabled, the wizard can also:

• place the generated player and camera rig into the current scene
• create a ground physics material
• set up a basic skybox
• create a post-processing placeholder

Generation rules

The wizard can generate only when:

• a model is assigned
• either an existing Animator Controller is assigned, or Idle, Walk, and Run clips are set
• validation errors are not blocking generation through Asset-Store Lockdown

What the wizard creates

During generation, the wizard can create:

• CharacterDefinition.asset
• AnimationDefinition.asset
• ZionTPS.controller if no existing controller was assigned
• player prefab
• camera rig prefab
• camera profiles

If scene instantiation is enabled, it can also place the generated result directly into the current scene.

After generation

After generation, the next steps are:

1. assign Input Actions on ThirdPersonInput
2. test camera profiles at runtime
3. adjust camera settings if needed
4. assign audio clips in ZionTPSAudioConfig if the audio module was installed

Related tools

ZionTPS also includes related editor tools, including:

• Tools > ZionTPS > Animation Clip Swapper
• Tools > ZionTPS > Diagnostics > Validate Generated Animator Controller
• Tools > ZionTPS > Diagnostics > Validate Selected Animator Controller
• Tools > ZionTPS > Diagnostics > Validate Selected AnimationDefinition + Controller

There are also quick scene actions such as:

• GameObject > ZionTPS > Create Player + Camera Rig
• GameObject > ZionTPS > Create Ground Plane