Release planning

CadCraft 0.9 impact map

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

ProjectCadCraft
Sheet0.9 impact
Items273
Date2026-11-09
115Fix
147Feature
4Spike
0Platform
0Site ops
0Sanity check
7Decision
≈ 0days in the written 0.9 plans
  • Planned 0 on the plan for the release it is filed under
  • Built 271 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 1 part of it is built in /lab; the rest waits (see "Waits on")
  • Promised 0 the live site already says it is coming
  • Moved 0 moved here from an earlier release or wishlist
  • Found 0 bug found after a release shipped; fixed in a point release or the next one
  • Candidate 0 recommended in a spike or session log; owner to choose
  • Community please test 0 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 0 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: 270 Built · Live, 1 Built · in the lab.

Sheet 1 · impact areas

Where 0.9 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 checkDecisionAll
Apps
CadCraft 38 36 – – – – 2 76
BimCraft 27 53 2 – – – – 82
ModelCraft 19 45 2 – – – 2 68
MarkupCraft 16 11 – – – – – 27
TakeoffCraft 18 7 – – – – – 25
CivilCraft 14 32 – – – – – 46
DetailCraft 13 13 – – – – – 26
PartCraft 18 27 1 – – – – 46
Studio 2 5 1 – – – – 8
SuperCad Studio 22 17 – – – – – 39
Layers
Site and services 7 11 – – – – 5 23
Desktop host 1 1 1 – – – – 3
App shell 2 1 – – – – – 3
App code 10 28 3 – – – 3 44
Our engines – 12 1 – – – 1 14
Vendor engines – – – – – – – 0
Drawing surface – – – – – – – 0
Help and words 1 2 – – – – 1 4
Tests and tooling – – – – – – – 0

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 9, 2026 7:00 pm.

ItemWhatAppsLayersStatusDaysWaits onIssues
Drafting and app features 4
FeatureWB.6 Link to WB.6Comment on WB.6 CivilCraft New Feature: Corridor, Templates, Terrain Templates and a Template Creation tool

-Template Creation Tool: A Template creation tool would be nice to see. The template creation tool should be designed to allow users the freedom to create any object. Points should be controlled through parametric constraints or targeting. -Terrain Template: Other software packages use the idea of applying a template to a terrain and it is a game changer for designers. Placing a template on a terrain allows 3d volumetric components to be "draped" on a terrain. i.e., 6" of Topsoil can be placed below a terrain or 5" of pavement with 12" of Base can be place on a terrain of a parking lot. This allows designers to create a site grading design and apply material without using a corridor modeler. Ideas: The 0,0 point of the template controls the point materials are built vertically. Any component or shape is applied to the terrain from the 0,0 point. Widths and slopes don't matter for these types of templates. Terrain templates can be clipped by a 2d shape in plan view. This will allow multiple terrain templates can be used on a terrain if different materials are required. -Corridors: Multiple Corridors: Please allow for multiple corridors to be applied to an alignment. Long alignments require the design to be broken into pieces at times. Multiple Templates : Allow multiple templates to be applied at once. i.e. Template for pavement and end condition Lt & Rt. The end condition templates can be controlled separately. Creating small reusable templates. **Built:** Built in /lab 2026-11-02 as SU.1110 (civil-templates-09): the template creation tool (parametric points, targets), terrain templates draped from the 0,0 point and clipped by a parcel, pad or closed feature line, several corridors on one alignment, several templates by station, left and right end conditions. Surface › More › Corridor templates… and Terrain templates…; an alignment's Properties › Corridor.

CivilCraft Built · Live – – From: a visitor (Site)
FeatureWB.10 Link to WB.10Comment on WB.10 Civilcraft: Add basic drafting tools. Snapping on elements. Move , Copy Rotate etc....

Drawing tools needed in Civilcraft. Snaps are need when drawing parcels, alignments and pads. All menu dialogs with coordinates show should have a button to allow users to snap to a point in the drawing. Entering N,E,Z manually is very , very time consuming and not used by any major civil design programs anymore. Points and bearings should have a pick button on all menus. Tangents should have two pick button to define the bearing with two points. **Built:** Built in /lab 2026-11-06 (civil-snap-09). Snaps: the Alignment, Pad, Parcel, Mass, Feature line, Measure, Boundary and Catchment tools and a dragged PI or corner snap to survey points and to PIs, pad / parcel / mass corners, feature-line vertices and structures within 10 px (a marker with a label and the E, N; Alt = free). A crosshair Pick button sits beside a PI's northing, every corner's northing and the move / rotate blocks. Tangent from two points under the PI table. Move, copy and rotate (typed distance or two picked points; about the middle or a picked point) for an alignment, pad, parcel and feature line. Not yet: snap to a segment middle or crossing, Pick in the landscape / power-line / water panels, move of storm networks.

CivilCraft Built · Live – – From: a visitor (Site)
FeatureWB.15 Link to WB.15Comment on WB.15 Alignment and Parcels coordinates

1. Allow users to enter Northings and Eastings for parcel and alignment vertices. 2. Allow users to snap to objects when creating or editing alignments and parcels. A pick button in the properties dialog for the N,E would be great. Users can snap to an existing element and the NE for the vertex will be updated. **Built:** Built in /lab 2026-11-06 (civil-snap-09). Alignment PIs already took a typed E / N; now pad, parcel and feature-line corners list typed E and N too, and every one has a Pick button: press it, click a place in the plan (snapped to survey points, PIs, corners and vertices; Alt = free), and the vertex takes that easting and northing, one undo step. Drawing and dragging alignments and parcels snaps the same way.

CivilCraft Built · Live – – From: a visitor (Site)
Requests for 0.9 8
FeatureD9.9 Link to D9.9Comment on D9.9 Zoom in and out of the drawing to see details (request in German)

Asked on /suggest (#1236, Nov 6 2026, in German, “Zeichnung vergrößern, verkleinern”): “Details should be zoomable; often the drawing in the edit window is too small and it is hard to see details.” The submitter did not say which app. Checked 2026-11-07: CadCraft has a ZOOM command and view zoom already; the report reads as someone not finding it, or a drawing that opens small (page or sheet view, a small window, a large paper size), or a touch screen where pinch/scroll do not work. Do: find which app and device (reply in German if there is an email), then check: zoom buttons visible on the canvas for mouse-less use, zoom to a window, zoom to the drawing on open, and the German labels (Vergrößern, Verkleinern, Alles zoomen). Not built yet. Built 2026-11-07 (lab, CadCraft): toolbar View group has Zoom in (2×) and Zoom out (½) beside Extents, Window and Previous, centred on the view (ZOOM 2x / ZOOM 0.5x, which already worked typed); tooltips say the wheel zooms at the pointer. bin/test-cadcraft.mjs 2815/0. Untested: German labels are a draft (en, es-MX, id only), the touch pinch, and on which app the requester looked (CadCraft done; BimCraft not changed).

CadCraftBimCraft Built · Live – – From: site suggestion (Site) Suggestion #1236, Nov 6 2026
Library 8
FeatureATTR.1 Link to ATTR.1Comment on ATTR.1 SuperCad Studio: project report binder with an automatic credits page

Owner 2026-11-03: 'a project report binder, where all the documents go, calculations, notes, etc., and add a credits page.' Built in the lab as the report-binder plugin (Workflow menu, Ctrl+K, Report and price strip): one PDF with a cover and contents, calculations, notes, tasks, optional time and calendar, documents, and always a Credits page, stamped with page numbers, saved in Documentation and downloaded. Credits come from saved IFC and DXF files and from open CadCraft panels (lib/report/credits.js); a closed DWG is listed as not checked. Engineer calculation reports file themselves in the project. Other files are named as not included. Not built: the binder in the Finalize and export zip, other apps' calc sheets filing themselves, bookmarks, a credits table on a sheet in CadCraft and BimCraft. Other scripts print as ? in typeset pages. Tests: bin/test-super-binder.mjs, tools/super-test/binder.mjs. Not released.

SuperCad Studio Built · Live – – From: owner (Site) owner 2026-11-03, library item page
FeatureATTR.2 Link to ATTR.2Comment on ATTR.2 SuperCad Studio: tick what goes in the Finalize and export zip

Owner 2026-11-03. The export dialog has a 'Project documents in the zip' list under the formats: Project file, Notes, Tasks, Time log, Calendar events, Project report binder, Credits page, Documentation folder. Plugins offer items through api.exportItem. The binder is ticked the first time, the rest are not; ticks are remembered in this browser. They go in documents/ and contents.txt names anything that had nothing to add. CC0 items stay on the credits page. Tests: bin/test-super-binder.mjs, tools/super-test/binder.mjs. In /lab, not released.

SuperCad Studio Built · Live – – From: owner (Site) owner 2026-11-03
FeatureATTR.3 Link to ATTR.3Comment on ATTR.3 Report binder: choose the section for each document

Owner 2026-11-03. Each document in the binder dialog has a section picker (Calculations or Documents), kept in the project. Until someone picks, the guess uses who made it (Engineer), the name (calc, calculation, data sheet, analysis, sizing) and the text (an engineer-of-record line). Only those two document sections exist; no sections of your own. Tests: bin/test-super-binder.mjs, tools/super-test/binder.mjs. In /lab, not released.

SuperCad Studio Built · Live – – From: owner (Site) owner 2026-11-03
FeatureATTR.4 Link to ATTR.4Comment on ATTR.4 Report binder: Unicode text, Arabic and Hebrew right to left

Owner 2026-11-03. Typed pages now embed a subset font only when the text needs one: Latin extended, Greek and Cyrillic (Liberation Sans), Arabic, Hebrew, Armenian and Georgian (DejaVu Sans, newly vendored in assets/vendor/rtl-sans), Thai, and Chinese, Japanese and Korean (10 MB, fetched on first need). Arabic letters join and right-to-left lines are ordered with numbers and Latin kept in order (lib/report/bidi.js, a simplified bidi, no bidi control characters). Limits: Devanagari and other Indic scripts have no font or shaper, so they still print as ? and are counted; those stretches print regular, never bold or italic; text copied from Arabic pages comes out as presentation forms in visual order; the page stamp leaves off a project name it cannot print. A font that fails to load prints ? and the dialog says so. Checked by eye on one rendered page, not by a native reader. In /lab, not released.

SuperCad Studio Built · Live – – From: owner (Site) owner 2026-11-03
FeatureATTR.5 Link to ATTR.5Comment on ATTR.5 Report binder: clickable contents and PDF bookmarks

Owner 2026-11-03. Each contents row on the cover links to its page, and the PDF has bookmarks by section with the documents under them. Read back with pdf.js. A merged PDF's own bookmarks are not kept. MarkupCraft's writeOutline moved to lib/report/outline.js. In /lab, not released.

MarkupCraftSuperCad Studio Built · Live – – From: owner (Site) owner 2026-11-03
FeatureATTR.6 Link to ATTR.6Comment on ATTR.6 One shared PDF text kit: BimCraft and CadCraft use lib/report

Owner 2026-11-03. lib/report is now the only copy: BimCraft's a Discord member-pdf.js and Markdown parser and CadCraft's pdf-font.js are thin wrappers over synced a Discord member/report copies (tools/report/sync.mjs; tools/engineer/sync.mjs for PartCraft and SuperCad Studio). BimCraft's PDFs still print with the built-in fonts only; passing fonts would give it Unicode too, not done. Tests pass: bin/test-bimcraft.mjs --sx-tags --only docs (48), --regs (151), bin/test-cadcraft.mjs (2773), bin/test-markupcraft.mjs (564). In /lab, not released.

CadCraftBimCraftMarkupCraftSuperCad Studio Built · Live – – From: owner (Site) owner 2026-11-03
FeatureATTR.7 Link to ATTR.7Comment on ATTR.7 Library credits table on a sheet in CadCraft and BimCraft

Owner 2026-11-03. BimCraft: every drawing set with Library items gets a Library credits schedule, including doors and windows, made again from the model each time and placeable on any sheet. CadCraft: the CREDITS command (ribbon, and a button in the Library credits view) draws the credits as one block of lines and text, at a point and text height you choose; it saves to DXF; running it again updates the table in place and adds no second copy. Both use lib/report/credits.js, required credits first, CC0 after. Limits: CadCraft's table updates only when CREDITS is run; BimCraft sheets print with Helvetica, so non-Latin credits show as ?. Tests: bin/test-cadcraft.mjs, bin/test-bimcraft.mjs --lib-openings and --res, tools/super-test/binder.mjs (real CadCraft panel). The BimCraft schedule was not clicked through in the app's Sheets dialog. In /lab, not released.

CadCraftBimCraft Built · Live – – From: owner (Site) owner 2026-11-03
Site 1
FeatureSTATUS.1 Link to STATUS.1Comment on STATUS.1 Public status page and API: /status and /v1/status, with uptime tracking

A public /status page shows "All systems operational" when that is true, each system's state, 90 days of daily uptime bars, 7/30/90 day uptime and recent incidents. The same data is public JSON at /api/v1/status and api.getcadcraft.com/v1/status (in the Developer API docs). Seven systems: hosting and web, data, API services, MeCentral, cloud, payment and messaging connectivity. A check runs every 5 minutes against the real service: public URLs, a database read and rolled-back write, MeCentral and storage lookups, a read of the payment account and a sign-in to the mail relay (no mail sent, no money touched). Late checks show as late rather than as an old all-clear; while the database is down the page still renders and results wait in a spool. Tested with bin/test-status.php (36 pass), against the live services, and on screen in both themes and at phone width; a real outage has only been simulated. The checks run on the server they watch, so a full server or network outage shows only afterwards, as a gap counted against hosting; an outside monitor is not built.

– Built · Live – – From: owner (Site) owner request 2026-11-04
Digital twin add-on (TW) 9
FeatureTW.1 Link to TW.1Comment on TW.1 Digital twin: soft PLC runs on the flow model

Built in the lab: lib/plc in lock step with the flow simulation, IEC 61131-3 ST or PLCopen XML, starter program from the layout. Same program and seed repeat to the byte. No real PLC involved.

ModelCraft Built · Live – – docs/0.9-DIGITAL-TWIN.md
FeatureTW.2 Link to TW.2Comment on TW.2 Digital twin: forces, faults, stock tests, report

Built in the lab: force any signal; stuck eye, stuck gate, belt stop, station down, emergency stop; stall watchdog; tests every layout gets; CSV report. A program that ignores the stop fails on the right check. Not a safety validation.

ModelCraft Built · Live – – docs/0.9-DIGITAL-TWIN.md
FeatureTW.3 Link to TW.3Comment on TW.3 Digital twin: rigid-body physics on loads

Built in the lab: our own XPBD with moving belt surfaces, boxes only, up to 8 loads along one line. Checked against closed forms: slip tan θ = μ, tip tan θ = L/H, belt pick-up v/(μg). Formula screen per belt agrees with the run. Not against a measured line yet (TW.12).

ModelCraft Built · Live – – docs/0.9-DIGITAL-TWIN.md
FeatureTW.4 Link to TW.4Comment on TW.4 Digital twin: compare layouts, bottleneck ranking

Built in the lab: repeat runs on common random numbers, 95 % intervals on paired differences, "no clear difference" when the interval holds zero. Ranks what is limiting; found a planted slow station. A ranking, not a proof.

ModelCraft Built · Live – – docs/0.9-DIGITAL-TWIN.md
FeatureTW.5 Link to TW.5Comment on TW.5 Digital twin: equipment view

Built in the lab: frames, rollers, legs, machines, robots with moving arms, people, cartons and vehicles in place of plain marks. Generic shapes for the picture. Arm motion is for the picture, not a robot program. Not checked for frame rate on large layouts.

ModelCraft Built · Live – – docs/0.9-DIGITAL-TWIN.md
FeatureTW.6 Link to TW.6Comment on TW.6 Digital twin: run into the model for the path tracer

Built in the lab: equipment as real geometry, loads on the animation timeline, up to 150 loads. Path-traced frame at a timeline time rendered on workstation11a (RTX 5070). A full path-traced clip has not been run. Arms do not move in the baked clip.

ModelCraft Built · Live – – docs/0.9-DIGITAL-TWIN.md
FeatureTW.8 Link to TW.8Comment on TW.8 Digital twin: ready cells as data

Built in the lab: PLC stop gate, robot palletizing, two-lane sorter, incline and curve. One data entry per cell. Numbers are starting points.

ModelCraft Built · Live – – docs/0.9-DIGITAL-TWIN.md
FeatureTW.9 Link to TW.9Comment on TW.9 Digital twin: bill of materials

Built in the lab: quantities from the layout, CSV with price and supplier columns for the person to fill in.

ModelCraft Built · Live – – docs/0.9-DIGITAL-TWIN.md
FeatureTW.15 Link to TW.15Comment on TW.15 Digital twin: order files from a warehouse system

Built in the lab (Material flow add-on, ModelCraft): a source can take its arrivals from a CSV orders file instead of random times (columns time_s / time_min / time_h / time / clock, type, length_m / length_mm, qty, source, order; the time unit and base are stated in the help). The same file gives the same run for any seed (no random draw is used). A row that cannot be read stops the whole read and the panel names the first bad row (line, column, what the cell said); nothing is skipped. Tables are saved in the model file; Save as CSV writes one back. Sample orders (about 130 invented rows) are in the add-on's data folder and the flow listing's Data section. Tested: lib/flow orders tests in the flow suite, and in the real /lab page (browser-orders.mjs 10/0). Does not read any warehouse system's own format.

ModelCraft Built · Live 4 – docs/0.9-DIGITAL-TWIN.md
Planned suggestions, built in 0.9 (2026-11-06) 4
FeatureSU.747c Link to SU.747cComment on SU.747c NURBS surfaces, step S3: fillets and blends between faces, thickening, a solid written to STEP as one closed shell

Asked (#747, #748, #749, #750, Oct 16): concept-to-prototype NURBS and production-quality surfacing. S1 (curves, untrimmed surfaces, measured G0 to G2) is Built in 0.8; trimmed surfaces, solids from them with union, subtract and intersect, and PartCraft Bake are Built in /lab 0.9 (docs/0.9-sessions/nurbs-09.md). That log lists what is left and says 'Fillets between faces come next'. Plan (lib/nurbs): (1) fillets and blends between two faces, constant then variable radius, deviation from the rolling ball measured; (2) thickening a surface into a solid, self-intersection refused and named; (3) a solid written to STEP as one closed shell, read back; (4) Booleans as nodes. Each result measured against a closed form. Not claimed: class-A surfacing, the other programs' file formats, a result equal to Alias or ICEM Surf. Class-A and equality with Alias/ICEM are never claimed. Completed 2026-11-06: in /lab (ModelCraft, PartCraft, SuperCad Studio's panel through the shared libs): fillet between two faces (constant/variable radius, convex/concave, closed edge; deviation from the rolling ball measured), several edges at once (mitred corners; one sphere patch where three flat square faces meet, radius equal), thicken into a solid, STEP and IGES (186 over closed shell 514) with a solid as one closed shell, read back as a solid, Booleans as nodes in the node editor, help lines. Measured against closed forms (removed volume within 2 % at tol 0.05, goes with the tolerance). Not built: vertex blend for curved faces or unequal radii, fillet between faces that do not meet, inside fillet ending on a slanted or curved face, several inside edges that reliably close (the result line says if not), Booleans/fillets on the surfaces without triangles, IGES not tried in another program. Tests: docs/0.9-sessions/nurbs-s3-09.md.

ModelCraftPartCraft Built · Live 8 A real surface model from the reporters (#747 to #750) opened in another program would be the best test docs/0.9-sessions/planned-suggestions-09.md
FeatureSU.749 Link to SU.749Comment on SU.749 PartCraft: large assemblies, measured first at 1,000, 5,000 and 20,000 parts, then fixed where it is slow

Asked (#749, Oct 16): managing large, complex assemblies, with Catia named as the reference. PartCraft's stress tests so far are 750 features in one part (D7.51) and closed-loop mates (D7.40); no row measures an assembly of thousands of parts. Do: (1) generate the test assemblies ONCE under testfiles/generated/ (registry testfiles/LARGE-FILES.md, memory 'large-test-files'), from repeated instances of a few parts, not from files typed by hand; (2) measure open, rotate, select, mate-solve and save at each size in the real page, one browser test at a time with nice and timeout; (3) fix what the numbers show, in this order of likelihood: instancing (one mesh, many transforms), level of detail and a lightweight display mode, hiding by visibility sets, mate solving only for what moved, saving without rewriting unchanged parts. Record every before and after number in the log and in the release notes (memory 'test-results-in-release-notes'). Not claimed: Catia's feature set, any size without a measurement. Untested: everything, including the sizes above. assembly-09 2026-11-06: Measured at 1,000, 5,000 and 20,000 copies of three small parts in the real page (headless Chromium on a CPU renderer, never a GPU), before and after; fixed: one draw group per part (40,000 draw calls to 3 at 20,000), a joint turned places only the parts behind it (5.0 s to 65 ms at 20,000), the part list shows its first rows (a click 11 s to 26 ms), boxes while the view moves (Views > Lightweight display keeps them on; a frame 15.7 s to 0.9 s on the CPU renderer), and assemblies open up to 50,000 copies (500 before). A frame in full detail is not faster on the CPU renderer; assemblies of heavy parts and a real GPU are not measured. No claim about any other program. Table and tests: docs/0.9-sessions/assembly-09.md.

PartCraft Built · Live 6 Hand check is community test SU.749-HAND (not blocking) docs/0.9-sessions/planned-suggestions-09.md
FeatureSU.908 Link to SU.908Comment on SU.908 Finite elements for plates, shells and solids (linear static and modal), the engine behind slabs, shear walls and a solid stress check

Asked (#908: Abaqus, Ansys, SAP2000, STAAD.Pro, ETABS and others; #890 RFEM; #1057 SPACE GASS; #1141 SAP2000): finite elements beyond beams. Built (lib/fem, own code, Apache-2.0): four-node shell (MITC4 or DKQ), ten-node tetrahedron, modal analysis, sparse IC(0)-PCG solver, slabs and shear walls through the frame mesher; known-answer tests with cited derivations (Navier, Lame, Timoshenko, Leissa, Blevins; 60 + 10 + 15 checks). Reachable: the Analysis panel of BimCraft and DetailCraft, block 'Finite elements: natural frequencies': modes, period, effective modal mass, mode drawn on the model, member end releases and rigid floors carried, settings saved with the model, the report carries the table, help written. Deflections, reactions and plate moments of slabs and walls are shown by the frame solver in the same panel (lib/frame plates; lib/fem agrees with it to 1 % in tests). Solid FEM: lib/fem's tet10 solid is the PartCraft add-on 'Solid FEM' with its own panel (SU.908c); PartCraft keeps its own solver (owner 2026-11-06). DKQ is a panel choice; the static solve in the panel stays lib/frame's (one engine, no second copy). Not built: nonlinear, contact, damping, response spectrum, soil models. No claim of equality with any other program. Hand check: SU.908-HAND (big meshes and a real building on a workstation or by the community; not a blocker). fem-complete 2026-11-06: docs/0.9-sessions/fem-09.md

BimCraftModelCraftDetailCraftPartCraft Built · Live 12 Hand check is community test SU.908-HAND (not blocking) docs/0.9-sessions/planned-suggestions-09.md
Units 1
FeatureTKW.1 Link to TKW.1Comment on TKW.1 Weight and temperature units (kg, lb, t, ton; °C, °F, K, °R)

Asked in support message #1329 (metric in the quick properties, kilograms, Celsius). Owner 2026-11-08: build weight and temperatures, both F and C, into 0.9. Shared table lib/units gets two kinds: mass (mg, g, kg, tonne, oz, lb, ton, long ton; exact factors from the 1959 pound) and temperature (K, °C, °F, °R; offset scales, converted without a detour through kelvin for C and F, negative values read correctly); Settings › Global › Units lists them (en, es-MX, id words). TakeoffCraft: lb, ton, kg and t as typed-quantity units (priced like CY), an optional Temperature on every item typed and shown in °C or °F (Settings › TakeoffCraft: Follow Global / °C / °F), kept in kelvin. bin/test-units.mjs 261/0, bin/test-takeoffcraft.mjs 1210/0. Seen in the real /lab page: browser-weights-temps.mjs 12/12 (unit lists, temperature typed in C and F, display setting, undo). Temperatures are absolute (a difference is not converted). Reports/exports do not carry the item temperature yet. Reply sent 2026-11-08 (support #1329, answered). No account for abdulrahman.mahmoud@almada-eg.com yet: the reply invites him to sign up; grant the lab pass (TakeoffCraft, a Discord member) when the account appears.

CadCraftBimCraftModelCraftMarkupCraftTakeoffCraftCivilCraftDetailCraftPartCraft Built · Live – requester account for the lab pass From: Abdulrahman Mahmoud (Site) support message #1329 2026-11-08
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.