Start here
System requirements and a healthy Windows setup
Plan Windows, LDPlayer, memory, storage and display capacity before running one or many Viking Rise farms.
Current platform plan#
VRA is being built as a Windows desktop application for farms already available as LDPlayer profiles. Mac, mobile-only and browser-hosted game automation are not part of the current release plan.
Final minimum specifications will be published before release. Emulator load varies dramatically by LDPlayer settings, game state and the number of simultaneous instances, so a single farm count is not a reliable hardware specification.
| Area | Prepare for release |
|---|---|
| Operating system | A supported, fully updated 64-bit Windows version. |
| Virtualization | Hardware virtualization enabled and no unresolved hypervisor conflict affecting LDPlayer. |
| Emulator | A supported LDPlayer release with Viking Rise installed and stable. |
| Memory | Enough headroom for Windows, VRA and every concurrently open emulator—not every configured farm. |
| Storage | Fast local storage with free capacity for emulators, application updates and diagnostic evidence. |
| Display | A normal Windows display configuration; final scaling requirements will be documented before release. |
Capacity means concurrent farms#
You may configure more farms than the PC can run at once. Concurrency is the number of emulator profiles VRA may actively handle together. Schedules and queues can cycle a larger fleet through a smaller safe concurrency limit.
Start at one. Watch memory pressure, emulator responsiveness and run duration. Increase by one only after repeated stable runs. If Windows begins paging heavily, LDPlayer freezes or action durations rise sharply, reduce concurrency.
A machine that can just barely open a group of emulators is not ready to automate them reliably. Keep capacity for Windows, game loading, updates and evidence capture.
What Environment Health should establish#
- The VRA background service is reachable from the customer interface.
- LDPlayer tooling is installed and its profiles can be listed consistently.
- Configured farm mappings still resolve to the intended emulator profiles.
- Required folders are readable and writable without running the whole product as administrator.
- The selected concurrency is realistic for current system resources.
Still stuck?
Complete the evidence checklist before contacting support. Never send passwords, recovery codes, payment details or private licence material.