For the complete documentation index, see llms.txt. This page is also available as Markdown.

Quality Guidelines

Topics

Guidelines for highest quality

Recommendations for final review

How creative method determines collisions

Recommendations for common assets

Best practices with visual examples

Making assets easy to create & place

Tips, name compatibility with behaviours

Colour, shape & common issues

Optimisation for discovery

Prevent conflicts

Optimise Performance

Minimalist Design

Efficient assets provide Experience creators greater flexibility to add more assets and logic to their creations.

As a rule, every asset should be an optimised design. Strive for minimalism and simplicity in shape and add more detail in texture.

Maximum Size: 512 x 512 x 512 voxels

Maximum Faces: 5,000

Face count tends to affect GPU usage

Maximum Nodes: 175

Node count tends to affect CPU usage

Face Count tends to affect your GPU usage. A GPU is a graphics processor built into your computer's graphics card, used to accelerate graphics rendering. It functions side by side with your CPU, or central processing unit.

Node Count tends to affect your CPU usage. A CPU is the central processor built into your computer's motherboard, which performs basic operations on your device.

A compound entity rigged in the Animator with no motion keyframes added is calculated as having one node.

Best Practices for Optimal Performance

🟢Optimize with Texture✂️Trim All Volumes🟡Create Smooth Angled Lines

When You Need to Revise

If you exceed our guidelines, simplify the geometry of your design without losing your concept.

🧹Need to Simplify?

Quality Assurance Testing

Last updated

Was this helpful?