The problem. Slicers already control many of the things that shape how a printed part behaves, such as infill density and pattern, surface texture, nozzle temperature, flow, and material mixing. But they apply them to whole regions that users have to cut out and configure by hand, so grading a setting smoothly through a part means hundreds of manual steps or hand-editing G-code.
The idea. I treat the slicer as a compiler target. A design describes each setting as a spatial field. The compiler divides those fields into regions, extracts matching sub-meshes, and writes a native project file for PrusaSlicer or OrcaSlicer. The slicer then does its own toolpath planning, supports, and preview as usual, so the method works with existing printers and slicer profiles instead of requiring a custom slicer.
Key result: grading the process, not just the material
A single bunny combines three process fields. Surface texture is assigned by anatomical region and blended smoothly, while nozzle temperature and flow control how much a foaming TPU expands, which sets the local hardness between 65A and 85A. In calibration, measured hardness followed the designed gradient with a mean absolute error of 0.5 Shore A.
This work is with Devon Beck (Draper) and Robert MacCurdy, and the compiler is part of OpenVCAD.