Skip to main content

Installing game content

There are only two steps in this section:

  1. Unpacking the archive
  2. Installing game content on hardware

Let's start with the first stage:

Unpacking the archive

After you have been sent a link, you need to download the archive and unpack it, below we attach a link to our unzipboxer (7Zip).

7Zip Decompressor

Zip.png

Go to install 7Zip:

Installation takes place in two clicks.

Instal 7zip Start.png              Instal 7zip finish.png

Unpacking the archive, click on the PCM archive and select Unpack to " XXX_x. x.x. xxx\"

2024-06-30_13-53-14.pngimage.png

In this way, we unpacked the archive with the game content, then we can proceed to install it on different devices. (The archive can contain such folders as: Windows_Server, Windows_Admin, Android_Tablet, Android_Oculus, Android_Pico)

The second stage is even easier:

After you have unpacked the archive, you will see the following folders::

Including.pngimage.png

In order to install game content, you will need:

There will be a video in this place.

  • Connect the helmet to a computer running on a Windows system (Windows 10 or Windows 11);
  • In the helmet, give permission to connect;

image.png

  • Open the folder you need, depending on your helmet (Meta/Pico);
  • Run the install file Instal.bat, you will see the installation window open;

If suddenly you don't get a notification when you connect the helmet to your computer, then run the installation file. It won't install it, but it will display the Allow USB Debugging window

image.png

  • Wait for the installation window to close AUTOMATICALLY.

Possible installation errors:

No connected devices

There may be several reasons:

  1. You don't use a high-quality wire to connect your helmet to your computer;
  2. You didn't give permission to connect your helmet;
  3. You haven't enabled Developer Mode or USB Debugging (See Configuring helmets).
The installation window closed, but the application did not install.

Most likely, your ADB files are buggy. To solve this problem, the Kill_adb file is located in the folder.bat run it and try installing it again.

Go back to the Content