> For the complete documentation index, see [llms.txt](https://docs.switchboard.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.switchboard.studio/guides/first-person-vehicle-interaction-system/at-a-glance.md).

# At a Glance

## First Person Character Controller

The first system of FPVIS is the First Person Character controller, modified from the standard character controller system the FPS Controller is designed to be un-obtuse and intuitive for the player. 

We believe that character movement shouldn't be overly complex - players movement is a number one priority so we designed the controller to reflect this.

Movement is designed with player freedom in mind and offer seamless movement throughout scenes - no clunky camera sway, no jarring motion anticipation. You want to move? - The controller does it.

![](/files/QcFk40qBfggRaiuFxAvu)

## Vehicles

Vehicles are the main element of this pack - designed around the same mindset as the First Person Character - vehicles are built to be intuitively operated and immersive in their behaviour. Worldspace UI elements for opening doors or controlling items like handbrakes and an easily modifiable blueprint system to expand it to your own vehicles.

Vehicles are made for the Chaos Vehicle Plug-in in Unreal 5, and the traditional PhysX system in Unreal 4.

Vehicles will only be supported on Unreal 4 until Unreal 5 becomes more stable and widespread.

![](/files/sa5OKV0Lkkq86mr1Aegq)

## Worldspace User Interface

The third and final element of this pack, which brings everything together for the end user is the UI. Once again designed on the same principals as the Character Controller and Vehicles, the UI is designed around immersion. Instead of drawing the player away trying to find the correct hotkeys to press, players are encouraged to use their surroundings to control the vehicle.

![](/files/bkBaM0fMHAkE5pzcPFcL)


---

# 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.switchboard.studio/guides/first-person-vehicle-interaction-system/at-a-glance.md?ask=<question>&goal=<endgoal>
```

`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.