Assets uploaded to Polyverse are automatically preprocessed to ensure seamless compatibility with a wide range of different viewers and environments.
Preprocessing is automatically done by Polyverse when a new asset is ingested in a library.
Depending on the asset type, different types of processing occurs:
Meshes are automatically processed to be viewable on the web, this includes converting CAD file formats to 3D or converting non web-compatible formats to formats viewable on the web. Additionally, other variants are created such as a variant viewable in AR.
Preprocessing:
Materials are automatically processed to be viewable on the web.
Preprocessing:
Environments are automatically processed to be viewable on the web.
Preprocessing:
Images are automatically are automatically processed to be viewable on the web.
Preprocessing:
Audio and Video Assets are automatically processed to be viewable on the web.
Preprocessing:
InstaMAT Packages are automatically processed to ensure safety and compatibility with Polyverse and InstaMAT Studio. Learn more about storing InstaMAT Packages in Polyverse.
Preprocessing:
When uploading InstaMAT packages, it is best to use the "Cook" functionality of InstaMAT Studio to save the package asset. This ensures that all dependencies are included in the package asset uploaded to Polyverse.
No automatic processing is done on data blocks.
No automatic processing is done on JSON files.
While Polyverse is built to be compatible with as many file formats as possible, errors may still happen if malformed assets are uploaded. The following page contains more information on Asset Preprocessing Errors and Messages.