options.json gains nozzle (hostSupplied: slicer, 0.2-0.8, default 0.4). The
entry sends it in tunables on every call, so a host's long-lived engine context
can't keep the last part's widths. Cura: machine_nozzle_size on the part's
extruder. Orca: nozzle_diameter, the wall extruder's entry. FreeCAD, Blender,
Fusion, SolidWorks and the CLI pick it up from the schema.
Tines and the contact tip scale by nozzle/0.4 both ways; the wall, wedge and
sway brace rib only grow (a finer nozzle doesn't stiffen a free-standing wall).
Heights stay on the layer height. 0.4 is unchanged (sweep vs main: identical).
The Worker gets it in opts.tunables.nozzle; the plugins stay at 0.4 for now.
URL.pathname gives '/C:/dir%20with%20space/...' on Windows, so every test that
reads a model or fixture failed there (75 of 265). import() specifiers keep the
URL; disk reads take a filesystem path.
* engine: interface crest (GitHub #21) -- with PROP.iface on, every wall (prop, part-attached, squat, Draw/fill, wedge blade) splits 0.6 mm under its top into body + crest, the crest and the tine comb tagged (v[3] = 1) so triRanges/removal/Worker are untouched; the 3MF writer's separate form writes the tagged triangles as a third object, '<name> interface', in register; off (the default) is byte-identical
* site: Interface material switch (Walls) -- the crest and tines show purple and export as their own 3MF object, for a toolchanger's second filament (PETG under PLA); reaches the Worker via tunables and Draw on the page; re-import still pre-selects the part; German strings; plugins leave it out (one body to the host)
* engine: interface crest review fixes -- sway brace tines are interface too (Auto and Draw); the crest is one trapezoid on the taper line, so no section has a collinear corner (zero-area cap triangles); Interface material is in the undo history; FIN-SPEC lists what is not split yet (sway rib edge, a part-standing wall's foot, a wedge whose contact steps straight up) (review)
* site: the interface is a part of the supports object, not its own -- an object starting in mid-air is refused by Orca ('empty first layer'); as the supports' second component it stands on the plate with them and takes its own filament per part
* engine: interface crest modes -- 'flat' (the default when on) crests a wall station only under an underside within 10deg of level, a full-width (th) 0.6 mm block with no tip taper, tines left in the body; 'all' crests every wall top and the tines as before. A 35deg cube's print with the crest everywhere couldn't lay PETG on the narrow PLA tip through every layer; PETG interfaces are used on flat undersides. Off stays byte-identical (sweep vs main)
* site: Interface material is a dropdown (Off / Flat contacts / Everywhere); the readout says when it is on and no wall got a crest; German strings
* engine: interface modes review fixes -- cutouts under a flat crest keep their old ceiling (holeTop: the taper start, not the crest's cut), so the split loses no plastic (lbracket Y8 lattice lost 4.6%); the crest's part reference is set only while the crest is on and dropped after each build; the readout's 'no flat contacts' note counts walls only (not the pad) and only in Flat contacts; tests: flat mode with lattice/diamond cutouts, mixed flat/tilted walls, squat walls (review)
* engine: the interface crest is one layer of the print (PROP.ifaceLayers 1, the Layer height field, as the tines), not a fixed 0.6 mm -- one tool change each way per flat contact instead of three; tooltip and FIN-SPEC say so; tests: the crest is one 0.2 / 0.3 mm layer
---------
Co-authored-by: matthewtrahan <mathyout@pm.me>
* engine: plateOnly -- every support on the build plate, none on the part (#218). Auto and the short walls drop a line the part-attached path would take (built or floored) and count it as skipped.onPart, never stilting it to the plate through the part; drawnWall refuses a line with part under it, naming the setting, and its squat fallback skips the part; the fill pass never retries a wall on the part. Off by default: sweep vs main identical. tests: plate_only -- a drawn line over the part refused, over open plate byte-identical; Auto and Full on the portal at Y90 build nothing on the part and count it; off, the lbracket is unchanged
* ui + plugins: a Plate only checkbox under Walls (#218) -- read by the auto build and the drawn walls; the readout says how many supports it left off and why, and names it when it emptied a part; undoable; German strings. options.json gains plateOnly, so every plugin dialog shows it, and both entries pass it on. tests: the dead-control check runs it on the portal at Y90 (the lbracket has no wall on the part); FreeCAD and Blender unit fixtures list it
* plate only: Full refuses a line over the part before building it, and a mixed line keeps its plate stretch (review) -- the local pass turned the on-part retry back on, and every try reached drawnWall to be refused: the portal at Y90 spent all 120 tries and blamed the wall limit. stationClear's `plate` now refuses a station with part under it on every try. Auto hands a line the part-attached path claims to the plate path (its column probes trim the stations over the part) instead of dropping it whole. The readout names Plate only when it emptied a part in any mode, not only Prop; German help line. tests: every built support reaches the plate, Full isn't capped
---------
Co-authored-by: matthewtrahan <mathyout@pm.me>
Takes over #183. The add-in (C#, .NET Framework 4.8) reads the part's visible
solid bodies, and a WebView2 window runs the website's engine (the shared
bundle, unmodified) at V8 speed, outside SolidWorks' thread. Its dialog is
built from options.json and its readout is the shared reportLine, so overhangs
it can't reach and floating pieces are said. Print bed: Top Plane (Y up),
Front Plane (Z up) or a selected flat face, never guessed. Each piece goes in
as its own named solid body (STL import as solid, mm, the user's import
settings put back after); the next run skips and counts them.
SolidWorks interop is compile-time only, its types embedded: no Dassault DLL
ships and no single SolidWorks release is required. Builds with dotnet on any
OS (build.py --zip). tests/host.test.js pins the frame mapping (same fins as
computeFins whichever way up the model is drawn) and that every piece is a
closed, consistently wound STL. Not yet run in SolidWorks: README has the hand
test.
From #183: the ribbon command, reading tessellation in metres, the Y-up frame.
Co-authored-by: Haititei <werbung@iggena.de>
A thin right triangle whose slope sits 0.2 mm under a tilted part's underside
(the 30/45/60 deg fins on printables.com/model/1771718): straight back edge,
short flat top, foot that keeps the slope's gap, one-layer horizontal tines along
the slope biting 0.5 into the part at mid-layer, tops snapped to the print
preset's layer grid. Slope Angle field (20-70, default 45). The smooth slope is
one cube turned about Y over a hidden step fill (make_prism is isosceles and would
need a Negative cut the slicer draws as a grey box). Mock test models rotation,
the layer grid and string presets; README + in-slicer checklist rewritten.
- Both overlays used the material "Support Fins overhangs", and _material repaints a
material by name: on a part with both kinds of face, the amber pass turned the red
overlay amber too (Blender's solid view colours by material), mixing up "held" with
"too small to fin". Each overlay now has its own material; the smoke test builds the
bracket + a 1.5 mm nub (both kinds) and checks each colour (fails without the fix).
- A fin whose triangles all fall to the degenerate filter is left out of the 3MF
(an object with no triangles isn't valid 3MF).
- README: Blender's own STL export needs Selection Only, or the overlay sheets go too.
Generate paints the overhangs the fins hold red and the faces past the angle but too
small to fin amber, as on printfins.com, so an overhang nothing holds is shown rather
than hidden. They are unselectable, unrendered objects under the part, drawn in front;
Show overhangs (after Generate) toggles them, skipping any in an excluded collection.
Lay face flat and Clear remove them with the fins.
Blender has no 3MF exporter. The part and each visible fin / drawn wall are their own
3MF objects, all in one build item, so a slicer opens them as one object in their
original places. Triangles the weld closed are dropped (invalid in 3MF), and the export
warns when the fins are out of date. The manifest asks for file access for it.
Co-authored-by: RemusTL <336249490+RemusTL@users.noreply.github.com>
- A part that only ever had drawn walls never gets a result line: with those walls
deleted by hand, Clear was disabled while the pose stamp stayed (out of date
forever). Clear now also runs for the stamp alone.
- A drawn wall that no longer fits the pose was hidden but kept its old-pose mesh,
which Blender's own STL export (Visible Only is off by default) would still write.
It is now emptied as well; its ends stay, so it comes back when the part does.
- A click in the viewport that misses the part no longer passes through to Blender
(it changed the selection mid-tool); the header says to click on the part.
Clicks outside the viewport still pass through.
Draw wall: two clicks under an overhang make one wall through drawWall, with an orange
preview line between the first click and the mouse; a line the engine refuses says why.
Each drawn wall keeps its ends in the part's frame, so Generate re-stands it for the
part's current pose (the site's rebuildDrawn) or says why it no longer fits; a drawn
wall alone marks the fins out of date when the part moves. Lay face flat turns the part
so the clicked face is down, keeping its lowest point, and drops the old pose's fins.
The tools start from the sidebar but cast from the 3D View's window region, and any
error ends them cleanly (no preview handler or header text left behind).
Co-authored-by: RemusTL <336249490+RemusTL@users.noreply.github.com>
- Blender cuts a label longer than the sidebar off with an ellipsis; the fixed
42-character wrap was wider than the default sidebar, so "That size looks wrong for
a print: is ..." and long result lines lost their ends. The wrap now follows the
sidebar's width and UI scale.
- Clear needed a fin to exist; with every fin deleted by hand the result line and the
pose stamp stayed (and the out-of-date check ran against fins that were gone).
- The manifest's Import-Export tag waits for the 3MF export.
The smoke test installs the zip into a checksum-verified official Blender with its user
folders in a temp dir, then: lbracket @35 gets the site's 4 walls / ~20 tines as closed
objects on the bed; moved / settings / edited / unit scale mark the fins out of date;
settings hide as the engine says; the panel draws in every state; Clear.
The zips go to plugins-latest with the others.
Co-authored-by: RemusTL <336249490+RemusTL@users.noreply.github.com>
Rebuild of #145 on the plugins' model: the panel is generated from options.json and a
setting shows only when the engine uses it; the fins come from computeFins through the
shared host (mini-racer as a manifest wheel, JIT on), one object per wall / sway brace
/ pad (pieces); the result line is host_report, so overhangs that weren't reached and
floating pieces are always said. Moving the part, editing its mesh (caught across a
save + reopen by a mesh fingerprint), changing a setting or the unit scale marks the
fins out of date. Units: Unit Scale x 1000 = mm; the panel offers Use millimetres when
the part's size looks wrong.
build.py makes one zip per platform and flattens mini-racer's wheel: it publishes the
package under .data/purelib/, which Blender 4.2 / 4.3's installer leaves unimportable.
GPL-3.0-or-later (Blender's rule for add-ons); the bundled engine stays MIT. Draw wall,
Lay face flat, 3MF export and the overhang overlay follow on their own branches.
The default stays --jitless on macOS (Orca's hardened app refuses JIT memory). Blender's
macOS app is signed with com.apple.security.cs.allow-jit, and jitless ran issue121 (75k
triangles, 81 walls) in 80 s against 3 s with the JIT -- same walls and tines. Pinned:
jit=True gives lbracket's 4 walls / 20 tines in a fresh process.
overFaces was every face past the threshold, but the site paints only the faces in
regions it supports red (res.kept) and the too-small ones amber. A host painting
overFaces red would have called slivers overhangs that no fin targets. Now
overFaces = red, smallFaces = amber, both pinned to paintOverhangs' rule (a shelf +
2 mm nub part gives an amber face, so that half of the check runs).
drawWall: the site comparison checks where the wall is, not just its counts, on an
off-centre part; layer height 0.1 / 0.3 reach the wall. host_draw_wall refuses a
NaN end in Python instead of a raw JS parse error; stats say partAttached.
engine/draw_entry.js drawWall(soup, a, b, options): the part as computeFins takes it
and the two clicked points in the same frame -> web/draw.js drawnWall, called as
web/ui/walls.js calls it (print-frame part, the material's tunables set). Same seat
as computeFins, so the wall is bit-identical wherever the part sits; a wall it can't
build comes back with the site's reason ("wall too short ..."). Bridge: drawWallB64;
Python: host_draw_wall.
Tests pin it to the site's wall (PLA and PETG), plate-position independent, no
clearance leak into the next wall or the next computeFins.
A host that wants each wall as its own object (Blender next) had to call buildFins
itself to get the fin ranges, skipping the entry's seat and material clearances.
computeFins now returns pieces ({id, kind, ranges} in triangles of its soup; every
triangle in exactly one) and overFaces (input faces analyze() marks red). Python:
host_compute_pieces; host_compute is unchanged for Orca, Cura and FreeCAD.
The seat (centre + 1 nm snap) and the material clearances move to engine/seat.js
so the next entry (Draw mode) seats a part exactly the same way.
PrintFrame.from_bed took x = n x ref, so a bed on the XY plane gave print x = world
+Y, y = world -X. The engine isn't the same under a turn about z: the headset got 95
walls / 144 tines in Fusion, 93 / 140 on the site and CLI. x is now ref projected onto
the bed, so an XY bed is the identity frame. Chairs, lampshade, bunny, gree, bear,
zombie, lighthouse and the headset now match the CLI.