> For the complete documentation index, see [llms.txt](https://ms-kb.msd.unimelb.edu.au/next-lab/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ms-kb.msd.unimelb.edu.au/next-lab/virtual-reality/guides/vr-development-overview/unreal-engine-overview/unreal-engine-primer/player-vr-and-non-vr.md).

# Player: VR and non-VR

This article extends on the basic primer by further explaining the concepts in the title and how to use some of the tools and best practices.

{% hint style="info" %}
You are reading an old article for Unreal Engine 4 - it should still work for Unreal Engine 5 though!
{% endhint %}

## Player

The player is represented by an avatar and camera configuration, this is usually categorised by the different perspectives.

There is a template file available provided by Unreal Engine that will get you started, this covers the most common available options, at the MSD, most experiences will be down as First Person or Virtual Reality.

### First Person

The player controls an avatar where the camera represents a view from that avatar's eyes, the most immersive option.

### Virtual Reality

VR is an extension of the FPS camera:

{% content-ref url="/pages/-LTVHycAndjz4PfE0E2D" %}
[Broken mention](broken://pages/-LTVHycAndjz4PfE0E2D)
{% endcontent-ref %}

### Third Person

A floating camera follows the player-controlled avatar, usually from behind.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ms-kb.msd.unimelb.edu.au/next-lab/virtual-reality/guides/vr-development-overview/unreal-engine-overview/unreal-engine-primer/player-vr-and-non-vr.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.