Commands  ›  Clash Manager / Solver  ›  Clash Solver Find Ceiling Void At Point

Clash Solver Find Ceiling Void At Point

Clash Manager / Solver writes to model Public API · not yet exposed

Coming soon

Before you run this

Active document; at least one non-template View3D; either (x,y,z) resolvers or a single-element selection.

After it runs

No model mutation — this is a read-only inspection recorded in CommandTracker.

When to use this

Don't use this when

Actual movement — Offset*Up commands do that.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) Resolve point: (x, y, z) if provided; otherwise take top-centre of selected element's BB.
2) WireError if neither source yields a valid point.
3) Delegate to SpaceAnalysisFindCeilingVoidAbovePoint.GetAll(doc, x, y, z, max_distance_ft) — single source of truth.
4) Record ceiling_z, obstruction_z, void_height_mm, is_beam into tracker outputs.
5) Human path shows TaskDialog summary; Bot path emits only the JSON.
6) WireError on no-3d-view / no-hits; WireFault on exception.

What you'll see in the chat

on start
Probing ceiling void at point…
thinking
Resolving point from resolvers or active selection…
Raycasting +Z via SpaceAnalysisFindCeilingVoidAbovePoint…
on success
Void {void_height_mm} mm between ceiling {ceiling_z} ft and obstruction {obstruction_z} ft.
on failure
Void probe failed: {error}

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

  • POST /api/v1/commands/clash_solver_find_ceiling_void_at_point
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

clashsolverfindceilingvoidatpoint · find ceiling void · clash solver offset up probe

PillarClash Manager / Solver