Start here

Installation and first-run setup

A release-ready checklist for installing VRA, completing guided setup and reaching the Command Centre safely.

Before installing#

  • Download only from the official Young Studio release location announced on youngstudio.uk.
  • Check the published version, release notes and signing information before opening an installer.
  • Close unnecessary emulator instances and allow Windows updates to finish.
  • Keep an existing backup of important LDPlayer profiles. Installing VRA should not be treated as an emulator backup.
No public installer today

VRA is not publicly downloadable yet. Any third-party download claiming to be the current VRA installer should be treated as untrusted.

Complete guided setup#

  1. 1

    Open the first-run guide

    Read each environment check rather than clicking through warnings.

  2. 2

    Locate LDPlayer

    Select or confirm the supported LDPlayer installation and allow the profile list to load.

  3. 3

    Review detected profiles

    Match profile names to the farms you recognise. Detection is not permission to automate all of them.

  4. 4

    Choose initial capacity

    Use one concurrent farm for the first controlled run.

  5. 5

    Enter the Command Centre

    Confirm Environment Health is ready before creating a routine.

Permissions and security#

Use the least Windows privilege that the released installer and runtime documentation require. Do not disable antivirus, firewall or account controls merely to force an installation through.

A security product warning should be checked against the official download, signature and current release notes. Send the exact warning to support if it cannot be reconciled.

A successful first run means#

  • The intended LDPlayer profile opened—not merely any available emulator.
  • Viking Rise reached a recognisable foreground screen.
  • A small, low-risk routine completed or produced a clear no-action-needed outcome.
  • The Command Centre recorded the farm and step results.
  • No other emulator profile or Windows application received unintended input.

Still stuck?

Complete the evidence checklist before contacting support. Never send passwords, recovery codes, payment details or private licence material.

Prepare your report