What it is
Denford-style VR CNC milling simulation for DT practice.
What broke, and what I’d change
Not written yet. This is the part only I can write — what actually went wrong, and what I’d do differently. It lives in builds/reflections/vr-cnc-milling.md (see _TEMPLATE.md); as soon as that file has words in it, this section fills in on the next build.
Everything else on this page — the spec, the version history, the file counts — is generated from the project’s own build notes and files, so nothing here is guesswork.
Build spec
The project’s own build notes, rendered. Open the raw .md ↗
Show the spec
VR CNC Milling
Category: Software & Apps · Status: Done
Denford-style VR CNC milling simulation for DT practice.
Stack / Tools: CNC, VR, Simulation, DT
Location: ~/demos/vr-cnc-milling.html
Self-contained single-file HTML web app.
Where it lives
- Source file:
~/Documents/VR_CNC_Milling_6.html - Artefacts on the site: 1 files · 897 lines of text · 29 KB
Stack
- HTML ×1
What's in the code
VR_CNC_Milling_6.html— 897 lines (HTML)
Verified in the page source
- page title: “VR CNC Milling 6 - Denford Simulation”
- headings: Machine Control · Material · Machine Info · Tool Info · Program
- functions:
createBillet,updateBilletVisibility,createToolpathVisualization,createCutSurface,c,d,addSideWalls,createWallMesh,c,d,c,d,createChip,updateChips - UI element ids:
coolantStatus,cycleStartBtn,estopBtn,feedHoldBtn,feedRate,gcodeFile,progressBar,progressText,sidebar,speedSlider
Notes found in the scripts
- app { display: flex; height: 100vh; }
- viewport { flex: 1; position: relative; background: #0a0a0f; }
_Spec generated from the project's own files on 2026-10-22 (gen-project-specs.py). Everything above was read from the listed files — file counts, line counts, names, routes, headings and script comments. No description was invented._