The stages an Eagle 3D Streaming upload and streaming session pass through, what each one is doing, and what it means when one of them stalls. This is the page to open when something is taking too long.
The Control Panel colours each phase: green passed, yellow a warning you can proceed past, red an error you cannot.
| Phase | What it does | If it stops here |
|---|---|---|
| 1. Application review | Checks the ZIP holds a packaged Unreal app with an executable, and that Pixel Streaming is enabled. Also scans for viruses. | Yellow: plugin not detected — you may continue, and it will not stream. Red: no Unreal app in the ZIP. |
| 2. Upload | Transfers the file. | A slow or interrupted connection. Press Retry, which restarts from phase 1. |
| 3. Acquiring | Begins at 50% uploaded; stores the ZIP on a machine. | Usually a ZIP missing files, or the connection dropping. Server problems here are rare. |
| 4. Preparing | Extracts and installs the build. | Same causes as phase 3 — an incomplete ZIP is the usual one. |
| 5. In queue | Waiting, if several apps are being processed at once. | Nothing is wrong. A long queue simply takes longer. |
| 6. Testing | Runs your app on a machine to confirm it streams. | The app itself — a crash on start, or resources beyond the hardware budget. |
| Phase | What is happening | If it stops here |
|---|---|---|
| 1. Opening the URL | The page loads. | — |
| 2. Requesting a slot | Asking for capacity. | See "stuck in the queue" below. |
| 3. Waiting for a machine | A GPU machine is being allocated. | For a Linux app, check the platform setting — a config set to Windows waits here forever. |
| 4. Acquiring | Downloading your app to that machine. Skipped if it is already there. | Large builds take longer the first time. |
| 5. Preparing | Extracting and setting up. Also skipped if already present. | — |
| 6. Launching | Your app starting. | The app's own start-up time — usually the largest share. |
| 7. Press play | Waiting for the viewer's click. | Not a fault. Browsers require one interaction before video. |
| 8. Streaming | Video is flowing. | — |
Phases 4 and 5 disappear once a machine already holds your app, which is why the same app can take 25 seconds one time and 12 the next with nothing changed. It is also what preallocation removes permanently.
A short queue when many people start at once is normal and resolves itself. Consistently queuing is not: it means no machine matching your configuration is free.
The platform setting if it is a Linux build; then your plan's concurrent-user limit, since every active session holds a slot; then whether sessions are being left open, which an idle timeout fixes.
What the wait is made of, and how to shorten the part that is yours.
Last updated