> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/platform-documentation/catalog-2.0-docs/project-data/augmented-reality/ar-settings.md).

# AR Settings

There are additional AR properties

#### Exportable to AR

The user is able to determine the behavior of a given asset relative to exportability by way ot the Exportable to AR dropdown in the properties panel of a model asset.<br>

<figure><img src="https://content.gitbook.com/content/efQOUWnh8WUpteoAKY9N/blobs/qBmHQnC0pYgLwYmVckld/ARSettings_ExporttoARsettings.png" alt="" width="563"><figcaption></figcaption></figure>

#### Vertical AR - Apple Only

Clicking the top of the hierarchy reveals the AR placement field.<br>

<figure><img src="https://content.gitbook.com/content/efQOUWnh8WUpteoAKY9N/blobs/re097VGOlmjuSr1eMLZt/ARSettings_ARPlacement.png" alt=""><figcaption></figcaption></figure>

Horizontal is the default setting.

Vertical wall to wall it is going to anchor this back part of the object to the wall.

Vertical ground to wall anchors the bottom of the object to the wall.

When the view in space button is pressed, the property is set based on what is selected on the model.

Another way to set AR Placement is by using the attribute and rules system. For example, a set of speakers may be tabletop or wall-mounted. An attribute accounting for these two types of display can be leveraged within the rules system to set the AR Placement as desired.


---

# 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://community.threekit.com/platform-documentation/catalog-2.0-docs/project-data/augmented-reality/ar-settings.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.