The hardest part of a multi-tool 3D workflow is usually the boundary between tools. A file arrives with geometry, but nobody knows whether it is coordinated design data, a procedural scenario, an AI-generated hypothesis, or a placeholder asset. I use MicroStation, Tripo3D, CityEngine, Shapezo, and Archshaper as separate pipeline stages and give every handoff a small data contract.
Step 1: define the contract
I start with the area of interest, coordinate reference, horizontal and vertical units, source date, target format, and intended use. I add a status field: source, generated, conceptual, designed, or verified. I also record what the next tool is allowed to do with the artifact.
This keeps a presentation model from drifting into an engineering workflow. It also gives reviewers a short answer when they ask whether an edge can be measured or only viewed.
Step 2: generate the first location branch with Shapezo
Shapezo uses a map-first interaction. I draw a boundary around a region, and its AI generates a model for the selected area. I use this branch when the location is known but the project scene is not built.
The handoff record stores the selected polygon or extent, generation date, visible coverage, and assumptions about inferred geometry. I keep the branch provisional. It is useful for questions about access, massing, and adjacency, but I do not pass its coordinates into controlled design without independent verification.
Step 3: test district rules in CityEngine
CityEngine is my scenario stage for repeatable urban patterns. I version the rule files or rule definitions with the boundary and source layers. A scenario should be reproducible as inputs plus rules, not only as a rendered image.
When density, height bands, frontage, or street hierarchy changes, I want the cause to be visible. I also keep a note about which parts are generalized. Procedural output is consistent enough for comparison, but consistency does not make it survey data.
Step 4: explore building form with Archshaper
Archshaper handles the building-scale concept. I record the site boundary, assumed grade, access condition, surrounding context, and the form constraints used for each option. The model remains conceptual until setbacks, codes, structure, and services are checked elsewhere.
I keep the architectural branch separate from the coordinated engineering file. They exchange intent and context, but they do not need to claim the same level of certainty.
Step 5: add communication assets with Tripo3D
If a scene needs a missing object, I may create it with Tripo3D. Before sharing it, I normalize units and origin, inspect normals and topology, reduce unnecessary geometry, and check materials. I retain the prompt or reference and mark whether the asset is presentation-only.
That source note matters when the object is reused. An AI-generated asset is still a dependency and should be traceable like an imported library component.
Step 6: establish coordinated geometry in MicroStation
MicroStation is where I carry decisions that need project structure. I check references, levels, units, attributes, model organization, and exchange requirements. A curve or footprint from an early generated scene is treated as a visual clue; I rebuild controlled geometry from explicit constraints and verified inputs.
The goal is not to erase the early studies. I keep links to them so reviewers can see how the design question developed without silently promoting provisional geometry into the accountable file. When a revision arrives, the links also show which assumptions changed and which ones stayed stable.
Checks before every handoff
- Confirm coordinate reference, units, and model origin.
- Preserve source dates, selected extents, and rule versions.
- Mark generated, generalized, conceptual, and verified geometry separately.
- Keep prompts, settings, exports, and transformations beside outputs.
- Test a small sample before moving a larger area. This pipeline works because the tools have different jobs. Shapezo gives me a map-selected first model. CityEngine tests repeatable district behavior. Archshaper tests building form. Tripo3D fills communication gaps. MicroStation carries coordinated project geometry. The reliable part is the handoff record that explains what each artifact means.
Top comments (0)