Documentation

​
​

Development

User Acquisition

Monetization

Industry

Asset Transformer SDK

2026.1

Supported
​

User Manual

Python API

C# API

Changelog

Discussions

Asset Transformer SDK

2026.1

Supported
​
​
​
Get started
  • System requirements
  • Licensing
  • Setup
  • Migrate from Scenario Processor
Framework
  • Framework
  • Preferences
Input/output files
  • Supported formats
  • Import files
  • Export files
  • Export textures
  • CAD vs Mesh
Scene
  • Product structure
  • Occurrence
  • Component
  • Material
  • Image
Algorithms
  • CAD
  • Healing
  • Optimization
  • Combine and bake
  • Reconstruction
  • UVs
Viewer
  • Viewer
Pixyz UI
  • Setup
  • Overview
  • Create a custom UI
Guidelines
  • Data preparation
  • Process point clouds
Debug and diagnose
  • Log files
  • Debug best practices
Other
  • Samples
  • Glossary
  1. Asset Transformer SDK (ex Pixyz)

Log files

Learn about Pixyz log files, including their default storage locations and configuration options.
Read time 1 minute
Last updated 9 months ago
Pixyz produces log files. You can use these log files to understand where any problems happened in your workflow or application.
Log files are stored in different locations depending on the operating system it runs on. The default locations are outlined on this page, but you can also use certain functions to control when and where Pixyz generates log files. For more information, see the log files and verbose functions in the API documentation.
Note
Log files are written to disk at exit.
Default directory location for log files:

OS

Path

Windows
%APPDATA%/PixyzSDK/
Linux
~/PixyzSDK/
macOS
~/PixyzSDK/
Important
Change "PixyzSDK" in the path if Pixyz was initialized with a custom product name.
Copyright © 2026 Unity Technologies
LegalPrivacy PolicyCookiesDocumentation Terms of UseDo Not Sell or Share My Personal InformationYour Privacy Choices (Cookie Settings)

"Unity", Unity logos, and other Unity trademarks are trademarks or registered trademarks of Unity Technologies or its affiliates in the U.S and elsewhere (more info here). Other names or brands are trademarks of their respective owners.

Some pages are machine-translated for convenience, and may contain inaccuracies. In the event of conflicting information, the English version is authoritative.

    Report a problem with this page