Stream to 3D — Logs & Diagnostics (Before contacting support)
This page explains what to include when you need help, and where to find logs. Providing the items below usually saves a lot of back-and-forth.
Contents
- What to include
- Stream to 3D log (streamto3d.log)
- Conversion logs (batch CSV + per-file logs)
- Privacy / redaction notes
What to include
- Your goal/workflow: Play, Stream, Convert, or Live Capture.
- Your store/edition: Steam vs Gumroad vs Itch (and which product/edition if known).
- Stream to 3D version: shown in the app (or from the installer/store listing).
- Your output format: SBS/TB, Half/Full, and whether the player/device is set to the same layout.
- Your player/device: e.g. MPC-HC, PotPlayer, VLC, Pigasus, Skybox, Bigscreen, Virtual Desktop, Kodi, 3D TV/projector.
- Any error codes: especially LVE0xx (see Error Codes).
- Key screenshots: Settings summary, Tools page, and Wizard summary (if used).
- Logs: see the sections below.
Stream to 3D log (streamto3d.log)
Stream to 3D is a Unity application. On Windows, the Unity player log is typically located at:
C:\Users\<username>\AppData\LocalLow\IWAHDK\StreamTo3D\streamto3d.log
If you can’t find it, search your PC for streamto3d.log and look for the IWAHDK\StreamTo3D folder.
Conversion logs (batch CSV + per-file logs)
Batch conversion creates a summary log (including a CSV) listing conversion results and, for failures, the path to a per-file log used for diagnosis.
See the conversion guide for how batch conversion logging works and what the CSV contains:
Privacy / redaction notes
- Logs may contain local file paths and device names. Redact anything sensitive if needed.
- Do not share license keys publicly. If support needs them, send them via email.
Support entry point: Stream to 3D Support.
Last reviewed: 2026-02-22