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
Sanity checkPERF.19 Link to PERF.19Comment on PERF.19 Scale: time is linear, memory is the ceiling. The 10x/100x/1000x table and where each format stops

The wave 3 scale track ran every engine on 10x and where possible 100x and 1000x files (Node 24, 12 GB heap cap; docs/0.9-sessions/perf-wave3/scale-1000x.md, tool tools/perf/scale-bench.mjs, generators tools/perf/gen/, 7.6 GB of files registered in testfiles/LARGE-FILES.md). Read time scales linearly almost everywhere (exponents: DWG read 0.93, IFC open 0.95, glTF 0.9, LandXML 1.1, LAS 0.7, GDS 0.87, PDF 1.0); the DWG writer is super-linear (1.3). What stops a file is memory and the data shape: one JS string per text file (hard stop 512 MB, practical 100 MB), one object per entity (cc-dwg 35 bytes of heap per file byte), whole-document JSON per undo step. Passes today: point clouds to 2 GB (100 M points in 59.5 s, 3.8 GB), cc-ifc index to 1.9 GB (15.9 s), GDS/OASIS to 622 MB (2.4 s), pdf.js 2,000 sheets (0.6 s), glTF 400 MB import (17 s). Stops: DXF 15 MB (crash, FX.142, now fixed), cc-dwg 76 MB needs 2.6 GB and 66 s to write, LandXML 358 MB needs 4.9 GB, ModelCraft first edit after a 400 MB import 36 s and 9 GB. This row: put the 1x and 10x lines of scale-bench into the PERF.6 budget (one line per format, fail on +15 % or any task over 5 s), plus the in-app budgets the 2D and 3D tracks set with their scripts (tools/perf/apps2d-*.mjs, apps3d-*.mjs on the registered files): CadCraft 100k entities open under 3 s, redraw p95 under 33 ms, pick under 5 ms, autosave under 500 ms; CivilCraft 500k points open under 5 s, zoom p95 under 100 ms; MarkupCraft 2,000 sheets switch p95 under 150 ms, heap under 400 MB; BimCraft heap per MB of IFC, ModelCraft heap per face, DetailCraft per member, draw calls, edit to next frame. Keep the table in the release notes results section; each format and app row below is the work. BUILT 2026-11-20 (scale-11, ws11a; docs/results/0.11/scale-11-table-ws11a.txt): IFC 201 MB open 0.7 s; 1.9 GB 6.3 s, peak 19.5 GB; DWG 100x (13 M entities) read 91.5 s, write 289 s, peak 43 GB. The run found DWG reads losing objects past 256 MiB; fixed.

– Our engines Built · in the lab 2 – 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