Why Foxel Uses a Full Scene Workflow

This tutorial explains why Foxel scenes feel broader than a simpler voxel-only workflow.

A Foxel scene is not only a place for voxel content. It can also contain groups, lights, cameras, and references.

That is why the scene hierarchy matters and why Foxel is built around a fuller scene workflow.

Why This Matters

If you expect the scene to be only a place where voxel objects live, some of Foxel’s structure can feel heavier than necessary.

It makes more sense once you see that the scene is designed to hold different kinds of objects with different roles.

The scene is not just a voxel container. It is the workspace where different scene elements are organized and used together.

A Foxel Scene Is More Than Voxel Content

A Foxel scene can contain voxel objects, but that is not all it can contain.

It can also contain other object types that support broader scene work.

This makes the scene useful for more than direct voxel editing.

A scene can also describe structure, lighting, views, reusable content, and helper organization.

Different Object Types Have Different Roles

Different scene object types exist for different tasks.

Examples include:

• Voxel objects for editable or generated voxel content.
• Groups for organization.
• Lights for illumination.
• Cameras for views and rendering.
• References for reusing other content in the scene.

This makes the scene workflow broader than simply arranging voxel content.

Voxel Objects

Voxel objects are the main content you edit or generate as voxel data.

They are the core modeling elements in a scene.

Groups

Groups help organize related objects.

Use them when several objects belong together or should be managed as part of the same structure.

Lights

Lights affect how the scene is illuminated.

They are part of the scene because lighting is often needed to judge materials, presentation, and final output.

Cameras

Cameras define views for rendering or presentation.

They are useful when you want repeatable viewpoints instead of only using the current editor view.

References

References let you reuse other assets inside the scene.

They make it possible to bring in generated content from source assets without rebuilding that content manually.

Why This Workflow Is Useful

A fuller scene workflow helps with:

• Better organization
• Clearer hierarchy structure
• Scene lighting
• Camera-based views and output
• Reuse through references
• Broader project workflows

This structure becomes more useful as scenes grow beyond a single editable voxel object.

Why The Hierarchy Becomes More Important

Once the scene contains more than one kind of object, the Hierarchy is no longer just a list of voxel items.

It becomes the structure that helps you understand and manage the whole scene.

Use the Hierarchy to see:

• Which objects exist in the scene.
• Which object is currently active.
• How objects are organized.
• Which objects are grouped.
• Which cameras, lights, and references are part of the scene.

The broader the scene becomes, the more important the Hierarchy becomes.

How To Think About It

A simple voxel-only workflow focuses mostly on editing voxel content.

Foxel’s scene workflow is broader:

Voxel Content + Organization + Lighting + Cameras + References

That is why the scene can feel more structured.

The added structure is there to support scene-based work, not only isolated voxel editing.

What To Remember

• A Foxel scene can contain multiple object types.
• Those object types have different roles.
• Voxel objects are only one part of the scene.
• Groups help organize content.
• Lights affect illumination.
• Cameras define reusable views and render output.
• References reuse other assets inside the scene.
• The Hierarchy matters because the scene is broader than voxel content alone.
• This is why Foxel uses a fuller scene workflow.