transform-usage-flags

Entities get wrong transform components during baking when TransformUsageFlags are not explicitly declared. You must specify flags like Dynamic or None in GetEntity calls to ensure correct LocalTransform and LocalToWorld composition.

To set TransformUsageFlags correctly, use Dynamic for moving entities and None for config or singleton entities. This ensures only required transform components are baked, preventing wasted components on data-only entities.

For prefab entity references, use matching TransformUsageFlags when calling GetEntity. This keeps archetypes consistent and ensures prefab entities receive the correct runtime transform components during baking.

You can use ManualOverride with ComponentTypeSet for batch component additions during ECS baking. This minimizes structural changes while transferring full responsibility for adding transforms to your baker logic.

You should not use TransformUsageFlags.None for entities that move or render at runtime. Applying None to moving entities omits required LocalTransform and LocalToWorld components, breaking their runtime behavior.

The best way to prevent spurious LocalToWorld components is declaring TransformUsageFlags.None during baking. This explicitly instructs the baker to omit transform components for entities that never move.