Skip to content
Main site Contact

VizSeek Release Notes

Documentation

New features, improvements, fixes and other updates to VizSeek.
Version: 5.12.0
Release date: August 7th, 2026

  • Added support for additional 3D and search-input file formats, including FBX, glTF, GLB, and IAS.
  • Added asynchronous search-input indexing so integrations can receive a file identifier immediately and monitor indexing progress.
  • Added attribute-based ranking for Search API integrations.
  • Added SharePoint source-scope support for Ask AI experiences, helping keep results aligned with documents a user can access.
  • Added richer duplicate and version context for AI search sources.
  • Improved RFQ category browsing: users can switch result categories instantly without a page reload.
  • Improved search-input viewing, thumbnails, document previews, and extracted metadata across RFQ and search workflows.
  • Improved compatibility with standalone and clustered deployments.
  • Improved 3D rendering reliability and added optional GPU-based rendering support.
  • Improved API documentation for shape-specific search, multi-value attributes, and ranked results.
  • Corrected RFQ auto-selection safeguards so high-deficit or unknown-deficit matches are not incorrectly treated as exact matches.
  • Fixed 3D overlay scale discrepancies for models using different units.
  • Fixed result-shape thumbnails for deployments using non-WebP image formats.
  • Fixed search results that could show missing or mismatched file hashes and metadata.
  • Fixed File Status behavior so clients can distinguish indexing, failure, and unknown-file states.
  • Fixed file deletion authorization and response status handling.
  • Fixed cases where file shape data could appear when it had not been requested.
  • Fixed on-premises synchronization and token-rate fallback failures.
  • Updated the API Documentation link to the external documentation site.
  • Added configurable thumbnail extensions.
  • Improved operational tracing for file-based search and AI requests.
  • No customer-facing known issues were formally recorded for this coverage period.