Troubleshooting
Performance and running multiple farms
Tune emulator count and routine scope using measured capacity instead of opening every configured farm at once.
Measure the right things#
- Available memory before a run and at peak concurrent emulator use.
- Routine duration from emulator start to final result—not only action tap time.
- LDPlayer responsiveness and game loading time on each profile.
- Windows paging, storage saturation and background security scans.
- Failure rate as concurrency increases.
Tune in this order#
- 1
Return to one concurrent farm
Establish a stable baseline.
- 2
Reduce routine breadth
Temporarily remove actions irrelevant to the farm’s purpose.
- 3
Stagger schedules
Avoid a large simultaneous queue spike.
- 4
Increase concurrency by one
Run several full cycles before increasing again.
- 5
Stop before saturation
The highest number that opens is not the highest reliable number.
LDPlayer settings#
Use the released VRA compatibility guidance for resolution, rendering and performance settings. Avoid changing resolution, DPI, language or major graphics settings across the fleet without retesting recognition and navigation.
Cloned profiles can accumulate different update, storage and rendering behaviour. A slow outlier may need LDPlayer maintenance rather than more VRA concurrency.
Still stuck?
Complete the evidence checklist before contacting support. Never send passwords, recovery codes, payment details or private licence material.