> 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/vehicles/vehicle-setup-import/vehicle-setup-sockets.md).

# Vehicle Setup - Sockets

Once your assets are imported you might want to add sockets for assisting on positioning things like the UI, pivots and interaction elements. On static meshes this can be done in your DCC, or adjusted after import in engine. For more information see the [sockets page on the Unreal Engine Wiki](https://docs.unrealengine.com/4.27/en-US/WorkingWithContent/Types/StaticMeshes/HowTo/Sockets/)

The hatchback meshes come with sockets already positioned in Maya

In the Unreal 5 branch the vehicles have various sockets applied to static meshes


---

# 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/vehicles/vehicle-setup-import/vehicle-setup-sockets.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.