Collect Autodesk VRED crash logs

Locate VRED's log files in the Windows Temp folder and grab the callstack so support can diagnose a crash.

When Autodesk VRED crashes or behaves unexpectedly during an Innoactive Spatial streaming session, the VRED log files are usually the fastest way to understand what went wrong. VRED writes these files to a temporary folder on the workstation — this guide shows where to find them and which file is most useful for support.

Where VRED stores its log files

VRED writes its log output to a per-edition subfolder under the current user's Windows temp directory.

  1. Open File Explorer.

  2. Paste the following path into the address bar and press Enter:

    %LOCALAPPDATA%\Temp\VREDPro\log

    This expands to the equivalent absolute path:

    C:\Users\[Your_Username]\AppData\Local\Temp\VREDPro\log

  3. Sort the folder by Date modified to see the entries closest to the time of the crash — these contain the terminal output leading up to it.

Which file to attach to a support ticket

The folder typically contains several files. The one that is almost always the most useful is:

  • callstack.txt — the stack trace captured at the moment VRED crashed. This is the single most informative file for diagnosing a crash, so always include it if it is present.

Alongside callstack.txt, also attach the most recent .log file (usually named after the VRED edition and a timestamp), which contains the runtime output up to the crash.

If you are not sure which files belong to the crashing session, zip the entire %LOCALAPPDATA%\Temp\VREDPro\log folder and attach it — support will pick out what they need.

  1. Reproduce the crash (or confirm VRED has just crashed).
  2. Do not restart VRED yet — opening VRED again can overwrite the log files for the affected session.
  3. Open %LOCALAPPDATA%\Temp\VREDPro\log in File Explorer.
  4. Sort by Date modified and confirm the timestamps match the crash.
  5. Copy callstack.txt and the latest .log files to a separate folder, or zip the whole log directory.
  6. Attach the archive to your support ticket.