Block Configure

The Block Configure command takes a project block — i.e. a row of houses — and produces a single Revit document with every house in the block correctly positioned and configured. Use it for project-level review and rendering, where you want to see the whole street rather than one house at a time.

This is the block-level counterpart of the Run Configuration flow, which runs a single house configuration.

Opening the Window

Click Block\nConfigure in the Configure panel of the Alpha ribbon. The window title is Block Configure and it opens as a modeless dialog.

The header shows the environment URL the add-in is currently pointing at — confirm this matches the environment the project lives on before running. Switch environments via Settings if needed.

Running a Block

1. Project — pick the project from the dropdown. Click Refresh if the list is stale.
2. Block — once a project is selected, the block dropdown loads. Each entry shows the block ID, its description, and the house count.
3. Resource Folder — where downloaded model files (RVT/GLB inputs) are cached.
4. Output Folder — where the configured block document is written.
5. Output formats — tick GLB, PDF, RVT, IFC as needed. RVT is on by default.
6. Click Configure Block. Progress and status update in the bar at the bottom of the window.

When the run finishes, the status line reports the number of houses configured and output files written, and an Open Export button appears so you can jump to the produced files. Outputs land under block-<blockId> inside the configured output folder.

What It Does

For the selected block, the add-in:

1. Fetches the block's house list and per-house configurations from Alpha
2. Resolves each house's static-model tree and option choices into placed Revit elements
3. Positions each configured house at its correct coordinate within the block
4. Writes the combined Revit document to the output folder in the formats you ticked

A failure on any single house surfaces in the status message; partial outputs already on disk stay there.

Local vs Queued

Like single-house configurations, blocks can also be run hands-off by the worker daemon:

• Local: this window — useful when you are iterating on a project and want to see the result yourself.
• Queued: queue the block on the platform and the worker daemon picks it up, opens Revit on the worker machine, and runs the configuration without anyone clicking buttons. See Run Configuration → Queueing for the worker — the same flow applies to BLOCK jobs.

Related