Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Settings are not emitted at the end of the gcode file, which prevents post processor functions #669

Closed
kursatu opened this issue Nov 15, 2020 · 2 comments
Labels
fix is live in the last release Please download /build the last release and try to reproduce.

Comments

@kursatu
Copy link

kursatu commented Nov 15, 2020

Version

Version of SupserSlicer used goes here, Use About->About SuperSlicer
I've built it from the latest sources on GitHub, so it is 2.2.55

Operating system type + version

What OS are you using (and version)
WIndows 10

3D printer brand / version + firmware version (if known)

What 3D printer brand / version are you printing on, is it a stock model or did you modify the printer, what firmware is running on your printer, version of the firmware #s

Behavior

  • Describe the problem
    I've a somewhat complicated post processor that relies on the settings.
    They are usually stored at the end of the gcode file
    Things like
    ; infill_speed = 80
    ; external_perimeter_speed = 30

They are not emitted anymore, so my post processor falls back to hard-coded default settings.
This does not really work.
Not sure if this is Prusa merge issue or not.
Defect14.zip

  • Steps needed to reproduce the problem
  • Slice and save the attached 3mf file.
  • Observe that there are no settings at the end of the gcode file.
  • Expected Results
  • Actual Results
    • Screenshots from SuperSlicer preview are preferred

Project File (.3MF) where problem occurs

Upload a SuperSlicer Project File (.3MF) (File -> Save / Save Project)

@supermerill
Copy link
Owner

supermerill commented Nov 15, 2020

solution: update to 2.3.55_hotfix version
you can also get the latest nightly

@supermerill supermerill added the fix is live in the last release Please download /build the last release and try to reproduce. label Nov 15, 2020
@kursatu
Copy link
Author

kursatu commented Nov 15, 2020

I've built the latest sources and the problem is gone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix is live in the last release Please download /build the last release and try to reproduce.
Projects
None yet
Development

No branches or pull requests

2 participants