> For the complete documentation index, see [llms.txt](https://docs.gercstudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gercstudio.com/weapons/weapon-controller/aim/third-person.md).
# Third Person
### Aim Speed‌
How fast a character takes the weapon in the aim mode.
### Switch to FP view
If you use the third-person view and activate this feature:
1. First button click - enable normal aim mode.
2. Second button click - switch to the first-person view to deep aim.
3. Third button click - disable aim.
### Aim before Attack
If this feature is active, a character will aim before the attack.
### Scope model
To create a sight display, do the following:
1. Create an object to match the weapon scope (standard cylinder for example)
2. Activate the **Scope Mode** in the **Weapon Controller** script
3. Place the object you created into the script
### Aim with texture
To add a sight texture, do the following:
1. Activate the **Texture Mode***.*
2. Set a scope texture.
---
# 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://docs.gercstudio.com/weapons/weapon-controller/aim/third-person.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.