A package can take time to prepare after you request it. TREKK360 tracks preparation separately from the final download to your computer. Wait for the completed package action rather than submitting the same request repeatedly.

Use Downloads for prepared packages when your account includes that page. Package availability depends on your workspace, project access, and any share restrictions.

Retrieve a package in Downloads

  1. Confirm the active Workspace and open Downloads from the navigation.
  2. Find the Package Name. Check Project, Files, Created, and Completed to distinguish similar requests.
  3. Use Search downloads... to narrow the table. Check any active time-range or project filters if the expected package is missing.
  4. Read Status. In Progress means preparation is still running. Completed means the package finished preparing.
  5. For a completed package with an available link, open Actions and choose Download.

The Download action is disabled while a package is not ready or has no usable download link. Completed preparation is not proof that your browser saved the ZIP; confirm the final file in your browser's downloads.

To create a package, return to the appropriate Viewers row and use its Download Package action. Follow Deliverables for component selection and access restrictions.

Interpret preparation status

  • Status: Pending. Meaning: The package request is waiting to start. Next action: Wait and check the existing request again.
  • Status: In Progress. Meaning: The selected contents are being prepared. Next action: Allow preparation to finish.
  • Status: Completed. Meaning: Preparation finished. Next action: Choose Actions, then Download when a link is available.
  • Status: Failed. Meaning: The package could not be prepared. Next action: Record the package and message, then contact Support.

A package's file count can include supporting files such as textures and related outputs, so it may differ from the number of structures selected. The Size column describes the package result when available, not the size of every original capture in the project.

Distinguish similar packages

Check Package Name, Project, Created, Completed, file count, and size before choosing a result. A later package can contain different components or a different set of structures. If you named the package when requesting it, use that name to find the intended delivery.

When the row is missing, check the workspace, project and time-range filters, clear the download search, and use Previous or Next where more pages are available. An empty Downloads list does not prove that no viewer outputs exist; return to Viewers to check the source and request the appropriate package.

Deleting a prepared package

The Delete action in Downloads removes the generated package request and attempts to remove its package file. It is separate from deleting original source uploads. Do not delete a package you still need to retrieve or share, and read the confirmation before proceeding.

When a download is unavailable

If the browser does not save the file after Download, check whether it blocked the new tab and review its downloads list. If an older link no longer works, reopen the current package action; links and generated packages can expire. Request a fresh package when the old result is no longer available.

For pending or in-progress work, allow the existing request to finish. For failed preparation, record the package name, project, requested contents, time, and visible message. Report whether the source viewers still open. This helps Support distinguish a package problem from missing viewer outputs.

Shared viewers require download permission from the share, and trial access does not grant viewer exports. See Viewer Problems for expired, revoked, or still-preparing shared package links.