You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GCode comments metadata from the slicer can provide valuable information to the library. However, slicers format the comments differently.
I'm suggesting a first implementation that would only take care of the layers split. Right now, the parser uses a tolerance algorithm based on z changes. I'm suggesting a library for prusa and/or cura that would parse the ;LAYER_CHANGE (prusa slicer) and ;LAYER:2 (Cura) comments when available and fallback to the tolerance algorithm only when the metadata is not available.
Eventually, we'll want the line types (outer wall, infill, etc) for features around those!
The text was updated successfully, but these errors were encountered:
GCode comments metadata from the slicer can provide valuable information to the library. However, slicers format the comments differently.
I'm suggesting a first implementation that would only take care of the layers split. Right now, the parser uses a tolerance algorithm based on z changes. I'm suggesting a library for prusa and/or cura that would parse the
;LAYER_CHANGE
(prusa slicer) and;LAYER:2
(Cura) comments when available and fallback to the tolerance algorithm only when the metadata is not available.Eventually, we'll want the line types (outer wall, infill, etc) for features around those!
The text was updated successfully, but these errors were encountered: