Known limitations
The code checks are an aid, not an approval. A PASS against an IBC, IRC or ADA section is not a permit or a certification: the rule packs cover only part of each code, many verdicts rest on assumptions the Problems panel lists, and the building department (the authority having jurisdiction) and a licensed professional have the final say on a design.
- Curved walls must be split into straight segments.
- Exports: SVG, GeoJSON, OBJ, 3D prisms, the Three.js page and the door / window schedule. There is no DXF or IFC export. The editor exports PNG and prints to PDF through the browser.
- No importers. Plans come as bldg JSON: drawn in the editor, traced from a plan image by its AI assistant, or written by hand. IFC, DXF and Apple RoomPlan files cannot be read.
- Catalog plugins are JSON only. Your own models are JSON catalog files (validated, never executed); there are no code plugins.
- In OBJ / Three.js, sliding, pocket and folding doors are the void plus header without a leaf. The fold side of a folding door is not stored; it is drawn folding to side A.
- GeoJSON coordinates are planar plan units (local CRS by prior arrangement under RFC 7946 §4), not WGS84.
- GB/T 50353 and GB/T 17986.1 clauses are recalled, not verified against the standard; bay windows, canopies, external stairs and shared-area apportionment (公摊) are not modelled.
- US opening marks are ambiguous at 10 and 11 inches.
D3068encodes feet and inches as one digit each, so a 5'-10" window writesW51040(deferred; the type's width and height are the data, the mark only a name). - No
mixedoperation. A window with panels of different operations (a fixed light beside a casement) is one operation per type today; per-panel operations need a panels contract and are deferred, as are a bay window's form and a door's travel / leaf count / sliding axis.
bldg · Editor · Editor guide · Viewer · Format · Benchmarks · Limitations · Terms · Privacy · hello@usebldg.com