Developer options in an Eagle 3D Streaming configuration let you pass values into your app at launch, choose where it runs, and get hold of the logs when something goes wrong.
Stream link › Edit Config › Advanced Options › Developer. These are the settings you reach for while building and diagnosing, rather than ones a viewer ever notices.
Two ways, and the difference is who decides the value.
| Set by | Use it when | |
|---|---|---|
| Parameters To Pass To App | You, in the configuration | The value is the same for everyone opening this link. |
| Append Parameters To URL | Whoever builds the link | The value differs per visitor — a customer name, a starting scene. |
Appending must be enabled in the configuration before a URL parameter will reach your app. With it off, the parameter is simply ignored — the stream runs, your value never arrives, and nothing reports a problem.
Console Cmds To Pass To Unreal App runs Unreal console commands as the session starts — the same commands you would type into the in-editor console, applied automatically to every session on this configuration.
This is where per-app engine tuning belongs: a resolution scale, a quality setting, anything you would otherwise ask every viewer to set for themselves.
Select region decides which part of the world serves the stream. Pick the one nearest your viewers — distance is latency, and latency is the thing people describe as "laggy" regardless of frame rate.
After launching, the Info button in the stream reports which region actually served it. Worth checking rather than assuming, particularly after changing the setting.
Three separate ways to see what Unreal said, and they suit different moments.
| Setting | Where the log goes | Best for |
|---|---|---|
| Print UE log in browser console | The browser's developer console, live | Watching a problem as it happens, on your own machine. |
| Auto-Download UE Crash Log — not working at present | A file on the viewer's device, on crash | A crash you can reproduce, where you have the device. |
| Email To Send Log Upon App Crash | An address you choose | Crashes you are not present for — a customer's session, an overnight event. |
Platform says whether the build is for Windows or Linux. A Linux build must have it set to Linux; left on Windows, its sessions wait for a Windows machine that will never run it. See upload and stream a Linux build.
The format your application compresses the picture into. The default is H264, which is what every stream on the platform uses and what every machine and every viewer can handle. AV1 sends the same picture in roughly a third less bandwidth but needs an RTX 40-series graphics card or newer to produce it; VP9 and VP8 are encoded on the processor instead of the graphics card.
Because two separate things have to agree — the machine has to be able to make it and each viewer’s browser has to be able to play it — the codec a session actually streams can differ from the one set here. What happens in each case, and how to check what a session really used, is on its own page.
The four choices, how the fallback works on the machine and in the browser, and how each behaves on different connections.
Sets the quality a session starts at, rather than leaving it to be negotiated. Useful when you know your audience's conditions — a venue with good wired network, or an event where you would rather have a steady picture than the best possible one.
Access, interface and loading screen settings.
Last updated