Release planning

CadCraft 0.11 impact map

Every fix and feature lined up for 0.11, and what each one touches: which apps, and which layers of the stack.

ProjectCadCraft
Sheet0.11 impact
Items799
Date2026-11-22
181Fix
383Feature
8Spike
35Platform
3Site ops
153Sanity check
36Decision
0Note
≈ 96days in the written 0.11 plans
  • Planned 45 on the plan for the release it is filed under
  • Built 449 built and working in /lab (the dev builds). Whether the public has it is its reach: "in the lab", "Live" (the last gate) or "switched off"; see docs/REACH-LIVE.md
  • Partly built 32 part of it is built in /lab; the rest waits (see "Waits on")
  • Promised 3 the live site already says it is coming
  • Moved 2 moved here from an earlier release or wishlist
  • Found 2 bug found after a release shipped; fixed in a point release or the next one
  • Candidate 49 recommended in a spike or session log; owner to choose
  • Community please test 143 built and in /use; a Discord post gives the steps and the expected result and asks people to try it on their own devices, files or know-how
  • Decision Time 74 a decision, check, file, key, flag or go only you can give; folds into the list once answered

Built means built and working in the lab. Live means the public can use it, and is the last gate: 3 Built · Live, 446 Built · in the lab.

Sheet 1 · impact areas

Where 0.11 lands

How many items touch each app and each layer, by kind. One item can touch several areas, so the rows add up to more than the item count. Pick a row to filter the schedule below.

Impact areaFixFeatureSpikePlatformSite opsSanity checkDecisionNoteAll
Apps
CadCraft 89 154 4 10 1 51 11 – 320
BimCraft 79 178 5 10 2 70 18 – 362
ModelCraft 60 81 2 10 1 41 4 – 199
MarkupCraft 46 59 2 9 1 18 1 – 136
TakeoffCraft 50 59 2 9 1 21 3 – 145
CivilCraft 69 131 3 11 1 35 3 – 253
DetailCraft 58 61 2 9 1 26 2 – 159
PartCraft 57 78 2 9 1 37 3 – 187
Studio 12 43 3 9 1 30 5 – 103
SuperCad Studio 9 109 2 7 – 23 5 – 155
Layers
Site and services 15 25 – 10 2 2 8 – 62
Desktop host 7 22 2 10 – 7 2 – 50
App shell 25 32 – 7 – 4 2 – 70
App code 69 193 4 6 1 9 16 – 298
Our engines 8 71 3 1 – 4 10 – 97
Vendor engines – 2 – – – – 1 – 3
Drawing surface 1 – – – – 1 – – 2
Help and words 2 9 1 – – 2 – – 14
Tests and tooling 4 9 1 3 – 4 2 – 23

Sheet 2 · schedule

Every fix and feature

Grouped by track. App chips carry each app’s layer colour; Studio is in ink. "Waits on" names what has to happen first; the small lines under it say who asked and where the item is written up.

Add an item Fork map (Rust and C++ forks) The roadmap

Issues sync every 10 minutes; last sync Nov 22, 2026 10:40 am.

ItemWhatAppsLayersStatusDaysWaits onIssues
Performance roadmap — wave 3 49
FixPERF.20 Link to PERF.20Comment on PERF.20 Scale: every text format reader holds the whole file as one JS string (DXF, LandXML, OBJ, DAE, ASCII STL, USDA, the native JSON documents)

Measured: a 1 GB DXF and a 692 MB LandXML die in TextDecoder.decode ("Cannot create a string longer than 0x1fffffe8"); a 358 MB LandXML needs 4.9 GB and 27 s; a 10 MB DXF needs 364 MB (38 bytes of heap per file byte, parsed twice through dxf-model.js:65). Sites: dxf-decode.js:35-49 and dxf.js:68-74, civilcraft.js:2485 and xml.js:27, modelcraft io/obj.js:84, and JSON.parse(await file.text()) for every .modelcraft/.detailcraft/.civilcraft document (modelcraft.js:3210). The caps that exist (CivilCraft 200 MB, ModelCraft 200 MB, OBJ 64 MB) are honest and stay until the readers stream. Change: byte-level tokenizers over Uint8Array fed from Blob.slice with lazily decoded values and Float64Array/Uint32Array output, the way lib/ifc scanStep already works. DXF first (the reader is 1,563 lines, L), then LandXML (M), OBJ and ASCII STL (S each). Target: 100 MB DXF under 1 GB of memory, 1 GB files open with a progress bar instead of an error. PARTLY BUILT in /lab 2026-11-14 and 2026-11-20: one shared parts reader (lib/textin); DXF, LandXML + XML parser, OBJ, ASCII STL, Collada, USD text and project JSON read from parts, byte-identical to the old readers; ws11a: a 954 MB DXF opens in 42 s, a 691 MB LandXML in 16 s (both failed at the 512 MB string limit); the tree of objects is the ceiling (LandXML 13x its size, DXF 16 to 20x). 0.11 (scale-11): CSV points (lib/layout, civilcraft patch), G-code (lib/carve) and GeoJSON (patch) read from parts: 18 M points 27.6 s, 36 M G-code lines 28.8 s, a 1 GB GeoJSON 16.7 s (all refused over 512 MB before); the Set that stopped both point readers at 16,777,216 points is gone; same speed under 512 MB; GeoJSON parts are 2.3x slower than one string, so parts only over about 400 MB. A 197 MB DetailCraft model rea LANDED 2026-11-20 (inbox-11b) scale-11 patch applied to civilcraft/a Discord member (points.js, geojson.js, landxml.js; chunks.js synced); DetailCraft openFile cap 50 to 400 MB. test-readers 488/0, test-writers 22/0, test-civilcraft 417/0. (inbox-11b) BUILT 2026-11-21 (perf-finish-11), lane scale-shell, in /lab (a Discord member) only: lib/textin joins parts under 400 M characters and hands them to JSON.parse, so callers pass parts at any size; the PartCraft and DetailCraft caps are 400 MB. workstation11a, same value: 268 MB GeoJSON from parts 4.5-5.2 s -> 1.9-2.0 s, peak 3.6 -> 2.2 GB; 197 MB DetailCraft project 1.5-1.7 s -> 0.95 s; a 1 GB GeoJSON unchanged by design (past the join limit). textin 70 / 0, test-readers 488 / 0; textin / textout / history copies in step in every app (--check clean). Not met: a 100 MB DXF under 1 GB (the object tree is 16-20x the file, not the reader).

CadCraftModelCraftCivilCraft App codeOur engines Built · in the lab 12 – docs/0.9-sessions/perf-wave3/
FixPERF.22 Link to PERF.22Comment on PERF.22 Scale: cc-dwg keeps 35 bytes of heap per file byte, clones the drawing out of the worker, and the writer is super-linear (extends PERF.5, PERF.9, PERF.10)

Measured at 10x (a 76 MB R2004 drawing, 1.4 M entities): readDwg 19.9 s and 2.6 GB after read (one object per entity and per vertex, objects-read.js:608-613 and :1105), the worker reply structuredClone adds 1.06 GB and 14.6 s (read-async.js:67), writeDwg 66 s (33 s from a fresh model), exponent 1.3. A 760 MB drawing would need about 27 GB: it does not fit anywhere. Browser ceiling today about 55 to 110 MB. Change: a struct-of-arrays entity store with lazy per-entity decode from the object map (the map and section locators are small; readDwg(bytes) at read.js:30 becomes openDwg(blob) with byte-range decoding), the worker reply as transferable typed buffers (or decode on the page from the transferred bytes), and a writer that streams sections to a FileSystemWritableFileStream. Reader L, writer M. The four apps carry byte copies of lib/dwg. Partly built (dwg-perf-10 2026-11-14): Writer half and worker hand-off built (see PERF.5, PERF.9): the worker copy is no longer cloned. Reader heap measured at 16.1 B per file byte (heapUsed after a GC, Plans.dwg and the 130k and 1.3 M generated drawings alike; the row's 35 was not reproduced), 15.6 now: one string per owner saves 0.5, the rest is 1.14 M objects and 2.5 M boxed numbers the model shape needs. Log docs/0.10-sessions/dwg-perf-10.md. PARTLY BUILT 2026-11-20, scale-11: measured on a prototype outside the apps (tools/scale-11/proto-table.mjs, lib/dwg/model-pack.js as the table): the reader holds 15.2 to 15.6 B of heap per file byte (not 35); keeping the entity lists as typed arrays: Plans.dwg 128 MB to 49 MB (2.6x), 1.3 M entities 1,150 MB to 346 MB (3.3x), all lists back as objects in 0.43 s per 1.3 M; the proposal (shape, each app's adapter, risk) is in the log under For the owner. A bug that read objects past 256 MiB as empty was fixed in the reader. No model changed.

CadCraftBimCraftModelCraftCivilCraft Our engines Built · in the lab 12 The owner's yes on the typed-array entity table (docs/0.11-sessions/scale-11.md, For the owner) docs/0.9-sessions/perf-wave3/
FixPERF.25 Link to PERF.25Comment on PERF.25 Scale: point clouds pass 2 GB, but the octree merge is single-threaded, LAZ copies the whole file into WASM and E57 is one 512 MB buffer (extends PERF.10)

Large point clouds: tiled by a worker pool, LAZ read chunk by chunk, E57 page by page, every point kept. 0.10 (pointcloud-10): tile pass on up to 4 workers, byte-identical to the serial build; LAZ chunk reader (heap 3 MB, not the file); E57 page reader. pointcloud-11 2026-11-20: a LAZ of 2.10 GiB and 241,100,000 points (made once, registered in testfiles/LARGE-FILES.md, made-up terrain) builds in 268.5 s with one decode thread and no tile workers, 207.3 s with 8 tile workers, 94.9 s with 4 LAZ decode threads (each its own laz-perf, results in file order: byte-identical cloud, tested), the merge of the upper nodes in the worker pool and the build folder cleaned 32 files at a time (2.54 M points a second, peak RSS 6.1 GB, workstation11a). The old whole-file reader cannot read that file ("not enough memory"). An E57 of 600 MB (22.1 M points) builds in 18.8 s, every point kept, 0.95 GB. Not done: a browser tab with a 2 GB file; the files are made-up data and the E57 writer was never opened in another program. Results: docs/results/0.11/pointcloud-11-perf25.md.

CadCraftBimCraftCivilCraft Our engines Built · in the lab 4 – docs/0.9-sessions/perf-wave3/
PlatformPERF.26 Link to PERF.26Comment on PERF.26 Scale: text writers return one string, so exports stop at 512 MB and hold twice the output

DXF (dxf.js:1324, dxf2000.js:437), LandXML (landxml.js:227), OBJ, DAE, USDA (usda-write.js:33), GeoJSON and gcode writers each build one string and return it; a 1,000,000-entity DXF export is near the V8 string limit and the string plus its Blob is twice the output in memory. Change: writers that yield chunks into a WritableStream (createWritable on a file handle when the host offers one, else a Blob built from parts), with the same report object. Pairs with the streaming readers row. Partly built (dwg-perf-10 2026-11-14): lib/textout/chunks.js (TextChunks: parts, Blob, pipe, string only while it fits): equal to lines.join at every size around a part, and 686 MB of text written without a string (peak RSS 1.7 GB). A ready patch for the DXF writer is docs/0.10-sessions/dwg-perf-10-dxf-chunks.patch. Log docs/0.10-sessions/dwg-perf-10.md. PARTLY BUILT 2026-11-20, scale-11: TextChunks gained push(); the LandXML and GeoJSON writers (patch for civilcraft/a Discord member) and the G-code writer (lib/carve, done) write past 512 MB: LandXML 9 M points 706 MB in 11.6 s, peak 3.2 GB (the string version fails: Invalid string length); 6 M points peak 5.7 GB to 2.2 GB; GeoJSON 4.8 M features 661 MB (fails as one string); G-code 40 M moves 767 MB (fails as one string). Same text as before on 62 checks. The DXF patch of 0.10 still applies: posted to cad-11. docs/results/0.11/scale-11-text-ws11a.txt. LANDED 2026-11-20 (inbox-11b) LandXML and GeoJSON chunked writers in civilcraft BUILT 2026-11-21 (perf-finish-11), lane scale-shell, cad, civil, model, in /lab (a Discord member) only: lib/textout TextChunks.output() (a string to 300 M characters, a Blob past that). CadCraft DXF 2000 save at 1 M objects works (was "Invalid string length": 538 M characters in parts, 12.5 s); CivilCraft LandXML and GeoJSON export in chunks (Blob past 300 MB), GeoJSON import from parts; ModelCraft OBJ, Collada, USDA write in parts, byte-identical 33 / 0; carve G-code check 29.8 -> 0.45 s (261 / 0). Copies synced (--check clean).

CadCraftModelCraftCivilCraft App codeOur engines Built · in the lab 4 – docs/0.9-sessions/perf-wave3/
FixPERF.76 Link to PERF.76Comment on PERF.76 Code: O(n squared) searches in kernel code (ModelCraft mesh ops, the shared m3d model, CivilCraft LandXML) and render functions that rebuild whole panels

Built (code-shared-11 2026-11-20, with model-part-11 for the kernels). CivilCraft LandXML writer: structures x pipes, pipes x structures and profile points x curves became one index each: 6,000 structures 1,359 ms to 96 ms, 20,000 PVIs 93 to 29 ms, file hash identical (tools/civilcraft-test/bench-quadratic-011.mjs). TakeoffCraft clipboard copy of 20,000 items 1,996 ms to 34 ms, 20,000 marks 1,525 to 86 ms, Live reorder op 765 to 7 ms (tools/takeoffcraft-test/bench-quadratic-011.mjs). Render-function rebuilds are a separate row's work. Was: Not started (code-shared-10 2026-11-16): kernel Sets (modelcraft mesh/ops, m3d model, landxml) and render-function rebuilds wait for a next session. Was: Nested-loop searches with includes/some inside N by N loops: modelcraft mesh/ops.js:421 subdivide (also :471, :820, :915), m3d model.js:693, :778, :1637, :1957 (in both ModelCraft and CadCraft's copy), civilcraft landxml.js:298-322. These are the places a 10x model turns into a 100x wait; the 3D track's numbers (ModelCraft push/pull and undo at 500k faces) land here. Change: Sets and Maps keyed by vertex or id, measured before and after with tools/perf/scale-bench.mjs and the apps3d scripts. Render functions that rebuild and re-query the DOM on every call (196 querySelectorAll and 315 addEventListener inside render functions; takeoffcraft.js sheet list on every sheet switch, shell app-workspace.js, supercadcraft.js, cadcraft renderLayers and renderSelTotals): keyed children and incremental updates, measured on the 2D track's 2,000-sheet set. MODELCRAFT AND THE M3D MODEL BUILT in /lab 2026-11-20 (model-part-11), same machine, results identical by hash: slideRails on a 1,001-vertex loop of a 4 M half-edge mesh 27.1 s to 0.09 s (the open half-edges by head built once), healCollinear on a 6,000-vertex polyline 2.53 s to 0.05 s (vertex map kept in step, edge-face map only after a merge), edgeChain on 6,000 edges 37 ms to 18 ms, insetFaces on 22,500 faces 4.4 s to 2.3 s…

CadCraftModelCraftTakeoffCraftCivilCraft App codeOur engines Built · in the lab 4 CivilCraft landxml.js (civil-11's); the render functions that rebuild whole panels (the 2D apps') docs/0.9-sessions/perf-wave3/
Suggest an item

Anyone can send one; no account and no name needed. The team reads each idea, and the ones we take on appear on this page. Please leave out web addresses.

Top