Skip to content

Installation

Before you dive into the world of realvirtual.io, you’ll need to set up your development environment correctly. Here’s a step-by-step guide to get you started.

Install Unity 6.3 LTS through the Unity Hub. In Unity Hub, the version number is displayed as 6000.3 (e.g., 6000.3.5f1). For detailed instructions, refer to Unity’s official installation guide.

🔗 Unity 6 Installation guide

  1. Open Unity Hub and click New project.
  2. Select Universal 3D under Core templates to use the Universal Render Pipeline (URP).
  3. Set a project name and choose a location for the project folder.
  4. Ensure Editor version 6000.3 (Unity 6.3 LTS) is selected.
  5. Click Create project.

Creating a new Universal 3D project with Unity 6.3 LTS

The installation depends on where you purchased realvirtual. Choose the section that applies to you.

  1. Open Window > Package Manager in Unity.
  2. Select My Assets in the left panel.
  3. Find realvirtual Starter (and realvirtual Professional if purchased) and click Download.
  4. After downloading, click Import to install the UPM packages into your project.

For your first installation, download the .tgz package files from the realvirtual Customer Portal. The link and login credentials are provided on your invoice.

After downloading, install the packages in Unity:

  1. Open Window > Package Manager.
  2. Click the + button in the top-left corner and select Install package from tarball….

Install package from tarball in Package Manager

  1. Navigate to the downloaded .tgz file and select io.realvirtual.starter first.

Select the starter package tarball file

  1. Wait for the import to complete. This may take a few minutes.
  2. Repeat the process for io.realvirtual.professional if you purchased the Professional edition.

realvirtual Professional installed via tarball in Package Manager

After installing the packages, the realvirtual menu appears in the Unity menu bar. Use the built-in User Hub to manage updates:

  1. Go to Tools > realvirtual > User Hub in the Unity menu.

Open User Hub from the realvirtual menu

  1. In the Login tab, enter your Invoice Number, Billing ZIP Code, and Email. Click Login.

User Hub login with invoice credentials

To receive automatic update notifications, activate the realvirtual UPM Registry:

  1. In User Hub, go to the Packages tab.
  2. Click Activate UPM Registry.

Activate UPM Registry in the Packages tab

  1. Unity will add a scoped registry to your Project Settings > Package Manager and show a confirmation dialog.

Scoped registry added to Project Settings

  1. Future updates will now appear automatically in the Package Manager under My Registries. Use Check for Updates in User Hub to verify.

Alternatively, you can download newer versions from the Downloads tab in User Hub (or from the Customer Portal) and install them via Install package from tarball as described above.

Download packages from the User Hub Downloads tab

Missing Signature warning — safe to close

Invalid Signature warning — safe to close

After installation, a dialog will ask if you want to import the Getting Started demo scene. Click Import Now to get started right away.

Import the Getting Started demo scene

You can import additional demo categories at any time using two methods:

Via Package Manager: Select realvirtual Starter (or Professional) in the Package Manager, go to the Samples tab, and click Import for the demo categories you want.

Import demo scene categories from the Samples tab

Via Demo Scenes Browser: Go to Tools > realvirtual > Demo Scenes Browser in the Unity menu. This window shows all available demo scenes organized by category with descriptions.

Open Demo Scenes Browser from the realvirtual menu

Demo Scenes Browser with categories and scene descriptions

The Getting Started demo scene opens automatically after import. It showcases a complete automation cell with conveyors, a robot, sensors, and a machine — all working together.

realvirtual 6.3 demo scene

Press Play in the Unity Editor to start the simulation and see the automation in action.

If you see red error messages in the Console related to the Input System, make sure that the Active Input Handling in Project Settings > Player > Configuration is set to Both (old and new Input System).

If your demo scene appears pink, you may be using the wrong render pipeline. We recommend switching to the Universal Render Pipeline (URP). See Render Pipelines for details.

If you encounter problems with text in the Runtime UI, go to Window > TextMeshPro > Import TMP Essential Resources to install the required components.

(Optional) Clean Up Unnecessary Unity Demo Folders

Section titled “(Optional) Clean Up Unnecessary Unity Demo Folders”

To keep your project clean, you can delete Unity’s default demo assets if present:

  • Scenes
  • Settings
  • TutorialInfo

If you have an existing project using realvirtual 6.0.x (the .unitypackage version), follow these steps to migrate to the new UPM package format.

  1. Open Unity Hub and change the Editor Version of your project to 6000.3 (Unity 6.3 LTS).
  2. Accept any compatibility warnings and let Unity convert your project.
  1. Close Unity completely.
  2. Delete the Assets/realvirtual folder from your project directory (this is the old .unitypackage content).
  3. Delete the Library folder to force Unity to regenerate all cached metadata.
  1. Reopen your project in Unity 6.3 LTS. You will see compilation errors — this is expected.
  2. Install the new UPM packages following Step 3 from the installation instructions above (either via Asset Store or Customer Portal tarball).
  3. After the packages are installed, compilation errors should be resolved.
  1. Check the Console window for any remaining errors.
  2. Open one of your scenes and verify that all components, references, and materials are intact.
  3. If materials appear pink, go to Tools > realvirtual > Settings > Switch to Universal Render Pipeline (URP) to convert them.

realvirtual.io 6.0 (Unity 6 — .unitypackage)

Section titled “realvirtual.io 6.0 (Unity 6 — .unitypackage)”
Tutorial realvirtual.io 6 and Unity 6 Installation

Install Unity 6000.0 LTS (Unity 6) through the Unity Hub.

  1. Open Unity Hub.
  2. Select Universal 3D under Core templates.
  3. Ensure Editor version 6000.0 LTS is selected.
  4. Click Create Project.
  • Direct Purchase from realvirtual.io:
    1. Download the realvirtual.unitypackage file from your account on the realvirtual.io download website.
    2. Drag and drop the file into the Unity Project window, or go to Assets > Import Package > Custom Package.
  • Unity Asset Store:
    1. Open Window > Package Manager.
    2. Under My Assets, locate realvirtual.io 6 and click Download, then Import.

When prompted about a URP Upgrade, select Install / Upgrade.

Installation Warning

Import Unity Package

After import, the demo scene opens automatically.

Demo scene after installation

See the problems and fixes section above — the same issues and solutions apply.


If you haven’t already, install Unity on your computer. Unity offers both free and licensed versions, depending on your use case. Check Unity’s official website here to determine which version suits your needs.

Installation of realvirtual.io 2022 (old deprecated version)

Our new releases is always based on the latest Unity Long Term stable release. Our main version number (e.g. 6) always corresponds to the Unity version number. For example to run realvirtual.io 2022.09 you need Unity 2022.03 LTS.

We highly recommend installing Unity Hub, a tool that simplifies managing multiple projects and Unity installations. You can download Unity Hub from Unity’s official download pages.

Launch Unity and create a new empty project by selecting “New.” Choose a location on your computer to store your project files and give your project a name. Then, click “Create Project.”

When prompted to choose a template, select the standard 3D template. This will form the foundation of your project:

Creating a new Unity Project with the Unity Hub

5. Ensure .Net Standard Framework 2.1 and Mono are Enabled

Section titled “5. Ensure .Net Standard Framework 2.1 and Mono are Enabled”

By default, Unity should have .Net Standard 2.1 and Mono enabled. However, in some cases, especially when integrating realvirtual.io into an older project, this setting might be incorrect. To confirm or change this setting:

  • Go to Player Settings by selecting “Build Settings” > “Player Settings.”
  • Under “Configuration,” change the Scripting Runtime Version to ”.NET Standard 2.1”

For the scripting backend, it’s recommended to start with Mono rather than IL2CPP, as Mono typically compiles much faster.

Selecting the .Net Standard 2.1 in the Unity Player Project Settings

Go to the Unity Asset Store and purchase the version of realvirtual.io that suits your needs, whether it’s Lite or Professional.

You can import realvirtual.io directly from the Unity Asset Store or manually download the asset. To install it manually, follow these steps:

  • From the main menu, go to “Assets” > “Import Package” > “Custom Package…”
  • A new window will appear, displaying the contents of the realvirtual.io package. Select “All” and click “Import.”

Import custom package

This will show a new window with all the realvirtual.io package contents:

Please select All and Import.

After importing the realvirtual.io package, check for the following:

  • You should see an additional “realvirtual” folder (previously “game4automation” before 2022) in your project structure.
  • A new “realvirtual” menu should be available in the main menu bar.

Project view after realvirtual.io installation

In such cases:

  • Address the compile errors first to ensure there are none remaining.
  • Once errors are resolved, apply the standard settings by selecting “realvirtual” > “Apply Standard Settings” from the main menu.

Applying standard settings will configure:

  • Standard layer naming (for physics).
  • Standard physics collision matrix.
  • Standard light settings.

Congratulations! You’ve now completed the installation process and are ready to explore the Demomodel outlined in the documentation.