Skip to Content
AssetsAsset requirements3D Models

3D Models

Overview

3D models are the foundation of every configurator in Amaspace. A clean, well‑prepared model ensures stable performance, predictable behavior in the editor, and correct rendering across devices.

This guide describes the supported formats, file size limits, scale and transform rules, polygon and performance recommendations, geometry and UV requirements, shading and normals setup, export rules, and common issues to avoid.

When to upload a 3D model

Upload a production 3D model when you need to:

  • Represent the base product geometry in a configurator
  • Reuse the same model across multiple configurations or materials
  • Serve as the “source of truth” for geometry used by materials, PCOs, or product variants

Every product in Amaspace relies on a 3D model in some form: as a base model, a shared asset, or a geometry reference for configuration logic.

Supported formats

Amaspace supports the following 3D model import formats:

  • GLB (preferred)
  • GLTF
  • ZIP (import)

GLB is the recommended format because it packages geometry, materials, and textures into a single file and minimizes import and linking errors.

ZIP import is supported for cases where you need to upload multiple related files together (for example, a .gltf file with external textures and supporting assets). Use ZIP only when the model is not fully self-contained as a single GLB.

Rule: Only one main model should be uploaded per file (one main model per GLB/GLTF/ZIP import).

File size limits

  • Maximum file size: 30 MB per model

If a file exceeds this limit, optimize geometry and textures before uploading. Oversized models may fail to upload or cause performance and stability issues in the configurator.

Model preparation workflow

1) Prepare the model (foundation)

Before any optimization or export, ensure the model is structurally correct:

  • One clear main object hierarchy
  • No duplicate or unused meshes
  • No construction helpers or temporary objects

The model should represent only what is required for the final product.

2) Scale and transforms (critical)

Before export, always verify:

  • Scale: 1 unit = 1 meter
  • Rotation: model faces forward correctly
  • Transforms: all transforms applied (no unapplied scale or rotation)

Incorrect transforms frequently cause camera framing issues, incorrect interaction, and broken part selection inside the 3D Editor.

3) Polygon count and performance

Amaspace does not enforce a hard polygon limit, but runtime performance depends on:

  • Total triangle count
  • Number of separate meshes
  • Number of materials
  • Texture resolution

Recommended ranges:

  • Simple products: under 100k triangles
  • Complex products: 150k–300k triangles
  • CAD‑based demos: higher counts are acceptable if optimization time is limited

When working under tight deadlines, geometry decimation is acceptable only if shading is corrected afterward.

4) Geometry and topology

Follow these rules for clean, production‑ready geometry:

  • Remove hidden and internal faces
  • Avoid unnecessary subdivisions
  • Keep edge flow consistent on curved surfaces
  • Manually triangulate areas with strong curvature (fabric folds, rounded silhouettes)

Incorrect quad diagonals can break the silhouette after triangulation. Always verify triangulation before export.

5) UV requirements

UVs must be production‑ready:

  • No overlapping UVs (unless intentional for tiling)
  • Consistent texel density
  • Proper padding between islands
  • Clean UVs for any baked textures

For short or prototype pipelines, UVs may be simplified. For final production assets, clean UVs are required.

6) Normals and shading

Amaspace relies on correct vertex normals for shading quality.

Recommended approach:

  • Use Weighted Normals
  • Use Data Transfer when needed
  • Manually adjust normals in Edit Mode (Alt + N) when required

Normal maps are not required if shading is handled correctly through geometry and vertex normals.

7) Ambient Occlusion (optional)

Ambient Occlusion (AO):

  • AO is optional
  • Skip AO for ultra‑short pipelines or fast demos
  • Bake AO only after final UVs are ready

AO should never be used to compensate for incorrect lighting, geometry, or shading.

8) Export and verification

Before exporting:

  • Apply all transforms
  • Verify triangulation
  • Check shading in a neutral environment
  • Ensure materials and textures are linked correctly

Export format: GLB

After export:

  • Test the file in a WebGL viewer (for example, Three.js Editor)
  • Confirm scale, orientation, and shading

Always validate the exported file before uploading to Amaspace.

Common issues

  • Model imports too large: geometry or textures not optimized
  • Broken shading: incorrect normals or triangulation
  • Wrong scale: transforms not applied before export
  • Missing textures: paths not embedded in GLB

Most issues can be avoided by validating the model locally before upload.

Best practices

  • Apply transforms early and consistently
  • Optimize geometry before touching materials
  • Keep polygon counts reasonable for the target product type
  • Prefer clean geometry and vertex normals over heavy normal maps
  • Always test the final GLB in a neutral viewer

Summary

A clean 3D model ensures reliable behavior across the entire Amaspace pipeline.

Focus on correct scale, clean geometry, proper shading, and reasonable polygon counts before moving on to materials and configuration logic.

Last updated on
Asset requirementsManaging Assets