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
in release build, we will only observed that all presures advance tests are not generating the correct gcode.
if you switched to debug build, it actually crashes.
not invalid slices, it just crashes in debug build, and in release build, the placeholder object is not replaced by the actual gcode, resulting the gcode only generate the non-calibration gcode.
overall, in current release version or master branch, the slicer calibration tests is are working at all.
Activity
wjyLearn commentedon Sep 10, 2026
Is it the case that the calibration function sometimes encounters the problem of invalid slices?
bugparty commentedon Sep 17, 2026
not invalid slices, it just crashes in debug build, and in release build, the placeholder object is not replaced by the actual gcode, resulting the gcode only generate the non-calibration gcode.
overall, in current release version or master branch, the slicer calibration tests is are working at all.
bugparty commentedon Sep 18, 2026
@wjyLearn
bugparty commentedon Sep 29, 2026
@wjyLearn 已更新 PR #231 的说明。当前 release 版本中 PA Line / Pattern / Tower 三种校准全部无法生成正确的 G-code，修复只涉及一行，麻烦抽空 review 一下，谢谢！