> For the complete documentation index, see [llms.txt](https://lightbug14.gitbook.io/ccp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lightbug14.gitbook.io/ccp/fundamentals/untitled/character-actor/stable-movement-features.md).
# Stable movement features
These features from the CharacterActor component (as seen in the previous section) **will be applied only if the character is stable**.
## Movement
### Velocy projection
Internally, when the character is stable, the CharacterActor component will project the input velocity (Linear Velocity) onto the current ground surface (Projected Velocity).
This process will always maintain the initial velocity magnitude, regardless of the slope angle.
### Collide and Slide
This algorithm is responsible for determining obstacles along the way. If the encountered surface is allowed the character will walk onto it (maintaining always the displacement magnitude). if not, the slope will be considered as an invisible wall.
 
## Grounding
### Step up/down
This feature is responsible for putting the character on the ground (if there is one). There are two important values to consider:
* **Step up distance:** Any stable surface below this height will be walkable by the character.
* **Step down distance:** When losing contact with the ground, if the distance between the character and the ground is less or equal to this value, then the character will be automatically *grounded* (sticking to the ground)*.* If there is no ground at all, then the character will be *not grounded*.
### Edge Compensation
Normally, when a character is standing **on an edge** it collision shape will make contact with it. What edge compensation does is to lift up the capsule, simulating a cylinder shape.
This feature only works on edges, for slopes you will get the same results as before (with edge compensation disabled).
### Dynamic Ground
If the current ground the character is standing on moves/rotates, then the character will move and/or rotate with it (only yaw rotation allowed).
A valid dynamic ground **must be updated during the physics simulation**. Here are some valid examples:
* **Kinematic rigidbody** that moves/rotates using **MovePosition**/**MoveRotation**.
* **Kinematic/Dynamic rigidbody** that moves/rotates based on an **animation clip**. The update mode must be *AnimatePhysics* (*Animator* component)**.**
* **Dynamic rigidbody** that moves/rotates using linear **velocity, angular velocity, forces, torque,** etc.
## Rigidbody interactions
### Weight
If the character is standing on top of a dynamic rigidbody, it will automatically apply a force downwards at the contact point, proportional to the rigidbody mass.
### Push
The character can push other dynamic rigidbodies by colliding with them. It is also possible to ignore some rigidbodies by using a dedicated layermask:
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://lightbug14.gitbook.io/ccp/fundamentals/untitled/character-actor/stable-movement-features.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.