Skip to main content

Troubleshooting

The usual suspects, in order of how often they come up.

"Waiting for MSFS" — nothing happens​

  • Is Microsoft Flight Simulator 2024 or 2020 actually running? GlassOut looks for the sim by process name.
  • Is GlassOut running as Administrator? Capturing panels from the sim requires elevated access. The app prompts for UAC on first launch; if you clicked "No", quit and relaunch.
  • If MSFS is detected but panels don't appear, keep going — panel discovery only kicks in once you're in a flight (the cockpit, not the world map).

DirectX 11 warning​

GlassOut only supports DirectX 12. Switch MSFS to DX12:

  1. MSFS → Options → General → Graphics.
  2. Set Graphics API to DX12.
  3. Restart MSFS.

Mobile app can't find the engine​

  • Phone and PC must be on the same Wi-Fi network. Most phones put guest / 5 GHz / 2.4 GHz SSIDs on isolated VLANs. If in doubt, join both devices to the same SSID.
  • On iOS, make sure you granted Local Network permission the first time the app scanned. If you declined, enable it under Settings → GlassOut → Local Network.
  • Corporate and hotel Wi-Fi often block multicast. Use the manual IP + port fallback on the Discovery screen.
  • VPN on the phone or PC will also break mDNS. Turn it off or use manual entry.

Panels look soft or stutter on a phone / tablet​

Streaming is bandwidth-sensitive and Wi-Fi is almost always the limit.

  • Prefer a 5 GHz SSID over 2.4 GHz — 2.4 GHz is heavily congested and drops hard through walls.
  • Keep the device in good signal range of the router. A single wall often costs more throughput than you'd expect.
  • Turn off Low-power mode on the phone. It throttles the Wi-Fi radio hard enough to cut sustained throughput 50–80%.
  • Lower the Frame rate slider in the mobile app's Settings sheet (gear icon on the Connected screen). 20 fps on a stable link looks better than 30 fps on a thrashing one.
  • To see exactly where the latency is coming from (network, decode, paint, or the engine's pre-send queue), enable the Stream debug overlay toggle in the mobile / PC Settings and read Stream diagnostics. Turn it off again after you diagnose — when off, it's free.

No panels in Discover tab​

  • Is the aircraft fully loaded and in the cockpit view?
  • Some aircraft take a few seconds to register all panels after spawn. Wait 10-15 seconds, then refresh.
  • If nothing shows up after a minute, try restarting MSFS. When that still doesn't help, Settings → Diagnostics → Upload diagnostic logs and send us a note — we'll dig in.

Fragments out of alignment​

  • Atlas layouts can shift across MSFS updates. Open the fragment editor and nudge the crop back into place.
  • If you're editing a fragment on a different aircraft than it was originally captured from, the source panel's ID may not exist. The Fragments tab shows a grey dot on fragments whose source panel is offline.

Touch panels not responding to taps​

  • Raise Profile → Settings → Touch Panel Click Delay to ~300–500 ms. Some instruments (WT G3000 GTC, MCDU) need a hover before the tap registers.
  • The delay applies to every viewer of that profile — on the PC, phone and any browser.

Viewer windows reopen in the wrong place after Run​

  • Your monitor setup has changed since you saved the layout. The Screen Mismatch banner should appear; use it to open everything on the primary display, then re-arrange and re-save.

"License moved to another device"​

Someone (maybe an earlier install on a reinstalled OS) activated the same license elsewhere. GlassOut will have cleared the local copy. Either:

  • Reactivate here (which will deactivate the other machine), or
  • Contact support to increase your device limit.

Logs​

Every session writes to a dated log file. Paths:

  • PC app: %LOCALAPPDATA%\Temp\GlassOut\pc\session-<ISO>.log
  • Engine: %LOCALAPPDATA%\GlassOutEngine\logs\session-<ISO>.log

Only the five most recent per app are kept. Use Settings → Diagnostics → Upload diagnostic logs to send them to support in one click — no raw license data is included.

Still stuck?​

Email contact@flyingart.dev with:

  1. A description of what you tried.
  2. The output of the log upload (you'll see a success message with an ID).
  3. Aircraft + MSFS version.