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

Option to render retractions #223

Open
2 tasks
sophiedeziel opened this issue Oct 13, 2024 · 5 comments
Open
2 tasks

Option to render retractions #223

sophiedeziel opened this issue Oct 13, 2024 · 5 comments

Comments

@sophiedeziel
Copy link
Collaborator

sophiedeziel commented Oct 13, 2024

I had that idea after investigating stringing issues that fused parts of a print-in-place flexible model.

Prusa Slicer has the option of rendering retractions. It's useful to be able to render that.

Screenshot 2024-10-13 at 11 07 59

For this feature to be as accurate as possible, we'd have to implement the G0/G1 with negative E case as well as introducing G10 support.

The API could be very similar to what we have right now with the other types of renders:

{
  ...,
  renderRetractions: true,
  retractionColor: '#FF0000',
}
  • detect retractions in g0/g1 movements: movements with E < 0
  • detect firmware retractions using G10/G11 (I think G22/G23 too and possibly other vendor-specific gcodes)
@remcoder
Copy link
Member

Can I suggest we do this in v3.1+?

@remcoder remcoder added 3.1+ and removed 3.0 labels Oct 18, 2024
@sophiedeziel
Copy link
Collaborator Author

Yes!

@remcoder
Copy link
Member

remcoder commented Jan 14, 2025

I just realized PR #269 actually detects and counts retractions now.

atm, zero-length movements are removed from the scene because they would be invisible anyway. But they might as well be rendered and the interpreter at least detects them.

@sophiedeziel
Copy link
Collaborator Author

sophiedeziel commented Jan 15, 2025

There's also the native G10 gcode, but I think slicers mostly use g0/g1 for backward compatibility with older printer firmware.

@remcoder
Copy link
Member

Good point. I updated the description

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants