
CityEngine vs. Shapezo: A Reproducible Workflow for Procedural and AI City Models
When I compare CityEngine and Shapezo in a technical workflow, I separate generation from evidence....
Tag archive

When I compare CityEngine and Shapezo in a technical workflow, I separate generation from evidence....

The hardest part of a multi-tool 3D workflow is usually the boundary between tools. A file arrives...

When I add an AI step to a building workflow, I treat it like an untrusted dependency. It can produce...

When I think about a next-generation multimodal agent such as GPT-6 Astra, I do not picture a magic...

I get fewer surprises when I treat site modeling as a sequence of artifacts instead of one giant...

When I design a construction technology workflow, I begin with a bottleneck and a measurable...

When I evaluate an empty office building for housing, I treat the first model like an untrusted...

I wanted a workflow that could answer two different questions without mixing their outputs. The...

When I put a location-based model into a technical pipeline, I care about provenance as much as...

Shapezo and Meshy can occupy different layers of an AEC or visualization pipeline. Shapezo organizes...

The mixed-tool problem I run into most often is not a missing command. It is a missing contract. A...

I think of a 3D city model as an intermediate data product between a map and a design model. It is...