First Playable Character

Place the sample CharacterContainer in a new scene with solid ground and verify one working character, camera, input route, and manager set before building a project-specific character.

Before you begin

• Complete Requirements and First Decisions and Importing.
• Import the optional sample and satisfy its TextMesh Pro, URP, and Input System requirements.
• Resolve every Console compiler error.
• Use a new saved scene so the result is easy to isolate.

Import the sample

1. Open Tools > Opsive > Ultimate Character Controller > Setup Manager.
2. Select Sample.
3. Select Import Sample and wait for Unity to finish importing and compiling.
4. Confirm that the Console has no new package, shader, or compiler errors.

Add CharacterContainer

1. Create and save an empty scene.
2. Search the Project window for CharacterContainer inside the imported sample.
3. Drag the prefab into the scene at the origin.
4. Confirm that the prefab supplies a character, Camera Controller, and scene-level manager objects. It does not contain an environment floor.
5. Add ground beneath the character, for example a Plane with a non-trigger Mesh Collider. Keep it on a layer included in the character’s Solid Object Layers, and place the character above it without overlapping the collider.
6. Save the scene again.

CharacterContainer supplies the camera, controller, and managers for this test. Add the ground, then use those supplied components rather than introducing a second camera or movement controller.

Verify in Play Mode

1. Enter Play Mode.
2. Use the configured movement input and confirm that the character changes position.
3. Use the configured look input and confirm that the camera follows or rotates with the character.
4. Start one standard ability such as Jump when it is available in the imported configuration.
5. Stop input and confirm that the character remains stable rather than drifting, jittering, or falling through the floor.
6. Confirm that the Console contains no missing-manager, Look Source, input, or movement-type errors.

This is the first-success checkpoint. Do not continue to custom models, item creation, or Animator edits until this scene works.

Recognize the working ownership

• The Game or equivalent manager object supplies scene services.
• Camera Controller owns camera position and rotation through its active View Type.
• Ultimate Character Locomotion owns character movement, collision, Movement Types, Abilities, and Effects.
• The Player Input implementation and locomotion handler translate device input into character commands.
• Animator Monitor coordinates UCC runtime values with the model’s Animator.

Read How UCC Fits Together before replacing any of those owners.

Troubleshooting

Use Getting Started Troubleshooting when the first failing owner is not obvious.

Continue to a project character

Keep this working scene as a comparison. Create another scene, follow Quick Setup, and build the project model with Character Creation. Compare the custom scene with CharacterContainer whenever movement, camera, or managers diverge.