Requirements and First Decisions
Choose the installed controller, perspective, input, render pipeline, and first-scene route before running a manager. These decisions determine which Setup Manager and Character Manager options are available.
Requirements
- Unity: Use Unity 2021.3 or newer for the released Version 3 installer.
- Clean compilation: Finish package import and resolve all compiler errors before opening Setup Manager.
- Sample: The optional demo requires TextMesh Pro, Universal Render Pipeline 14.0.11 or newer, and the Input System.
- Project backup: Back up or commit an existing project before changing layers, input mappings, render-pipeline integrations, Animator Controllers, or generated character hierarchies.
The Installer and Importing provide the authoritative checks for the downloaded package.
Choose the controller edition
| Installed product | Available perspective | Choose it when |
|---|---|---|
| Ultimate Character Controller | First, Third, or Both | The project may use either perspective or switch between them. |
| Ultimate First Person Shooter | First | The game requires only the first-person controller content. |
| Third Person Controller | Third | The game requires only the third-person controller content. |
Setup Manager can display an unsupported perspective in its popup, but selecting it shows a validation error and prevents Setup Camera. Install the matching controller content before configuring that camera or character; choosing Both requires both perspectives.
Choose the first route
| Question | Recommended first choice |
|---|---|
| Do you only want to verify that UCC works? | Import the sample and follow First Playable Character. |
| Do you need to explore complete systems? | Open the Demo Scene. |
| Do you have the final project model and camera requirements? | Follow Quick Setup, then Character Manager. |
| Are you upgrading Version 2 content? | Stop and use the Version 3 Migration Guide. |
Do not begin with item creation, Animator customization, integrations, or multiplayer. First prove that one character and camera move together in an otherwise simple scene.
Choose the character route
| Choice | When it applies |
|---|---|
| Humanoid | Recommended for the first visible character. It supports the included Animator Controller, Unity IK, and automatic ragdoll setup. |
| Generic | Use when the model cannot use Humanoid retargeting and the project already has a compatible Animator Controller. |
| Bodyless first person | Use when the game needs no full character model. Disable Animator when no rig is assigned. |
| Player | Uses a Player Input implementation and character handlers. Recommended for the first test. |
| AI Agent | Removes the player-input route and requires external decision-making. Add it after player locomotion works. |
Choose input
- Use Input System when the project already uses Unity’s Input System actions.
- Use the legacy Input Manager only when the project deliberately uses that backend.
- Use Rewired, InControl, or another integration only after importing and configuring its matching UCC integration.
- Do not apply Update Buttons to a project that should not receive the default legacy mappings.
Choose rendering
The active Built-in, URP, or HDRP pipeline must match the imported UCC integration and materials. The sample is a URP reference. A custom Built-in or HDRP project should follow its own project setup instead of copying sample pipeline assets indiscriminately.

Decision checkpoint
Before importing the sample or running a manager, write down:
- installed controller edition;
- First, Third, or Both perspective;
- sample or custom-scene route;
- Input System, legacy, or integration input;
- Built-in, URP, or HDRP;
- humanoid, generic, or bodyless character; and
- player or AI ownership.
Use the same choices in Setup Manager, Character Manager, Camera Controller, and input setup. If those surfaces disagree, return here before troubleshooting individual components.
Next step
Continue with Importing, then First Playable Character.