> For the complete documentation index, see [llms.txt](https://doc.realvirtual.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.realvirtual.io/advanced-topics/troubleshooting.md).

# Troubleshooting

## What You Should Do First

Unity projects are complex and can sometimes encounter issues when upgrading, moving files, or installing/uninstalling packages. If you're upgrading from an existing version, it's essential to review the release notes for any known issues related to the upgrade. Additionally, our forum can guide you through common problems.

Here are some general steps to follow for troubleshooting:

1. **Check the Console Log**:\
   Start by reviewing the console log to see if any messages give you a hint about the problem.
2. **Clear Cached Data**:
   * Close Unity.
   * Delete the `Library` folder in your project directory to clear cached data and force Unity to rebuild the project.
   * Restart Unity. Unity will regenerate the necessary files from scratch.
3. **Upgrading to New Versions**:
   * If issues persist after upgrading, close Unity again.
   * Delete the entire `realvirtual` folder from your project. This will remove all realvirtual.io assets and configurations.
   * Open Unity again. Your scene references should remain intact.
   * Re-import the realvirtual.io Asset to restore all components and preserve references in your scenes.

Following these steps should resolve most issues while maintaining the integrity of your references to realvirtual.io components in your user scenes.

## Contacting Support

If you still experience issues, please post on our public support forum at [forum.realvirtual.io](http://forum.realvirtual.io). This allows others to learn from your experience.

When posting a support issue, please include the following:

* **Version Information**: Always provide the version of realvirtual.io Professional/Starter and realvirtual.io Simulation you are using (search for "version" in your project folder to find the version numbers and check the properties in the inspector).

<figure><img src="https://260262196-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpYxFg97YnJX96UzNNTSd%2Fuploads%2Fgit-blob-9fe58bc6ab338eb37ebb287c234ee29c1d920f5a%2Fimage.png?alt=media" alt=""><figcaption><p>Getting the version numbers.</p></figcaption></figure>

* **Full Console Log**: Include your full console log. On Windows, you can find it at `%LOCALAPPDATA%\Unity\Editor\Editor.log`. For other systems, refer to Unity's documentation: [Unity Log Files](https://docs.unity3d.com/Manual/LogFiles.html).
* **Reproducible Project**: Prepare a project where the issue can be reproduced. Specify the scene where the issue occurs and ensure it's directly visible when starting the scene.
* **Upload Your Project**: Upload the full project, including the scene, to [realvirtual.io/send](https://realvirtual.io/send). The upload will be private and only visible to our support team. In the upload comments, specify which scene we should open to check your issue.


---

# 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://doc.realvirtual.io/advanced-topics/troubleshooting.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.