Users can now customize the position of foundation elements - simplifying and speeding up modeling workflows while unlocking higher level of detail.

Users can apply foundation assemblies to the entire foundation system, or individual edges, and can override individual parameters as needed. This encourages reuse and centralization - reducing manual overrides and overall model maintenance.

New toggles in the Levels Inspector ("Enable Foundations" / "Enable Floors") let drafters suppress auto-generated systems so freeform entities can take over. Similar toggles can be used to disable foundations on a per room basis.

Users can now create custom origin-relative vertical datums that can be utilized by levels, foundations, facades, and modeling components. These datums can be shared by multiple entities and update centrally, reducing model maintenance.

Studio users can now explicitly control the position of levels by assigning a level a specific origin-relative datum. This provides greater control and flexibility, especially useful for complex architecture typologies like Townhomes.

Users can also now control level-stacking behavior by specifying specific stacking relationships between levels.

Users can save groups of geometry as a reusable Modeling Component Catalog and place multiple instances of that component on the canvas. Modeling Components allow users to extensively reuse model geometry across their portfolio.

Each Modeling Component Instance supports some individual controls (naming, move, datum assignment, offset).

To edit an existing Modeling Component Instance, users can right-click an instance in 2D and select "Edit Component". When editing a Modeling Component, users enter Isolated Editing Mode - a special editing experience that hides surrounding file context so drafters can edit a component's geometry in isolation.

This mode duplicates the project file's levels into the component definition, locking internal level relationships regardless of placement. This mode is best for multi-level components like townhome units where L1, L2, L3 relationships must stay consistent across project files. This is the default level-positioning method for components.

This alternate positioning method lets the modeling component instance borrow a level in the project. It is currently limited to component definitions with objects on a single level, and is best for repeating layouts like a bathroom suite or bedroom. It allows users to author a flexible modeling component that will stretch to fit its assigned project level.

Non-component geometry like roofs can reference the levels that exist inside specific component instances, so when an instance moves vertically the referencing geometry follows. This provides greater flexibility and allows users to avoid constantly updating the position of certain model geometry.

This is currently supported for a limited set of entity types like Roofs.

Users can associate an option with a modeling component such that a new instance-option appears for each Modeling Component Instance. In the example of Townhomes, this allows users to easily create one option per unit instance within a building.

To associate an option with a Component, users must add the Option to the Modeling Component. To do this, navigate to the component inspector, click “Add Entities”, then select the option in the option list in the explorer.

Instance Options will appear downstream in Config and Showroom, allowing buyers to make option selections for their particular unit.

A single Studio file usually contains more than one dwelling — a townhome building string, a duplex, a multiplex. Reporting Units let you declare which geometry belongs to which dwelling, so one model produces per-unit plans, configs, and Showroom experiences instead of one undifferentiated building.

Create one: add a custom label, name it (e.g. "Unit A"), check is reporting unit. Assign it to roofs, foundations, props, and modeling components — including Modeling Component Instances, so identical components can be told apart.

Downstream: the designation carries into CDs. On publish, Config and Showroom detect each unique reporting unit label and map it to a unit designation.

Limits: reporting unit content can't nest inside other reporting unit content, and a single piece of geometry can't carry conflicting labels.

Reporting Unit Designations can be visually previewed in Studio. This enables Studio users to double-check their work before publishing or testing out files in Showroom.

To preview, users should navigate to the 3D View Inspector. Then under 3D View, select one reporting unit to isolate. All other geometry grays out in the preview, letting drafters QA unit filtering before publishing downstream deliverables.

In order to accommodate Townhome and multi-unit style Buildings, we’ve introduced a new location hierarchy level within Config. This allows users to operate on the Townhome Building itself, in addition to the individual units.

A new "Buildings" location level can be enabled in Account Settings and added as a sub-location to a Community. Studio, Config, and Showroom all read this hierarchy.

This is a required setup for all other multi-unit workflows.

Studio Documents will have a specific number of units upon publishing. This number of units is then read by Config, where users should map specific units to specific lots.

Availability, price, and sold/held status track at the unit level using the same inventory workflow as single-family lots.

Some choices belong to the whole building and some belong to a single unit. The option template lets you decide which is which. Set an option as building-wide, like exterior siding, roof material, or window package, and it applies to every unit in the building at once. Set it per-unit, like kitchen finishes, flooring, or appliance packages, and it only affects the unit it's chosen on.

In any multi-unit Showroom file, users can toggle between Full Building Mode (full context) and Focus/Highlight Unit Mode (orbit and interactions center on the selected unit). Works across 3D Exterior, 3D Dollhouse, and Floor Plan, so a single Showroom file supports both whole-community presentation and per-unit shopping. This functionality works in both Showroom and Showroom Intro.

Composite Levels combine multiple levels into a single plan view. Create a composite level in Views, add the discrete levels you want, then point a Plan Viewport at it.