Voxel Scene Generation: From 3D Models to Interactive Web Pages

    This article explains how to evaluate 3D generation tasks for voxel scenes, turn a short request into acceptance criteria, design effective prompts, review generated results across five dimensions, and define delivery requirements for interactive web pages.

    Voxel Scene Generation: From 3D Models to Interactive Web Pages

    1. Why 3D Generation Tasks Need Separate Evaluation

    3D content production has long depended on professional experience in modeling, materials, and scene assembly. As generative models can now directly output editable 3D projects, rendered images, and interactive pages, teams need a repeatable evaluation method to decide whether generated results can enter an actual delivery workflow.

    Unlike text or code generation, the quality of a 3D result is difficult to measure with a single metric. A scene may have a correct overall layout but miss the local element that most clearly identifies the theme. In another case, the model geometry may be complete, but the interaction features may exceed the requirements. Evaluation therefore needs to be divided into several dimensions that can be checked item by item.

    2. Turning a One-Sentence Request into Acceptance Criteria

    Many prompts describe only the theme, such as “make a miniature landscape of a certain theme.” This kind of description leaves a large amount of room for interpretation, and the result often depends on the model’s default understanding. A more reliable approach is to split the request into four types of information.

    1. Theme and style: State the source of the scene setting and the visual language to use, such as voxel block style, low-poly style, or realistic style.
    2. Required element checklist: List all structures and identifiers that must appear, such as the number of building floors, indoor and outdoor functional zones, people or props at the entrance, and sign text on walls. Each item should be findable in the result.
    3. Deliverable format: Specify the required file types, such as an editable project file, rendered images at a specified resolution, or a single-file page that can be opened directly in a browser.
    4. Interaction and additional features: If interaction is needed, specify the operation method, such as drag-to-rotate, click-to-focus, or annotation display. Features that were not requested should not be added by default, otherwise acceptance becomes more difficult.

    Once these four types of information are clearly written, acceptance has a basis. Content that is not included in the checklist is treated as optional, not mandatory.

    3. Prompt Design Key Points

    The goal of the prompt is to reduce the model’s room for free interpretation while preserving its creativity in composition and details. In practice, the following structure can be used:

    • The first paragraph describes the overall scene and its purpose.
    • The second paragraph describes the structure in spatial order, from outside to inside and from bottom to top.
    • The third paragraph lists the identifying elements that must appear and emphasizes them with wording such as “must include.”
    • The fourth paragraph provides the deliverable list.
    • Finally, state the interaction requirements and avoid open-ended descriptions.

    An example structure is shown below:

    1. Scene: A two-story voxel miniature building for showing indoor and outdoor layout.
    2. Structure: The first floor is a coffee shop, the second floor is a detective agency, and there is an external staircase leading to the second floor.
    3. Must include: A shop sign on the wall (text clearly readable), two character models at the entrance.
    4. Deliverables: 1 editable project file, 2 rendered images from different angles (PNG, 16:9).
    5. Interaction: A single HTML file that supports drag-to-rotate, auto-rotate, and click-to-focus on parts.

    The advantage of this approach is that each item can be converted into an acceptance item. If an item is not satisfied, the problem can be located directly.

    4. Evaluation Dimensions for Generated Results

    It is recommended to check generated results item by item across the following five dimensions.

    1. Structural completeness: Check whether floors, rooms, passages, and main furniture are complete. Check whether stairs connect to the correct floors and whether the spatial relationships between rooms are reasonable.
    2. Key identifiers: Check whether required signs, people, and props exist. This item is most easily overlooked because a structurally complete scene may still lack the most recognizable elements. Check each item against the checklist rather than judging only by overall impression.
    3. Proportions and scale: Check whether the ratio of people to buildings, door and window sizes, and step heights match common sense. Voxel style is especially sensitive to proportions, and a scale error in a single block can be amplified.
    4. Details and presentation: Check whether the color palette, material distinction, lighting, and filters are coordinated. Details such as character hairstyles and clothing can easily deviate from expectations. If such details have high requirements, provide reference images or specify key color and shape features in the prompt.
    5. Editability: Check whether objects in the project file are grouped, whether names are clear, and whether materials are independent. A file that can only be viewed but not edited is difficult to support later iteration.

    Evaluation results can be recorded in a table, with a clear conclusion for each item:

    Dimension Check item Result Notes
    Structural completeness Floor and stair connection Pass Stairs connect the first and second floors
    Key identifiers Wall sign Fail No sign in the model
    Detail presentation Character hairstyle Fail Large difference from the reference description

    Recording results item by item helps the team clearly see which category the problems are concentrated in, instead of reaching a conclusion such as “overall it is okay,” which is difficult to act on.

    5. Delivery Requirements for Interactive Web Pages

    When the deliverables include an interactive page, functions can be divided into a basic layer and an enhanced layer.

    The basic layer includes capabilities that most 3D display pages should have:

    • Model drag-to-rotate and zoom;
    • Auto-rotate, with support for pausing at any time;
    • One-click reset of the view;
    • An operation guide shown on first open, so users know how to interact.

    The enhanced layer can be selected according to business needs.