> For the complete documentation index, see [llms.txt](https://apertus.gitbook.io/vr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apertus.gitbook.io/vr/vlft_application/local-user-interface.md).

# Single Player

The Single Player Interface can be used for testing the resources and the animation on a local machine.

![](/files/-M_phh4IROrgT1IaMIej)

The "Info" contains the properties of the clicked object. This menu element can be toggled to hide/show by the ▽

By the help of the "Manipulator", the selected/clicked object can be moved to the desired place. This menu element can be toggled to hide/show by the ▽

The "Animation" menu allows controlling of the play of the pre-recorded motions of the objects. This menu element can be toggled to hide/show by the ▽

![](/files/-M_pk283x1b-6RYbiL2B)

The animation can be controlled by the pause and stop buttons. The current state of the objects can be toggled to hide/show by the "show headers" checkbox.&#x20;

The "Screenshot" Button and the "Screencast" Button allow the possiblity to make a picture or a video which will be saved into the installation folder.


---

# 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://apertus.gitbook.io/vr/vlft_application/local-user-interface.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.
