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

Corruption in exported GCODE } #3178

Open
TheWhiteDragonsRage opened this issue Sep 4, 2022 · 1 comment
Open

Corruption in exported GCODE } #3178

TheWhiteDragonsRage opened this issue Sep 4, 2022 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@TheWhiteDragonsRage
Copy link

Version

Version of SuperSlicer used goes here (help->about)
Version 2.4.58.4

Operating system type + version

What OS are you using, and state any version #s
tested on Win 11 & Win 10

Behavior

  • Describe the problem
  • Exporting STLs produces a name with a } in the time section.
  • Steps needed to reproduce the problem
  • purge the appdata\roaming\superslicer folder
  • run superslicer, slice a STL, export Gcode
  • Expected Results
  • filename generated to have an additional } - ie Geotappino medio_2h18m_0.20}mm_205C_PLA_ENDER5.gcode
  • Actual Results
    • Screenshots if useful

Is this a new feature request?
Related guides for writing feature requests: http://meta.stackexchange.com/a/259196 http://nickohrn.com/2013/09/write-great-feature-request-bug-report/

Project File (.3MF) where problem occurs

Upload a Project File (.3MF) Plater -> Save Project as...
You have to zip it (or rename it to .zip) to be able to drag& drop it here
superslicer-corruption-name

@jhlchu
Copy link

jhlchu commented Sep 5, 2022

#3157

@supermerill supermerill added the duplicate This issue or pull request already exists label Sep 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants