Point Visuals and Nodes at the openflowfm/visuals wiki, where they live now
Document model preview navigation and lighting Co-authored-by: Codex <noreply@openai.com>
Document reusable GLB models Co-authored-by: Codex <noreply@openai.com>
Say that light goes past white, and that copies get dealt The node manual regenerates itself, so `vary` and the two new modes arrived in Nodes.md on their own. Visuals.md needed the prose: a neon filament is driven above what the screen can show and `spread/bloom` is what puts that excess back as halo, which is the difference between a lit line and a pale one. `shade` gains `filament` — one colour from unlit to blown — because ramping across the palette paints hue onto geometry and a curve whose colour changes along its length reads as a thermal image. And `vary` is here, with why a copy number wired straight into brightness gives a ramp round the ring rather than sixteen separate lights. Twenty-four flows now: `depth` and `comet` join the five. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SGPm8ZaGY63UWZRkGg2feU
Add the drawing nodes to the manual, and the oscillator merge to the guide The node reference is generated, so `figure`, `array`, `glow`, `shade` and `form` arrived in it on their own. The guide is not: it calls out the nodes worth a paragraph, and five new ones with nothing said about them would send a reader to a reference page to work out what a distance is for. So: how a shape becomes a lit line, why `array`'s second outlet is the point of it, and what `form` costs — it brings its own light rather than being bloomed, and turning `chrome` up trades the glow for a reflection of a room built out of the colourway.
Every node, every mode, every inlet — generated from the rig Visuals has a table of what you can drop on a canvas, written by hand and read before you start. This is the other half: the thirty nodes in full, with each one's modes, what every inlet is for, and the value it starts on until you say otherwise. It is generated — `npm run dev:node-manual` in the repo — from the same descriptions the app prints on the node, so the manual and the app cannot come to disagree about what a mode does. The list it joins had said eleven `lens` modes since the twelfth was added.