If you're having trouble with slow model viewing, bad frame rates, or browser crashes, the scene is probably too complex for your device or browser.

'material_packing': 1, Rendering Performance If you don't need to keep the meshes and materials separated in a Viewer API application, you can enable these optimizations in your URL options: 'merge_materials': 1, Geometries are not merged for animated objects or transparent objects, up to a maximum of 100 geometries per material. Scene optimization is disabled by default in the 3D Settings editor and when using the Viewer API.

Remove unused normals & tangents (this can also happen during processing in some cases).

Merge meshes (geometries) that share the same material.

The following things happen during scene optimization: It usually does not take much time, but the more complex the scene, the longer this will take. This can greatly improve viewer performance. While not technically part of the 'download', several scene optimization processes take place before the scene is rendered. A solid color background is the best, as it requires no download. A fixed image background also needs to be downloaded. HDRi environments are large images, and if you are using one for the background and/or lighting, it needs to be downloaded. The higher the vertex count / polygon count of your model, the longer it will take to download.

Visit the Materials & Textures article and texture performance in this article for more details. We optimize texture file size after you upload a model or make changes to materials, and we will never use a texture larger than 8192×8192 pixels. However, you should minimize the number of textures and the size of textures as much as possible. TexturesĪll the texture images need to be downloaded, so using many high-resolution textures can greatly affect download time. Download Timeīefore a model or scene can be rendered, the viewer needs to download and prepare all the required assets. This is what happens during the Loading 3D Model screen as well as the first moments of rendering when higher-resolution textures are loaded (the blue loading bar across the top of the viewer - if you want to avoid this step and only display the model when the full resolution textures are ready, try the preload embed parameter). Many different factors can affect how long a model takes to load and how well it performs after it's loaded. This is even more important to consider for mobile users. However, WebGL is hardware-accelerated, so the viewer's performance depends greatly on the machine displaying it. In theory, there's no limit to the complexity of models that can be displayed.

Walkthrough sketchfab models