Repository navigation
v1.76.0 — raster order preserved by the travel optimizer
The travel optimizer no longer reorders raster scan lines unless explicitly asked to, fixing the irregular banding that raster engravings picked up from travel-optimized row order (rayforge#686), and the core now builds without any compiled C/C++ dependencies.
Changed
- The travel optimizer keeps raster scan lines in emission order by default (#116). It treated every scan line as a reorderable segment, so raster rows burned in travel-optimized order instead of strictly top-to-bottom. On belt-driven machines each Y reversal between out-of-order rows takes up mechanical play and displaces the rows, which shows up as irregular horizontal banding spanning several lines. Confirmed against a user's exported G-code: 2,804 rows on a perfect 0.08mm grid, but 34.7% of row transitions moved the Y axis back up, with hops of up to 2.8mm between consecutive rows. The old travel-optimizing behaviour stays available behind the new
reorder_scanlinesflag onOptimizeSpecandoptimize_travel; cut-only segments are still reordered as before. - All compiled C/C++ dependencies replaced with pure Rust (#115). The native clipper2/zstd builds are gone, simplifying wheel builds and the wasm32 embeddable target.
Fixed
- Docs gallery renders of the final clipper backend restored (#115).
Full changelog: v1.75.0...v1.76.0